A typical application delivery progresses through:
- Business requirements capture
- IT requirements mapping
- Development lifecycle
The longer you take to progress through these steps leaves you more open to impacts and risk by requirements change and incorrect interpretation of the requirements. Shorter timescales allow independent contracts to be delivered and made visible early to mitigate the risks.
Move from application delivery to contract delivery.
Questions to ask yourselves
- How long is a typical development project?
- Are Service Level Agreements (SLAs) defined before delivery commences?
- Do you have measurable contracts between the Business and IT?
At ProSolveIT, we see a number of Themes that must be addressed in any EA approach – Click here for more information!