For nearly every client, when asked if they have a launch date in mind the answer is always ASAP. What clients do not understand is the cause and effect of ASAP. During this session we will have an open discussion surrounding the following topics:
- How to set client expectations around deadlines
- The cause and effect of missed dates
- The benefits of planning and working in a cushion
- How to become focused on quality not on hours
- Removing the term hours from your vocabulary
- Lessons learned from past experiences
Managing Project Expectations with a Realistic Timeline
1. A Date is a Date
Managing Internal and External Expectations
2. Failure is common
Nearly 70% of projects are
late, over budget, or don’t meet
expectations.
3. Never trust a salesman
● Sales team job: Bring in new
business. No matter what.
● DPM’s job: See past the story that
sales has painted and determine
from the very beginning a clearly
defined scope and timeline.
● Without clearly defined goals, how
do you know what to deliver and
when?
4. Define expectations from the start
● Separate the wants vs the
needs.
● Get the right info by asking
the right questions.
● Build a [Realistic] Timeline.
7. Plan with a cushion in mind
● Set an artificial soft deadline in advance of the stated deadline as a target date
for completion.
● Allow more cushion for the higher the degree of uncertainty and complexity of the
project.
THE 1.5 RULE
Client Estimate = Your Estimate X 1.5
8. Divide and Conquer
● List out your features
● Break the whole project into
smaller pieces
● Identify the problem child -
handle it first
● Take control
10. Over Communicate.
Over Communicate.
Over Communicate.
● Be a solid communicator.
● Call first, e-mail second.
● Raise risks and concerns to your
client.
● Don’t run a project base on
scope hope.
15. Where did it all go wrong?
❏ Poor Planning
❏ No time for design
❏ Unclear goals and objectives
❏ Lack of understanding
❏ Objectives changing during the
project
❏ Unrealistic time or resource
estimates
❏ Lack of executive support and
user involvement
❏ Failure to communicate
❏ Failure to act as a team
❏ Inappropriate skills
❏ Lack of Quality management
16. Learn from mistakes
● Band-Aids or major surgery?
● How did “it” happen and how can we keep it from
happening again?
● Poor planning or execution?
● Resist assigning blame.
18. Always remember ...
“There is a great difference between knowing and understanding: you can know a lot about something
and not really understand it.”
Charles Kettering
Editor's Notes
Determine the exact deadline for the project’s completion.
When is the project due?
Is this a firm or flexible deadline?
Are there several deadlines for aspects of the project or is there just one for the overall project?
Who from your team has final say?
Ask the client what is driving their deadline?
Is this a hard deadline?
Can you deliver in phases?
Is this an arbitrary date
Accepting a deadline is a commitment. It’s a promise.
Estimate a project completion date for the entire project.
Set an artificial soft deadline in advance of the stated deadline as a target date for completion.
Allow more cushion for the higher the degree of uncertainty and complexity of the project
Divide the project into several phases if necessary.
don’t miss the warning signs
if you over hear a team members talking about the project is failing, bring it up to them.