LiveCode and SCRUM tools

Geoff Canyon gcanyon at gmail.com
Sat Jan 4 17:52:22 EST 2014


Agreed, velocity, turndown, etc. are very useful.

All I meant by managed backlog is that you need to understand the items in
the backlog well enough to prioritize and construct the next sprint, and
possibly trade-off items during sprints if it comes up, etc.


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

> Geoff-
>
> Saturday, January 4, 2014, 6:29:27 AM, you wrote:
>
> > Scrum: time-based sprints, with release and review/planning in between
> > them; some form of scrum-master who runs stand-ups; a managed backlog; a
> > defined process for substituting requirements during a sprint.
>
> This may well fall under the category of "managed" backlog, but I've
> found that tracking developer velocity is a great feature for keeping
> schedules from slipping. It helps the developers, the scrum master,
> and the project manager size tasks properly and know when and where to
> apply more resources.
>
> --
> -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
>



More information about the use-livecode mailing list