application lifecycle management
TRANSCRIPT
References
• http://en.wikipedia.org/wiki/Unified_Process#Inception_Phase
• http://www.enterpriseunifiedprocess.com/essays/phases.html
Inception
• Requirement gathering • Requirement Analysis• Building Team• Identify risks• Primary estimation of the project
Elaboration
• Address known risk factor• Establish and validate the system architecture• plan for the Construction phase (by addressing risk
factors)
Construction
• Development• System stability• Prepared stakeholders• Risk acceptance• Enterprise standards compliance
Transition
• Production deployment• Enterprise standards compliance• Feedback from end users• Returns to the inception phase as per feedback &
response of initial release
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
Resolving ProblemsRequirement 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
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.