How do you get people to do what they say they are going to do?

Slides:



Advertisements
Similar presentations
Last Planner ® National Capital Region Community of Practice Victor Sanvido – Southland Industries Matt Bruening – Southland Industries 1.
Advertisements

Agile development By Sam Chamberlain. First a bit of history..
Change is a Process Organizational Stages Individual Stages (ADKAR) Business Need Concept and Design Implementation Post-Implementation Awareness Desire.
Sharif University of Technology Session # 4.  Contents  Systems Analysis and Design Sharif University of Technology MIS (Management Information System),
Last Planner: A Case Study in Learning from Anomalies and Breakdowns Glenn Ballard Nottingham Trent University May 7, 2014.
Trusted IT Group. The challenge: 40 active, concurrent IT projects  Unsatisfactory Project Delivery.
© 2011 AT&T Intellectual Property. All rights reserved. AT&T, the AT&T logo and all other AT&T marks contained herein are trademarks of AT&T Intellectual.
1 ISA&D7‏/8‏/ ISA&D7‏/8‏/ ISA&D7‏/8‏/2013 IS Projects: Success and Failure Role of the Project Manager Project Management Tasks in SDLC.
AP-1 5. Project Management. AP-2 Software Failure Software fails at a significant rate What is failure? Not delivering it on time is an estimation failure.
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 What is Solution Assessment & Validation?
1 TenStep Project Management Process ™ PM00.9 PM00.9 Project Management Preparation for Success * Manage Quality *
Introducing Project Management Update December 2011.
® IBM Software Group © 2006 IBM Corporation PRJ480 Mastering the Management of Iterative Development v2 Module 7: Iteration Management.
Project Management. Projects and Project Managers Project – a [temporary] sequence of unique, complex, and connected activities having one goal or purpose.
Class 5 – Planning IT Projects
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
If you can’t say “no”, you can’t make a promise
The Continuum of Interventions in a 3 Tier Model Oakland Schools 3 Tier Literacy Leadership Team Training November
Project Management A Practical Approach Sridhar Pandurangiah Director - Engineering Sridhar Pandurangiah Director - Engineering.
Risk management Here’s my section for risk management! ~ Christopher Thornton.
Time Management.
Time Management.
AP CSP: Sending Binary Messages with the Internet Simulator
BUSINESS PLUG-IN B15 Project Management.
Wael Ellithy, Ph.D. Arx ICT
Creating Our Common Wealth Supporting the Growth of Others
The Continuum of Interventions in a 3 Tier Model
Adapted from PPT developed by Jhpiego corporation
Project Management Processes
4.05 Time Management.
Lean construction ireland deliver projects better, faster, together
IMPACT HIRING #4 – Creating Success from the Start
Customer experience loop
Project Management Lifecycle Phases
Mike Cohn - Agile Estimating and Planning
[Project Name] Post-Mortem
12 Steps to Useful Software Metrics
Models of Software Development Life Cycle (SDLC)
Weekly Network Call LSW Weekly DC Leader Call LSW
PROJECT NAME POST-MORTEM
The value of a project-oriented approach to IT and how we do it in IBM
Taking an Iteration Down to Code
IT Systems Analysis & Design
2018 CompTIA PK0-004 Study Guide Killtest
Requirement Engineering - Customer-Oriented
How to Successfully Implement an Agile Project
Phillip Steele Software Development Team Lead Sage
Quality Department
Eliminating the Variance
Frameworks in project management
Sprint Planning April 2018.
Quality Assurance in an Agile Development Team Michelle Wu 2018 PNSQC
Project Management Processes
[Project Name] Post-Mortem Presentation Template
Project Name Post-Mortem
M253 Team working in distributed environments
Project Management How to access the power of projects!
Principles of Customer Service
Interviewing Sriram Mohan.
KNOWLEDGE MANAGEMENT (KM) Session # 36
Manage testing by time boxes
Software Maintenance Part1 Introduction. Outlines What Is Software Maintenance Purposes of Maintenance Why We Need It Maintenance Difficilties Some Tips.
Conscious Competence Ladder: Debrief
Conscious Competence Ladder: Debrief
Executive Project Kickoff
Customer experience loop
SD5953 Successful Project Management AGILE SOFTWARE DEVELOPMENT
Driving Successful Projects
CSCI 360: Software Architecture & Design
Process improvement for the lab
Presentation transcript:

How do you get people to do what they say they are going to do? Christine Pasquire & Paul Ebbs

Purpose of the session: To better understand why plans fail,

IF I WANT IT DOING PROPERLY I HAVE TO DO IT MYSELF! IT’S DIFFICULT TO GET THE RIGHT THINGS IN THE RIGHT PLACE AT THE RIGHT TIME CLIENTS ALWAYS CHANGE THEIR MINDS WE HAVE TO MAKE SAVINGS DESIGN IS AN ITERATIVE PROCESS PROJECTS HAVE TO RESPOND TO CHANGING CIRCUMSTANCES NO RISK IS NOT AN OPTION ADMIN GETS IN THE WAY COMPANIES LOOK AFTER THEIR OWN INTERESTS WE HAVE TO RETENDER TO MAKE SAVINGS CONSTRUCTION IS UNCERTAIN PROJECTS ARE COMPLEX I DON’T HAVE ENOUGH POWER PEOPLE MISUNDERSTAND DESIGN INFORMATION IS ALWAYS LATE OTHER THINGS COME ALONG I DON’T HAVE TIME TO DO EVERYTHING PEOPLE KEEP CHANGING

Purpose of the session: To better understand why plans fail, To introduce systematic approaches to improve reliability.

Purpose of the session: To better understand why plans fail, To introduce systematic approaches to improve reliability. What’s that got to do with what people say/do?

Purpose of the session: To better understand why plans fail, To introduce systematic approaches to improve reliability. Why should we be interested in what people say/do? Because people make & execute plans………

As many as you like, there is no wrong answer! Let’s explore why people don’t do what they say they will, when they say they will. Break into groups of 2 – 3 people Discuss and debate reasons Write answers, one per post-it As many as you like, there is no wrong answer! 5 Minutes

5 Rules to help you do what you plan on doing

5 Rules to help you do what you plan on doing Understand what your “next” customer actually wants (shared understanding) 5 Rules to help you do what you plan on doing

Who is your customer?

Who is your customer? Client and/or end user? The world and society we live in? Your “next” customer in line?

Who is your customer? Client and/or end user? The world and society we live in? Your “next” customer in line?

Who is your customer? Client and/or end user? The world and society we live in? Your “next” customer in line?

5 Rules to help you do what you plan on doing Understand what your “next” customer actually wants (shared understanding) 5 Rules to help you do what you plan on doing AND WHAT YOU REQUIRE AS THE CUSTOMER OF THE PREVIOUS TASK

Who is your supplier?

The world and society we live in? Who is your supplier? Another company? The world and society we live in? Another person?

The world and society we live in? Who is your supplier? Another company? The world and society we live in? Another person?

5 Rules to help you do what you plan on doing Understand what your “next” customer actually wants (shared understanding) Assess competency beforehand (skills) 5 Rules to help you do what you plan on doing

5 Rules to help you do what you plan on doing Understand what your “next” customer actually wants (shared understanding) Assess competency beforehand (skills) Ensure capacity is available (resources) 5 Rules to help you do what you plan on doing

5 Rules to help you do what you plan on doing Understand what your “next” customer actually wants (shared understanding) Assess competency beforehand (skills) Ensure capacity is available (resources) Refuse “last minute requests” (fire-fighting) 5 Rules to help you do what you plan on doing

5 Rules to help you do what you plan on doing Understand what your “next” customer actually wants (shared understanding) Assess competency beforehand (skills) Ensure capacity is available (resources) Refuse “last minute requests” (fire-fighting) Accept responsibility for failure (culture) 5 Rules to help you do what you plan on doing

Understand what your “next” customer actually wants (shared understanding) Assess competency beforehand (skills) Ensure capacity is available (resources) Refuse “last minute requests” (fire-fighting) Accept responsibility for failure (culture)

Say no!

Say no! Why?

Which of these are reliable? I will… I’ll try… That’s the plan… Should do… Fingers crossed… I will by Tuesday at noon... I think so... I will do that if...

Conditions of Satisfaction Cycle

”What makes that a yes or a no?” Countermeasure ”What makes that a yes or a no?”

Milestone Pull Planning Creating and maintaining reliable workflow As Needed Milestone Pull Planning Define Milestones (30,000’) - Master schedule - Establishes promise of the project - Set phase durations & overlaps - Identify project constraints Should Action Learning Phase Pull Planning Phase Schedules (10,000’) - Collaboratively built phases (3-4 months) - Focus on handoffs & Conditions of Action Learning Satisfaction of processes within phases Look-ahead Window (6 – 8 weeks) Make Work Ready (1,000’) Preparing for flow Identify constraints Commitments to remove constraints Constraint Log Can Make-Ready Planning Action Learning Commitment Planning Weekly Work Plan (100’) - Reliable promising - Only constraint free (sound) tasks - Tasks are well defined, sound, sequenced Will Action Learning Weekly & sized to match available capacity Daily Coordination (10’) - Rapid learning & adjustment to constraints - Capture Metrics Percentage of Promises Completed (PPC) Reasons for Missed Commitments (RMC) Did Daily Huddles Action Learning Learning & Action Root Cause Analysis - 5 Whys - Take action at appropriate level to prevent Learn Action Learning reoccurrence (PDCA) Creating and maintaining reliable workflow

Milestone Pull Planning Creating and maintaining reliable workflow As Needed Milestone Pull Planning Define Milestones (30,000’) - Master schedule - Establishes promise of the project - Set phase durations & overlaps - Identify project constraints Should Action Learning Phase Pull Planning Phase Schedules (10,000’) - Collaboratively built phases (3-4 months) - Focus on handoffs & Conditions of Action Learning Satisfaction of processes within phases Look-ahead Window (6 – 8 weeks) Make Work Ready (1,000’) Preparing for flow Identify constraints Commitments to remove constraints Constraint Log Can Make-Ready Planning Action Learning Commitment Planning Weekly Work Plan (100’) - Reliable promising - Only constraint free (sound) tasks - Tasks are well defined, sound, sequenced Will Action Learning Weekly & sized to match available capacity Daily Coordination (10’) - Rapid learning & adjustment to constraints - Capture Metrics Percentage of Promises Completed (PPC) Reasons for Missed Commitments (RMC) Did Daily Huddles Action Learning Learning & Action Root Cause Analysis - 5 Whys - Take action at appropriate level to prevent Learn Action Learning reoccurrence (PDCA) Creating and maintaining reliable workflow

What have you heard in this session? (your take aways)

THANK YOU!