Agile Projects Estimations and Planning
2 likes346 views
The document discusses planning for fixed-price agile projects, highlighting the challenges of estimation and the importance of thorough investigation in project planning. It emphasizes the need to account for project lifecycle activities, potential change requests, and realistic cost assessments, particularly regarding code support. Recommendations include minimizing new code production and measuring time spent on code support to ensure more accurate project estimations.
Agile Projects Estimations and Planning
- 1. Planning for Fixed Price Agile projects.First step: Problem investigation.Damir TenishevPh.D, Project Manager“It’s better to step twice on an adult rake than once to a children’s…”www.ExigenServices.comJan27, 2011
- 2. Planning for FixedPrice Agile projectsContents Terms
- 3. Fixed Price Agile projects applicability
- 4. Challenge of estimation
- 5. Reasons for too optimistic estimates
- 6. How to make estimates realistic
- 7. Typical problems and approachesPlanning for FixedPrice Agile projectsTerms A fixed-pricecontract defines the scope, timing and price of a software project.
- 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.Planning for FixedPrice Agile projectsAgile projects applicability Research projects.
- 9. Lack of knowledge about product to be built.
- 10. Customer requires production as soon as possible.Fixed-price projects applicability Well-known business domain area.
- 11. High level of technology expertise on provider side.
- 12. Low risk level for initial estimation.Planning for FixedPrice Agile projectsChallengeof estimation Estimate should be done without deep investigation.
- 13. All the activities of project lifecycle should be taken into account.
- 14. Change requests aftermaths should be foreseen.Possible reasons for too optimistic estimates Most of projects activities are ignored
- 15. Background and regular activities are ignored
- 16. Code support cost is ignoredPlanning for FixedPrice Agile projectsProject activities (1) Project understanding.
- 17. Business requirements definition.
- 19. Learning customer environment.
- 21. Developing software architecture.
- 22. Preparing local development and testing environment.
- 23. Continues integration process support.
- 24. Development. Tasks clarification. Integration.
- 25. Change management.Planning for FixedPrice Agile projectsProject activities (2) Code quality insurance.
- 26. Testing and quality assurance.
- 27. Bugfixing.
- 28. User manuals preparation.
- 31. User Acceptance Testing (UAT).
- 34. Legacy data migration.Planning for FixedPrice Agile projectsBackground and regular activities Inter-project communications.
- 36. Communication with providers of third-party tools.
- 37. Development, testing and production environment support.
- 38. Human resources management. Interviews. Hiring.
- 41. Reporting.Planning for FixedPrice Agile projectsCode support We need to support written code.
- 42. One developer can support about 100K lines of code.
- 43. Support cost grows imperceptibly during project lifetime.
- 44. For 1 000 000 lines of code you need about 5 developers dedicated to support this code.Recommendations Reduce amount of produced code.
- 45. Most of new features should be implemented based on existing code.
- 46. Always measure time spend to code support.Planning for FixedPrice Agile projectsDevelopment itself takes about10% of project effort!
- 47. Planning for FixedPrice Agile projectsHOW TO MAKE YOU ESTIMATES MORE REALISTICThe penalties method Incomplete business or software requirements – 30-50%.
- 48. Indistinct requirements like user interface, performance – 20-40%.
- 49. Lack of examples or samples to verify and validate software – 10-30%.
- 50. New business domain area – 20-50%.
- 51. New tools & technologies – 20-40%.
- 52. Poorly specified execution environment – 20-30%.
- 53. New customer – 10-20%.
- 54. New team – 20-50%.Planning for FixedPrice Agile projectsTypical problems and solution approaches (1)
- 55. Planning for FixedPrice Agile projectsTypical problems and solution approaches (2)
- 56. Planning for FixedPrice Agile projects???There are no final decisionsDamir.Tenishev@exigenservices.com