Walk the Wall Tami Deakins Kendall Norris Walk

Walk the Wall Tami Deakins Kendall Norris

Walk the Wall • Big project with multiple threads and interwoven dependencies across multiple functions? • Delivery teams making unfounded assumptions? Here’s your solution! • Align your teams and project schedule using this interactive technique that will produce the synergy you’re 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.

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

Discovery – Deloitte University is a $300 M training base, conference center and worldclass 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

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

‘ Walk the Wall Objectives ’ 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

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

Walk the Walls Expectations: o Everyone’s 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

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 Teams will represent the delivery threads 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

Milestone Cards Mandatory information required for each milestone: Start Date End Date (ID#) Milestone Description Name of Your Team Dependent Function (if applicable) 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

DRAFT “Walk the Wall” Wall Workstream Sep. Oct. Nov. Dec. Jan. 1 ITS Feb. 2 Systems Integration 1 HR Policies & Procedures 1 2 Mar. Apr. May June Aug. Sept. 4 3 3 4 5 6 7 8 9 2 Operations 3 1 2 Communications 2 Transportation Finance 1 u l Il Health & Fitness 1 Talent Development 1 Scheduling e v 3 1 r t s i t a 4 5 1 2 3 2 Security 1 Culture 2 3 1 2 Green Operations 2 Guest Experience 1 # Functional Milestone # Infrastructure Milestone 6 3 1 Meeting Services July 3 3 2 3 ‘Aligned’ Dependency ‘Broken’ Dependency NOTE: ‘Wall’ is not to scale, some workstreams may have larger swimlanes

Actual “Walk the Wall” Wall

Workshop Output Cross-Team Dependencies Worksheet u l Il r t s i t a e v

u l Il r t s i t a e v

Workshop Output: Consolidated Roadmap u l Il r t s i t a e v

Let’s Build a House • Look at your rows – you have a delivery thread • Person at the end of the row is the team leader - they’ll represent your thread in the presentation • Create 3 key milestones and their timing NOTE: don’t 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

Observations

Thank You

Milestone Cards Mandatory information required for each milestone: Start Date End Date (ID#) Milestone Description Name of Your Team Dependent Function (if applicable) 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

Milestone Worksheet Mandatory information required for each milestone: End Date Milestone Identifier Team Milestone Start Date End date Dependency (ID#) Milestone Description Name of Your Team Dependent Function (if applicable) 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