Managing Scope Creep in Development Projects
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Managing Scope Creep in Development Projects
About Me
Name Dhivya Arunagiri
Role Senior Business Analyst – Thoughtworks India
Email [email protected]
Wiki says…. Scope creep occurs when the scope of a project is not properly
defined, documented, or controlled.
It is generally considered a negative occurrence and should be
avoided.
Scope Creep = A Disease ? NO!!!
Scope Creep is a Symptom….. Inception : 150 points
Current status : 200 points
This story was a 2 pointer, but it turned
out to be much more complex
Oops, this flow
seems incomplete
My product owner is
adding new features
In Practice….
Scope Creep refers to an increase in scope compared what
was originally agreed upon.
It is an indicator that the project may not be delivered on
time, with the current set of features with the original cost
agreed upon.
Scope Creep always points to a Deeper Issue
For the next 45 minutes…..
Issues underlying Scope Creep
Visualizing from multiple perspectives
Using Scope creep to advantage
The symptom shows up….
Integration Projects Due to the
Product Owner
Project Duration While playing a story
The symptom shows up….
Integration Projects Due to the
Product Owner
Project Duration While playing a story
While playing a story….
Late feedback
Re - design
Scope balloons up
Feedback not coming in during
development
While playing a story….
New Technology - More Complex than
anticipated
Team is new to technology
While playing a story….
Dependencies/NFRs identified after dev
work start
The symptom shows up….
Integration Projects
Due to the Product Owner
Project Duration While playing a story
Due to the Product Owner….
Pressure from Multiple Stakeholders
Due to the Product Owner….
Issues with conceptualising the
product
Due to the Product Owner….
Functionality vs Frills
The symptom shows up….
Integration Projects
Due to the Product Owner
Project Duration While playing a story]
Project Duration factor….
Project starts much later after Inception
Period between Releases is longer
The symptom shows up….
Integration Projects
Due to the Product Owner
While playing a story
Project Duration
Failure of Contract
Specifically in Data Intensive Projects
Workarounds…
Saves time/cost but increase scope
Integration delays….
Filler Stories add onto Scope
Scope Creep – The indicator……
Scope Creep tells me….
Conceptualisation of the Product is
wrong!!!!
Back to the Basics – What are we trying to
solve?
Scope Creep tells me….
I am talking to the wrong set of
People!!!!
Go to the decision maker… NOW!!
Scope Creep makes me think….
Can I Refine my client’s processes?
Let’s try a Quick win…..
Scope Creep makes me think….
What is the business value of a story?
Cost vs Benefit trumpcard
Scope Creep – Do not Manage it….
The Vicious Circle
- Remove X,
- Add Y,
- Make sure X = Y
But Y grows…..
Attaining Steady state – NOT possible
every time
Inception is NOT a complete analysis process ….
Release Plan (60 - 80% confidence)
Change in assumption Conversation with the client
Scope Management should not nip conversations
Velocity/Points….
May not reflect the true status of the project
Client immersed in points focus shift from the project goal
Measurement Scales are not to be
considered alone
Team Dynamics
Pace of the team α Complexity of
the Goal
Scope Creep -> Unsettling
-> Challenging
-> Triggers Innovation
Q&A
Thank You
Related Documents
