LiveCode and SCRUM tools

[Peter Haworth]

I guess it's a different world these days.  The thought of trying to assess
progress on a daily basis seems like a major case of micro management to
me.  No matter what the reporting period is, if someone isn't good at
estimating their progress, the project slips. Splitting a project into such
small tasks that they can be measured on a daily basis seems practically
impossible.  Plus, back to the critical path issue, if a sprint or whatever
you want to call it takes twice as long as estimated but still doesn't
affect the overall project end date, so what?

But once again, I'm "old school" so if that works for people, that's all
that matters.

Sorry, I guess this is getting wildly [OT]

Pete
lcSQL Software <http://www.lcsql.com>


On Sat, Jan 4, 2014 at 8:50 PM, Mark Wieder <mwieder at ahsoftware.net> wrote:

> Geoff-
>
> Saturday, January 4, 2014, 6:22:45 PM, you wrote:
>
> > Mark might work differently (scrum is flexible) but where I work each
> > discrete task is a day's effort or less (for one developer). The
> assumption
> > is that tracking smaller tasks in simple terms of not-started,
> in-progress,
> > done makes for greater accuracy than tracking percentages on larger
> tasks.
>
> Not that much differently, and the end goal (greater accuracy by
> tracking smaller tasks) is the same. We assign points to stories. Then
> each developer picks up a certain number of points per iteration to
> work on. Developers learn not to overreach over time, and you can
> track historically when stories have missed their goals, so over time
> you learn how to work better as a team.
>
> Of course, all this would be moot without the daily standups.
>
> --
> -Mark Wieder
>  ahsoftware at gmail.com
>
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>