O'Reilly logo
  • Giovanni Asproni thinks this is interesting:

The first difference in our planning approach now is that with a common code base that is architected for scalability, and with a highly automated and simple integration and qualification system, we can separate out “get a hardware product out the door” from “deliver a set of features on that product.” Turning out a new hardware product goes much more smoothly and is now done much earlier than before. With quarterly releases, the products pick which release train they need to get on to support the schedule. If they don't believe they have a rich enough feature set, they wait for the next release, but they can go out the door on time from a firmware dependency viewpoint. Any slip is due to their...


Cover of A Practical Approach to Large-Scale Agile Development: How HP Transformed LaserJet FutureSmart Firmware


Note the user story granularity. To do that, they must have a good grasp of how to write and handle stories properly.