The potential downside of not having the true technical experts in the organization proactively looking at new requests coming in is that some of the features may not fit with the current architecture or may be so much work within the architecture that it would be impossible to deliver them anytime soon. So once per quarter (plus real-time as needed), the system engineer sits down with the appropriate architect for each area and they briefly walk through the Input Queue and assign architectural risk and effort level (low/med/high/extreme) to each requirement. No work breakdown and no mapping to individual resources is done, so no real planning is done, either. What is created is familiarity with the list and any long-...
- 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/