Slide 1

Walk the Wall Tami Deakins Kendall Norris

Slide 2

Walk the Wall Big project with multiple threads and interwoven dependencies across multiple functions ? Delivery teams making unfounded assumptions ? Align your teams and project schedule using this interactive technique that will produce the synergy youre seeking along with light bulb moments. Join us and learn how to Walk the Wall with your project team to produce the plan that will maximize project execution. Heres your solution!

Slide 3

Presentation Flow ActivityPresenterTiming Welcome and Kendall IntroductionKendall3 min Session OverviewKendall2 min Tami Intro and Explain the processTami15 min Live demo Leader is at the end of the Row Foundation Framing Plumbing Roofing Create 3 high level milestones Each lead explains & puts on wall ID dependencies Adjust timing Tami/Kendall30 min 10 min 15 min 5 min Discuss observationsKendall5 min

Slide 4

Walk the Wall Session Overview Review process Applicable situations Preparation Process Live demo Select threads Identify milestones Get to the Wall Address dependencies Observations Thoughts Questions

Slide 5

Deloitte University is a $300M training base, conference center and world-class hotel all in one. And it went from breaking ground to hosting guests in 2 short years. Highlights: One third mile long 750,000 sq ft 800 guest rooms Grand Ballroom 2 Large lecture halls 35 classrooms Team Rooms Full service dining Videoconference facilities 500 employees Project Planning 15 main delivery threads Untold sub threads Discovery Deloitte University

Slide 6

Benefits of the Walk the Wall Session Facilitation for the sharing of deliverables and timing across delivery threads. Goal : identification and understanding of dependencies. Result : Risk mitigation Applications Mergers and Acquisitions Real Estate Data Center Migrations Mega Programs Multi-functional, multi-stakeholder management Any project with multiple delivery streams and inter- dependencies

Slide 7

Objectives: Review and confirm list of key milestones for each delivery thread Identify key cross team dependencies and eliminate any duplication Update roadmap with latest milestones and dependencies Desired End State: Understand the key dates and milestones for each delivery thread in order to create a consolidated roadmap outlining cross-team dependencies Out of Scope: Reviewing every single milestone and task (current focus is 10-15 most critical by workstream) Focusing on post-launch milestones and dependencies WalktheWallObjectives Walk the Wall Objectives

Slide 8

2 weeks out Instruct teams on objectives, process and preparation needs together Set deadlines Provide materials to create In person 1 week out Collect materials Review for gaps 1 day out Prep the milestones Prep the room: Put the grid on the wall Preparation

Slide 9

Expectations: o Everyones active participation is essential Will concentrate on cross-functional alignment Will identify and resolve as many discrepancies as possible on the fly Perfection is not the goal o Our target is 80-90% alignment and a clear path to 100% If we bog down on an issue, we will log actions and move on Actively participate but also carefully consider comments that might cause group churn o Focus on launch readiness Our primary focus is an aligned plan leading up to launch Milestones for post-launch should be covered during a later session WalktheWallsExpectations Walk the Walls Expectations

Slide 10

Process for a Walk the Wall Session Identify Milestones Each team will have create milestone cards Post milestones on the wall Logistics Set the time limit for each thread Reiterate information regarding Day 1 vision, Day 1 experience, etc. in the context of your milestones Audience Participation Add milestones based on presentations Record dependencies for use during walk the wall Discuss new milestones at end of presentations Identify Interdependencies Use ribbon to connect interdependent milestones Red ribbon for broken dependencies Green ribbon for aligned dependencies Align Interdependencies Fix broken milestones to achieve aligned, integrated milestone roadmap Teams will represent the delivery threads

Slide 11

Start DateEnd Date Name of Your Team (ID#) Milestone Description Milestone Cards Dependent Function (if applicable) Mandatory information required for each milestone: Milestone Definition: A milestone represents the deadline/date for a key deliverable, group of related tasks or 'gate' approval meeting that must be met in order for the work to progress. Milestones should be written in a sentence so that those outside of your workstream can understand it, and is important enough that if not completed, the success of your workstream and/or the success of the program would be jeopardized

Slide 12

DRAFT Walk the Wall Wall NOTE: Wall is not to scale, some workstreams may have larger swimlanes WorkstreamSep.Oct.Nov.Dec.Jan.Feb.Mar.Apr.MayJuneJulyAug.Sept. ITS Systems Integration HR Policies & Procedures Operations Communications Transportation Finance Health & Fitness Talent Development Scheduling Meeting Services Security Culture Green Operations Guest Experience 1 1 1 1 1 1 1 2 2 2 2 2 2 5 2 2 3 45 678 2 3 21 21 21 1 1 1 2 3 3 2 3 3 3 3 3 3 9 4 6 3 1 4 3 2 # # Functional Milestone Infrastructure Milestone Aligned DependencyBroken Dependency

Slide 13

Actual Walk the Wall Wall

Slide 14

Workshop Output Cross-Team Dependencies Worksheet

Slide 15

Slide 16

Workshop Output: Consolidated Roadmap

Slide 17

Lets Build a House Look at your rows you have a delivery thread Person at the end of the row is the team leader - theyll represent your thread in the presentation Create 3 key milestones and their timing NOTE: dont actually try to build a house this is just an exercise Build a House Leader is at the end of the Row Foundation Framing Plumbing Roofing Create 3 high level milestones Thread Presentations ID dependencies use the ribbon Adjust dependencies resolve btw teams 30 min 5 min 15 min min 5 min

Slide 18

Observations

Slide 19

Thank You

Slide 20

Start DateEnd Date Name of Your Team (ID#) Milestone Description Milestone Cards Dependent Function (if applicable) Mandatory information required for each milestone: Milestone Definition: A milestone represents the deadline/date for a key deliverable, group of related tasks or 'gate' approval meeting that must be met in order for the work to progress. Milestones should be written in a sentence so that those outside of your workstream can understand it, and is important enough that if not completed, the success of your workstream and/or the success of the program would be jeopardized

Slide 21

End Date Name of Your Team (ID#) Milestone Description Milestone Worksheet Dependent Function (if applicable) Mandatory information required for each milestone: Milestone Definition: A milestone represents the deadline/date for a key deliverable, group of related tasks or 'gate' approval meeting that must be met in order for the work to progress. Milestones should be written in a sentence so that those outside of your workstream can understand it, and is important enough that if not completed, the success of your workstream and/or the success of the program would be jeopardized Team Milestone IdentifierMilestoneStart DateEnd dateDependency