linaro-project-management team mailing list archive
-
linaro-project-management team
-
Mailing list archive
-
Message #00312
Re: Toolchain's method
Hi Michael,
Nice details.
Might I suggest you consider
1) dropping "todo"? When you assign something it moves from backlog to
in-progress.
2) only assigning items to people when they are free to work on them
(this is a bit harder). Pragmatically you have to assign (or target)
a few items for each person each month so they know what to work on.
This would simplify your working model.
An alternative approach is to split the backlog lane into two:
unassigned and assigned. Then you'd have backlog, in-progress, done,
blocked, postponed. In progress again would show only the stuff that
folks are actively working on.
J
On Sun, Aug 14, 2011 at 9:11 PM, Michael Hope <michael.hope@xxxxxxxxxx> wrote:
> I've updated how I plan to implement monthly planning in Toolchain:
> https://wiki.linaro.org/MichaelHope/Sandbox/MonthlyImplementation
>
> and done a mock up of a Kanban-style view:
> http://ex.seabright.co.nz/helpers/backlog
>
> This view shows that we're not very good at finishing things. One
> reason is that the blueprints are too big and have dregs that take a
> while to finish up. Splitting them will help. I'm also going to go
> through and deallocate blueprints from people's queue to get them into
> the backlog.
>
> I wrote this up as I don't understand how we're going to implement the
> current ideas. Any thoughts?
>
> -- Michael
>
> _______________________________________________
> Mailing list: https://launchpad.net/~linaro-project-management
> Post to : linaro-project-management@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~linaro-project-management
> More help : https://help.launchpad.net/ListHelp
>
Follow ups
References