Transformation Onboarding and Discovery Approach November 6 th, 2012

- 2 - An onboarding and discovery process has been setup to coordinate the Transformation Projects using the Application Delivery Method Components Risk / Validation Activity Deliverable Risk / Validation Activity Project BacklogTransformation Backlog LaterNext In Progress Transformation TCM Website Renewal EDW …. Project CanvasCollaborate Identify Risks / Deliverables Coordinate with Transformation Kanban 123 4

- 3 - Project Canvas Overview The canvas is a collaborative tool used to facilitate brainstorming, ideation and collaboration in elaborating the vision and scope of a project. It is the first component each project team should develop to onboard a project to the Transformation Kanban. The canvas provides the necessary information required to populate the Idea Document and Vision/Scope Document. If required, the team can extract the information from the canvas to build the above documents as deliverables. Project Canvas 1

- 4 - Collaborate with Project Canvas Overview It is recommended that the project manager organize a team workshop with Business stakeholders to develop the canvas. Typically 2 sessions are required to sufficiently populate the canvas. During the workshop, planning tasks, risks, unknowns and out-of- scope items should be identified that will be used to populate the Transformation Kanban for team stand-ups. Collaborate 2

- 5 - Identify Risks and Deliverables Overview Once the team has sufficiently developed the canvas, the tickets in the unresolved column of the canvas should be captured as risk / validation tickets that will populate the Transformation Kanban. In addition, any other risk items such as solution, scope, team / capacity, cost / benefits, etc. should be identified and a validating activity / task should be created to resolve it. The team is responsible for identifying items that impact the overall transformation and coordinating with the transformation team to hand-off the ownership of the activity. These items can be marked as orange tickets and should be moved to the Transformation Backlog. Identify Risks / Deliverables 3

- 6 - Coordinate with Transformation Overview Each project team is responsible for creating appropriate risk / validation activity tickets, tasks and deliverables on the Transformation Kanban. In addition, any items that is outside of the scope of the project but may impact the Transformation should be moved into thee Transformation Backlog (Later column within the Transformation swimlane) and represented as an orange ticket. Teams are responsible for running stand-ups at the Kanban board and coordinating with other teams as needed. Coordinate with Transformation Kanban 4