Play 7 – Map Applications To Projects For Impact Analysis
- Difficulty: Easy to Moderate
- Target time: 4-10 weeks
- Maturity: 0 to 2
- Lack of clarity as to project impacts/dependencies
- Application catalogue
- Project List
- Engagement with Project teams/PMO
- Create strategic plans with the architecture elements they will be impacting – applications, others if feasible
- Create a project list with dates
- Tie the plans to the projects that will implement them
- By plan, you can see the projects impacting different applications, and by application, you can see the projects impacting the focus application
- Enables discussion on dependencies and mitigation
- Projects begin to work on optimal delivery schedules
- PMO – project portfolio
- Projects – project dates and architecture impacts
- Engage PMO and projects – highlight dependencies and impacts
- Engage business in how project portfolio can be reshaped to deliver quicker or at lower cost
- EA closer to the project teams, value add through dependency analysis – builds credibility with projects and a keenness to engage architects
- Credibility with the CIO as EA can demonstrate impacts on projects and dependencies, spotting potential threats to the overall project delivery
| Steps | A1.1 | S1.2 | S1.3 |
|---|---|---|---|
| What | Capture the applications with basic details and services | Define strategic plans and the applications they impact | Create the projects that will implement the strategic plans |
| Usage | Have a list of applications used that can be the anchor for the rest of the work. Define strategic applications in line with your target state | See strategic plans applications implementing them | See Projects delivering the strategic plans |
| Interested Parties and expected response | Business & IT Interested but not excited | Business & IT Interested in what is changing | CIO Visibility of the change portfolio Projects Interested because interdependencies become apparent |
| Approach | Start with Key Applications | By Programme | By Programme |