> * When a card is decomposed at a Connect, the resulting engineering > blueprints are placed in a backlog. > * At the start of each month blueprints are taken from the backlog > and assinged. > * At the end of each quarter anything that remains on the backlog is > assessed, and dropped or moved to another quarter.
Correct! > Can this scheme work well if we don't have a priority ordered backlog > per-team, and only have one per-project? Could it work? Yes, you'd have to split out work by month. However it won't be as easy as the method infrastructure is doing now. I think a better question is "for the work we are doing for ourselves and others that is not directly related to a roadmap card, do we need to contain the work into monthly BPs?" My reply would be, do we? No. Should we? Yes we should try so that everyone is following the same path. Infrastructure is really the odd ball group in that it doesn't source many of the requirements from the Roadmap but instead via a stakeholders team. I think Infrastructure piloting an ordered backlog would be easy and take less time than this email thread. Especially since you're only talking about very, very few pieces of work. And since Infrastructure is the exception, you can start by just targeting (in LP) the larger items out to the month in which you expect to land them vs chunking them out (initially) into monthly deliverables. That said, Alexander may want you to try and fit into the scheme used by everyone else and I would be very supportive of that. You can always run an experiment to see if it works. Determine the speed bumps and then try to mitigate them. J _______________________________________________ Mailing list: https://launchpad.net/~linaro-project-management Post to : [email protected] Unsubscribe : https://launchpad.net/~linaro-project-management More help : https://help.launchpad.net/ListHelp
