Architecture Planning Process

Quarterly Team Planning Process

Brainstorm a list of Architecture tasks that need to be completed across every area
Prioritize the most important Architecture tasks that need to be accomplished that have the biggest impact to business outcomes
Define what can be done within the next 90 days based on resource capacity and skills
Determine if additional resources need to be brought in to accomplish the work
Identify what we are going to stop doing - be intentional

Ensure that the leadership and employees are up to the task of taking on strategy work - or - it will stall out

Embed team members into the working groups [business areas] once you know the strategy and have a solid handle on where you are taking the team

At some point you will want to get everyone in a room - and yet - stay disciplined - don't do it until you have a handle on key components:

One-on-one with leadership and what their expectations are along with their top 3-5 priorities for the next year / three years
Don't underestimate the people - if you don't have the right team engagement - actions will stall out - and - it will take a lot more time to rebuild the impetus behind the effort and you will lose MORE time than if you took your time building momentum - see "Leading Change" above
During the offsite you can come prepared with a summary of:
- The questions that you asked
- Priorities across the organization
- Drafted Winning Aspiration
- Basic inventory of applications

Point of Arrival (Offsite) Process - Overview
Point of Arrival (Offsite) - Template
Review the summary of the questions that were asked - your viewpoint on them
Top priorities and your views on those
Review the approach of Playing to Win - and - the draft of the Winning Aspiration
Take Action:
- Build out an application communication diagram [Michael needs to provide a template]
- Categorize the application portfolio across the Application Value Lifecycle

Google Sites

Report abuse