Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
20 Cards in this Set
- Front
- Back
- 3rd side (hint)
|
What is scrum? |
An agile process that allows us to: 1. Focus on delivering the highest business value in the shortest time. 2. Rapidly inspect actual working software. |
|
|
|
Scrum characteristics |
1. Self-organizing teams. 2. Product progresses in a series of month-long sprints. 3. Requirements are captured as items in a list of “product backlog”. 4. No specific engineering practices prescribed. |
|
|
|
Scrum frameworks |
1. Roles 2. Ceremonies 3. Artifacts |
|
|
|
Scrum Ceremonies |
1. The sprint planning 2. The daily scrum 3. TheSprint review 4. The Sprint retrospective |
The |
|
|
Sprint planning |
1. Team selects items from the product backlog that they can complete. 2. Sprint backlog is created and tasks are identified and estimated. 3. High-level design is considered |
Select, estimated |
|
|
The daily scrum |
1. Parameters - Daily - 15-minutes - Stand-up 2. Not for problem solving 3. Helps avoid other unnecessary meetings |
|
|
|
Everyone answers 3 questions |
1. What did you do yesterday? 2. What will you do today? 3. Is there anything in your way? |
|
|
|
Sprint review |
1. Team presents what it accomplished during the sprint 2. Typically takes the form of a demo of new features or underlying architecture 3. Whole team participates |
|
|
|
Sprint retrospective |
1. Periodically take a look at what is and is not working 2. Typically 15–30 minutes 3. Done after every sprint 4. Whole team participates |
|
|
|
Start/Stop/Continue |
Whole team gathers and discuss what they would like to start/stop/continue doing |
|
|
|
Scrum roles |
1. Product owner 2. Scrum master 3. Team |
|
|
|
Product owner |
1. Define the features of the product 2. Decide on release date and content 3. Accept or reject work results |
|
|
|
Scrum master |
1. Represents management to the project 2. Responsible for enforcing Scrum values and practices 3. Removes impediments |
|
|
|
Team |
1. Typically 5-9 people 2. Cross-functional eg. programmers, testers, ux designers. 3. Members should be full-time. |
|
|
|
Scrum artifacts |
1. Product backlog 2. Sprint backlog |
|
|
|
Product backlog |
1. The requirements 2. A list of all desired work on the project. 3. Ideally expressed such that each item has value to the users/customers of the product. 4. Prioritized by the product owner. 5. Reprioritized at the start of each sprint. |
|
|
|
Sprint backlog |
1. Sprint goal 2. Managing sprint backlog 3. What is user story? |
|
|
|
Sprint goal |
A short statement of what the work will be focused on during the sprint |
|
|
|
Managing the sprint backlog |
1. Individuals sign up for work of their own choosing. 2. Estimated work remaining is updated daily. 3. Any team member can add, delete or change the sprint backlog. 4. Work for the sprint emerges. |
|
|
|
What is user story? |
1. A short, simple description of a feature told from the perspective of the person who desires the new capability, usually a user or customer of the system. 2. The essence of user-centric and usage requirements elicitation is to focus on what the user wants to have, not what the user wants the system to do. |
|
