Planning for Fixed Price Agile projects.First step: Problem investigation.<br />Damir Tenishev<br />Ph.D, Project Manager<...
Planning for FixedPrice Agile projects<br />Contents<br /><ul><li>  Terms
 Fixed Price Agile projects applicability
  Challenge of estimation
  Reasons for too optimistic estimates
  How to make estimates realistic
  Typical problems and approaches</li></li></ul><li>Planning for FixedPrice Agile projects<br />Terms<br /><ul><li>  A fix...
Agilesoftware development is a group of software development methodologies based on iterative and incremental development,...
Lack of knowledge about product to be built.
 Customer requires production as soon as possible.</li></ul>Fixed-price projects applicability<br /><ul><li> Well-known bu...
High level of technology expertise on provider side.
 Low risk level for initial estimation.</li></li></ul><li>Planning for FixedPrice Agile projects<br />Challengeof estimati...
 All the activities of project lifecycle should be taken into account.
 Change requests aftermaths should be foreseen.</li></ul>Possible reasons for too optimistic estimates<br /><ul><li> Most ...
Upcoming SlideShare
Loading in …5
×

Agile Projects Estimations and Planning

986 views

Published on

Presentation by Damir Tenishev for Exigen Services webinar Agile Projects Estimations and Planning that was held online on January, 27 2011

Exigen Services webinars schedule is avialable at:
http://www.exigenservices.ru/webinars

Published in: Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
986
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
0
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Agile Projects Estimations and Planning

  1. 1. Planning for Fixed Price Agile projects.First step: Problem investigation.<br />Damir Tenishev<br />Ph.D, Project Manager<br />“It’s better to step twice on an adult rake than once to a children’s…”<br />www.ExigenServices.com<br />Jan27, 2011<br />
  2. 2. Planning for FixedPrice Agile projects<br />Contents<br /><ul><li> Terms
  3. 3. Fixed Price Agile projects applicability
  4. 4. Challenge of estimation
  5. 5. Reasons for too optimistic estimates
  6. 6. How to make estimates realistic
  7. 7. Typical problems and approaches</li></li></ul><li>Planning for FixedPrice Agile projects<br />Terms<br /><ul><li> A fixed-pricecontract defines the scope, timing and price of a software project.
  8. 8. Agilesoftware development is a group of software development methodologies based on iterative and incremental development, where requirements and solutions evolve through collaboration between self-organizing, cross-functional teams.</li></li></ul><li>Planning for FixedPrice Agile projects<br />Agile projects applicability<br /><ul><li> Research projects.
  9. 9. Lack of knowledge about product to be built.
  10. 10. Customer requires production as soon as possible.</li></ul>Fixed-price projects applicability<br /><ul><li> Well-known business domain area.
  11. 11. High level of technology expertise on provider side.
  12. 12. Low risk level for initial estimation.</li></li></ul><li>Planning for FixedPrice Agile projects<br />Challengeof estimation<br /><ul><li> Estimate should be done without deep investigation.
  13. 13. All the activities of project lifecycle should be taken into account.
  14. 14. Change requests aftermaths should be foreseen.</li></ul>Possible reasons for too optimistic estimates<br /><ul><li> Most of projects activities are ignored
  15. 15. Background and regular activities are ignored
  16. 16. Code support cost is ignored</li></li></ul><li>Planning for FixedPrice Agile projects<br />Project activities (1)<br /><ul><li> Project understanding.
  17. 17. Business requirements definition.
  18. 18. Learning technologies.
  19. 19. Learning customer environment.
  20. 20. Developing software requirements.
  21. 21. Developing software architecture.
  22. 22. Preparing local development and testing environment.
  23. 23. Continues integration process support.
  24. 24. Development. Tasks clarification. Integration.
  25. 25. Change management.</li></li></ul><li>Planning for FixedPrice Agile projects<br />Project activities (2)<br /><ul><li> Code quality insurance.
  26. 26. Testing and quality assurance.
  27. 27. Bugfixing.
  28. 28. User manuals preparation.
  29. 29. Deployment. Integration. Configuration.
  30. 30. Intermediate releases.
  31. 31. User Acceptance Testing (UAT).
  32. 32. Integration Testing.
  33. 33. Support. Users teaching.
  34. 34. Legacy data migration.</li></li></ul><li>Planning for FixedPrice Agile projects<br />Background and regular activities<br /><ul><li> Inter-project communications.
  35. 35. Cross-domain communications.
  36. 36. Communication with providers of third-party tools.
  37. 37. Development, testing and production environment support.
  38. 38. Human resources management. Interviews. Hiring.
  39. 39. Education, professional development.
  40. 40. Regular scrum meetings.
  41. 41. Reporting.</li></li></ul><li>Planning for FixedPrice Agile projects<br />Code support<br /><ul><li> We need to support written code.
  42. 42. One developer can support about 100K lines of code.
  43. 43. Support cost grows imperceptibly during project lifetime.
  44. 44. For 1 000 000 lines of code you need about 5 developers dedicated to support this code.</li></ul>Recommendations<br /><ul><li> Reduce amount of produced code.
  45. 45. Most of new features should be implemented based on existing code.
  46. 46. Always measure time spend to code support.</li></li></ul><li>Planning for FixedPrice Agile projects<br />Development itself <br />takes about10% <br />of project effort!<br />
  47. 47. Planning for FixedPrice Agile projects<br />HOW TO MAKE YOU ESTIMATES MORE REALISTIC<br />The penalties method<br /><ul><li> Incomplete business or software requirements – 30-50%.
  48. 48. Indistinct requirements like user interface, performance – 20-40%.
  49. 49. Lack of examples or samples to verify and validate software – 10-30%.
  50. 50. New business domain area – 20-50%.
  51. 51. New tools & technologies – 20-40%.
  52. 52. Poorly specified execution environment – 20-30%.
  53. 53. New customer – 10-20%.
  54. 54. New team – 20-50%.</li></li></ul><li>Planning for FixedPrice Agile projects<br />Typical problems and solution approaches (1)<br />
  55. 55. Planning for FixedPrice Agile projects<br />Typical problems and solution approaches (2)<br />
  56. 56. Planning for FixedPrice Agile projects<br />?<br />?<br />?<br />There are no final decisions<br />Damir.Tenishev@exigenservices.com<br />

×