User stories are small and minimal to fit into the sprint plan |
Project has to be estimated for timelines before the start date. All user stories are split into smaller sprints. |
A user story must include “Acceptance Criteria” that forms the basis for developing end to end test acceptance. |
Customized |
Product Owner
Scrum Master
Team Members |
User Story: User Story is the basic unit of requirements specifications for Scrum, and typically consists of a title and a brief, usually narrative, with a description of the desired system capability. |
Scrum does not allow for changes once a sprint has begun. User stories can’t change in the middle of the sprint. Changes, if any, are accomadated in the subsequent sprints. |
Each sprint can have their own sprint planning. Sprint time is further divided into smaller chunks as Analysis, Development, Testing, etc.. |
Unit Testing |
|
(4-9) Members in a team. Teams are split to multiple units for larger projects, aligned to core modules. Maintaining team collaboration is key. Teams meet everyday to review progress |
Product Backlog : The Product Backlog is the set of all un-implemented User Stories that have not been assigned to the current Sprint. |
User Stories are selected for each sprint which form a duration of 2 to 5 weeks. Selection is also influenced by the need to release “working software” at the end of each sprint. |
Sprints are Timeboxed. |
Independent Testing:
(1) Test Case Execution & minimum documentation (Current Sprint)
(2) Test Case preparation (Subsequent Sprint) |
|
Customers participate via the role of a Product Owner, and join in atleast one or two daily team meetings a week. |
Sprint Backlog : Is the set of User Stories planned for implementation in a active Sprint |
|
Progress is measured based on the velocity of the sprint’s user stories |
Test Automation is optional, and is implemented only when regression testing is needed. |
|
|
Sprint Burndown Chart: Is a visual resource effort burndown chart for Sprints (1…n) |
|
Sprint meetings are usually proportional to the Sprint duration. |
High priority user stories are tested first |
|
|
|
|
|
Defects are raised and recorded and fixed in subsequent sprints |
|
|
|
|
|
Performance & Security Validations are an end of the line activity. |
|
|
|