Chapter 8. Unique Challenges of Estimating Large Innovations

The previous chapter provided an overview of how we estimate schedules and feature delivery in an agile environment when the system engineers can do a good job estimating the work for each team or, even better, if the requirements are broken down into two to four weeks’ worth of work for an engineer. We’ve found this works great for 80 to 90% of the features being asked for. But some features or innovations have large architectural dependencies and are much harder to predict. These initiatives typically involve a lot of discovery and prototyping, and even doing significant investigations into multiple alternatives. The biggest example is a large re-architecture effort like ours. How ...

Get A Practical Approach to Large-Scale Agile Development: How HP Transformed LaserJet FutureSmart Firmware now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.