So we came up with a method for predicting based on where a feature is on the 1-N list, without doing any planning on that feature whatsoever. Given that our resources were constrained in the down economy for extended periods of time, it did not make much sense for us to design a system that would show the need for hiring, so the intent of our planning process was to maximize throughput and ensure we were working through the requirements in priority order. We went to a 4-week time slice approach with our sprints (MMs) and tried to work toward user story (feature) granularity that was between two and four weeks of an engineer’s time. This enabled us to track how many user stories are delivered in each sprint. ...
- Chapter 7. Taming the Planning Beast
- from A Practical Approach to Large-Scale Agile Development: How HP Transformed LaserJet FutureSmart Firmware
- Publisher: Addison-Wesley Professional
- Released: November 2012
Note the user story granularity. To do that, they must have a good grasp of how to write and handle stories properly.
Share this highlighthttp://www.safaribooksonline.com/a/a-practical-approach/61921/