3. Fixed Price Agile projects applicability

4. Challenge of estimation

5. Reasons for too optimistic estimates

6. How to make estimates realistic

9. Lack of knowledge about product to be built.

11. High level of technology expertise on provider side.

13. All the activities of project lifecycle should be taken into account.

15. Background and regular activities are ignored

17. Business requirements definition.

18. Learning technologies.

19. Learning customer environment.

20. Developing software requirements.

21. Developing software architecture.

22. Preparing local development and testing environment.

23. Continues integration process support.

24. Development. Tasks clarification. Integration.

26. Testing and quality assurance.

27. Bugfixing.

28. User manuals preparation.

29. Deployment. Integration. Configuration.

30. Intermediate releases.

31. User Acceptance Testing (UAT).

32. Integration Testing.

33. Support. Users teaching.

35. Cross-domain communications.

36. Communication with providers of third-party tools.

37. Development, testing and production environment support.

38. Human resources management. Interviews. Hiring.

39. Education, professional development.

40. Regular scrum meetings.

42. One developer can support about 100K lines of code.

43. Support cost grows imperceptibly during project lifetime.

45. Most of new features should be implemented based on existing code.

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%.