Your SlideShare is downloading. ×
Planning for Fixed Price Agile projects. Second step_Problem investigation.
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Planning for Fixed Price Agile projects. Second step_Problem investigation.

583
views

Published on

Дамир Тенишев. AgileКруглый_стол Planning for Fixed Price Agile projects. Second step_Problem investigation.

Дамир Тенишев. AgileКруглый_стол Planning for Fixed Price Agile projects. Second step_Problem investigation.

Published in: Education, Technology, Business

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
583
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
8
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. “It’s better to step twice on an adult rake than once to a children’s…”Planning for Fixed Price Agile projects. Second step: Problem investigation. Damir Tenishev Ph.D, Project Manager Exigen Services
  • 2. Planning for Fixed Price Agile projectsContents Terms Fixed Price Agile projects applicability Challenge of estimation Reasons for too optimistic estimates How to make estimates realistic Typical problems and approaches
  • 3. Planning for Fixed Price Agile projectsTerms A fixed-price contract defines thescope, timingand price of a software project. Agile software development is agroup of software developmentmethodologies based on iterativeand incremental development,where requirements and solutionsevolve through collaborationbetween self-organizing, cross-functional teams.
  • 4. Planning for Fixed Price Agile projectsAgile projects applicability Research projects Lack of knowledge about product to be built Customer requires production as soon as possibleFixed-price projects applicability Well-known business domain area High level of technology expertise on provider side Low risk level for initial estimation
  • 5. Planning for Fixed Price Agile projects Estimation challenge  Estimate should be done without deep investigation  All the activities of project lifecycle should be taken into account  Change requests aftermaths should be foreseenPossible reasons for too optimistic estimates Most of projects activities are ignored Background and regular activities are ignored Code support cost is ignored
  • 6. Planning for Fixed Price Agile projectsProject activities (1) Project understanding. Business requirements definition. Learning technologies. Learning customer environment. Developing software requirements. Developing software architecture. Preparing local development and testing environment. Continues integration process support. Development. Tasks clarification. Integration. Change management.
  • 7. Planning for Fixed Price Agile projectsProject activities (2) Code quality insurance. Testing and quality assurance. Bugfixing. User manuals preparation. Deployment. Integration. Configuration. Intermediate releases. User Acceptance Testing (UAT). Integration Testing. Support. Users teaching. Legacy data migration.
  • 8. Planning for Fixed Price Agile projects Agile project related regular components Inter-project communications. Cross-domain communications. Communication with providers of third-party tools.Development, testing and production environment support. Human resources management. Interviews. Hiring. Education, professional development. Regular scrum meetings. Reporting.
  • 9. Planning for Fixed Price Agile projects We need to support written code. Code One developer can support about 100K lines of code.support Support cost grows imperceptibly during project lifetime. For 1 000 000 lines of code you need about 5 developers dedicated to support this code Recommendations  Reduce amount of produced code.  Most of new features should be implemented based on existing code.  Always measure time spend to code support.
  • 10. Planning for FixedPrice Agile projects
  • 11. Planning for FixedPrice Agile projectsDevelopment itself takes about 10% of project effort!
  • 12. Planning for Fixed Price Agile projectsHOW TO MAKE YOU ESTIMATES MORE REALISTICThe penalties method Incomplete business or software requirements – 30-50%. Indistinct requirements like user interface, performance – 20-40%. Lack of examples or samples to verify and validate software – 10-30%. New business domain area – 20-50%. New tools & technologies – 20-40%. Poorly specified execution environment – 20-30%. New customer – 10-20%. New team – 20-50%.
  • 13. Planning for Fixed Price Agile projects Work breakdown TO BE CONTINUED structure Next step Risk management Negotiations Priorities Deadlines Good enough software Fast decisionsOptions
  • 14. Planning for Fixed Price Agile projectsThere are no final decisions Damir.Tenishev@exigenservices.com