A story is fully done when the below phases are done.
Analysis (What)
- Story Description: The story is detailed, what does it aim to achieve as the?
- Story Scenarios: The edge cases of the story are detailed.
- Story Conditions of the Acceptance is written in details
- Story Review Session: The overall high level view of the story
- Stories being sized in points regarding complexity e.g. 3, 5, 8 etc.
- Story Kick off session: To go through the story details and all its edge cases and conditions of acceptance in details. All the questions should be answered at this phase.
Milestone:
The Developer will know exactly what the PO/BA would like to achieve.
Design (How)
- The solution how to implement is proposed, discussed and agreed with the Architect/Lead dev.
- Story Estimation: the story is estimated in more details
- Smaller Tasks are created out of the design session
Milestone:
The Developer will know how exactly the story should be achieved and how long it'd take.
Development
- The main scenario/edge cases are developed
- Unit tests are written and pass
- Component tests are written and pass
- The PR is created
- The code is built with no errors
- Test coverage remains within limit.
- The PR code is reviewed by peer devs
- The PR demo is reviewed by peer UX/UI designers
- PR feedbacks are resolved
- PR is approved and merged
Milestone:
The Developer believes the story is fully implemented.
Testing (Quality)
- Test cases and plans are written based on the story main and edge scenarios
- Tests conducted and issues logged and reported.
- Acceptance criteria is met
- Issues are resolved.
- Test cases pass successfully
- Product owner signs off
Milestone:
The Tester believes the story is fully implemented according to the requirements and the Product Owner signs it off meaning ready for deployment.
Deployment
Milestone:
The Product Owner believes that the story has deployed to live.