Tami Deakins Kendall Norris Walk the Wall Big project with multiple threads and interwoven dependencies across multiple functions Delivery teams making unfounded assumptions ID: 136176
Download Presentation The PPT/PDF document "Walk the Wall" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
Walk the Wall
Tami Deakins
Kendall NorrisSlide2
Walk the WallBig 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 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.
Here’s your solution!Slide3
Presentation Flow
Activity
Presenter
TimingWelcome and Kendall Introduction Kendall3 minSession OverviewKendall2 minTami Intro and Explain the processTami15 minLive demoLeader is at the end of the RowFoundation
Framing
Plumbing
Roofing
Create 3 high level milestones
Each lead explains & puts on wall
ID dependencies
Adjust timing
Tami/Kendall
30 min
10 min
15 min
5 min
5 min
Discuss
observations
Kendall
5 minSlide4
Walk the Wall Session OverviewSlide5
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 long750,000 sq ft800 guest roomsGrand Ballroom2 Large lecture halls35 classroomsTeam RoomsFull service diningVideoconference facilities
500 employees
Project Planning
15 main delivery threads
Untold sub threads
Discovery – Deloitte UniversitySlide6
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 mitigationApplications Mergers and Acquisitions Real Estate
Data Center Migrations
Mega Programs
Multi-functional, multi-stakeholder management
Any
project
with multiple delivery streams and inter- dependenciesSlide7
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 dependenciesDesired 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
‘
Walk
the
Wall
’
Objectives
Slide8
PreparationSlide9
Expectations:Everyone’s active participation is
essential
Will concentrate on
cross-functional alignmentWill identify and resolve as many discrepancies as possible “on the fly”Perfection is not the goalOur target is 80-90% alignment and a clear path to 100%If we bog down on an issue, we will log actions and move onActively participate but also carefully consider comments that might cause group churnFocus on launch readiness Our primary focus is an aligned plan leading up to launchMilestones for post-launch should be covered during a later session
Walk
the
Walls
ExpectationsSlide10
Process for a Walk the Wall Session
Teams will represent the delivery threadsSlide11
Start Date
End 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 jeopardizedSlide12
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.
May
June
July
Aug.
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
4
5
6
7
8
2
3
2
1
2
1
2
1
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’ Dependency
‘Broken’ Dependency
IllustrativeSlide13
Actual “Walk
the Wall” WallSlide14
Workshop OutputCross-Team Dependencies Worksheet
IllustrativeSlide15
IllustrativeSlide16
Workshop Output:
Consolidated Roadmap
IllustrativeSlide17
Let’s Build a HouseLook 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 HouseLeader is at the end of the RowFoundationFramingPlumbing RoofingCreate 3 high level milestones
Thread Presentations
ID dependencies – use the ribbon
Adjust dependencies – resolve btw teams
30 min
5 min
15 min
min
5 minSlide18
ObservationsSlide19
Thank YouSlide20
Start Date
End 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 jeopardizedSlide21
End Date
Name of Your Team
(ID#) Milestone Description
Milestone WorksheetDependent 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 Identifier
Milestone
Start Date
End date
Dependency