7. Elaboration
• Address known risk factor
• Establish and validate the system architecture
• plan for the Construction phase (by addressing risk
factors)
9. Transition
• Production deployment
• Enterprise standards compliance
• Feedback from end users
• Returns to the inception phase as per feedback &
response of initial release
10. Issues Faced
Requirement Issues Technical issues
Incorrect and miss understanding
of requirements
Incorrect implementation of
requirements
Inconsistent Analysis Delay due to critical issues
Unfeasible Estimations Delay due to feasibility steps
Communication Gap Exception in code
11. Resolving Problems
Requirement Technical
Scrum meeting Bug fixing by checking root of
the issue
Confirmation on requirements Communicating with team
members for problem facing
Receive Use Cases of features Suggesting probable delay
with proper reason
12. Conclusion
• For better product delivery it is important to have
requirement analysis with team members.
• Any issues faced by team members should be shared
with other team members .
• Members should provide details to project manager if
possible delay is occurring with proper reason and
estimation time.