There is a phrase in agile deliver early and deliver often. Let's test this potential platitude in the enterprise and software intensive systems business
Let's look at Delivery Often. Often needs to match the business rhythm of the project or the business. This requires answers to several questions:
- How often can the business accept new features into the workflow processes?
- Do users need training for these new features? Is so, is there an undo burden on the training organization for new training sessions?
- Are there external process that need to stay in sync with these new features?
- Are there changes to data or reports as a result of these new features?
Deliver Early is more problematic
- Can the organization put the features to work?
- Are there dependencies on external connections?
So let's look at the enterprise or software intensive systems domain. How about showing up as planned. This of course means having a Plan. The picture below is an enterprise systems that has Planned capabilities in a Planned order, with Planned features.
So before subcoming to the platitudes of agile, determine the needs for successful project completion in your domain. Then ask is that platitude is actually applicable to your domain?
