Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Managing Scope Creep in Development Projects

1,848 views

Published on

Published in: Technology, Business
  • Be the first to comment

Managing Scope Creep in Development Projects

  1. 1. Managing Scope Creep in Development Projects
  2. 2. About Me Name Dhivya Arunagiri Senior Business Analyst – Role Thoughtworks India Email dhivyaa@thoughtworks.com
  3. 3. 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!!!
  4. 4. Scope Creep is a Symptom….. Inception : 150 points Current status : 200 points My product owner is adding new features This story was a 2 pointer, but it turned out to be much more complex Oops, this flow seems incomplete
  5. 5. 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
  6. 6. For the next 45 minutes….. Issues underlying Scope Creep Visualizing from multiple perspectives Using Scope creep to advantage
  7. 7. The symptom shows up…. While playing a Project Duration story Integration Due to the Projects Product Owner
  8. 8. The symptom shows up…. While playing Project Duration a story Integration Due to the Projects Product Owner
  9. 9. While playing a story…. Feedback notcoming in during development Late feedback Re - design Scope balloons up
  10. 10. While playing a story…. Team is new to technology New Technology - More Complex than anticipated
  11. 11. While playing a story…. Dependencies/NFRs identified after dev work start
  12. 12. The symptom shows up…. While playing a Project Duration story Due to the Integration Product Owner Projects
  13. 13. Due to the Product Owner…. Pressure from Multiple Stakeholders
  14. 14. Due to the Product Owner…. Issues with conceptualising the product
  15. 15. Due to the Product Owner…. Functionality vs Frills
  16. 16. The symptom shows up…. While playing a Project Duration story] Due to the Integration Product Owner Projects
  17. 17. Project Duration factor…. Project starts much later after Inception Period between Releases is longer
  18. 18. The symptom shows up…. While playing a Project Duration story Due to the Integration Product Owner Projects
  19. 19. Failure of Contract Specifically in Data Intensive Projects
  20. 20. Workarounds… Saves time/cost but increase scope
  21. 21. Integration delays…. Filler Stories add onto Scope
  22. 22. Scope Creep – The indicator……
  23. 23. Scope Creep tells me…. Conceptualisation of the Product is wrong!!!! Back to the Basics – What are we trying to solve?
  24. 24. Scope Creep tells me…. I am talking to the wrong set of People!!!! Go to the decision maker… NOW!!
  25. 25. Scope Creep makes me think…. Can I Refine my client’s processes? Let’s try a Quick win…..
  26. 26. Scope Creep makes me think…. What is the business value of a story? Cost vs Benefit trumpcard
  27. 27. Scope Creep – Do not Manage it….
  28. 28. The Vicious Circle - Remove X, - Add Y, Attaining Steady state – NOT possible - Make sure X = Y every time But Y grows…..
  29. 29. 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
  30. 30. 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
  31. 31. Team Dynamics Pace of the team α Complexity of the Goal Scope Creep -> Unsettling -> Challenging -> Triggers Innovation
  32. 32. Q&AThank You

×