3. Problems
After 2 first sprints:
• Developers made up there own ideas and criteria
• During the development developers focus on codes
• Developers’ ideas not fit with in production stage
• Repeating bugs for developers and more tasks for testers
4. Solution
• Requirements doc and features’ criteria notes
• In production perspective should be share across development and
deployment stage
• Suggestion/ideas for improve developing features
• BA and PO involving in sprint planning for deliverables
6. BA in Cobra
• Requirements for each deliverable features
• Criteria for each functions, elements, attributes …
• => Extract requirements from Repeating bugs
• => Extract requirements from Experience of other projects
• => Simplify, Organize, andTranslate requirements
7. Product Owner
https://www.mountaingoatsoftware.com/agile/scrum/product-owner
• Responsibilities is to have a vision of what he or she wishes to build, and
convey that vision to the scrum team
• Commonly a lead user of the system
• someone from marketing, product management or anyone with a solid
understanding of users, the market place, the competition and of future
trends for the domain or type of system being developed
• Product owner role needs to have a vision for what is to be built
8. PO in Cobra
• Vision on Each Roles’ perspective (user story)
As a <type of user>, I want <some goal> so that <some reason>.
• Vision of a Feature and Function to be built
• => Extract stories from Repeating bugs
• => Extract stories from Experience of other projects
9. Conclusion
• During sprint planning, the team will nominate new features.
• BAs and POs will involving in Sprint planning and give notes on
requirement, criteria and …for deliverables
• Future steps …