| At line 1 changed one line |
| !!!Scrum |
| !!!Scrum Agile Development Framework |
| At line 3 changed one line |
| Inspect & adapt |
| __Story__ |
| * As a <role>, I want <a feature> so that I can <accomplish something>. |
| * Each story increases the value of the product. |
| * Each completed Story is a product increment. |
| At line 5 changed 3 lines |
| Sprint = short, sustainable burst of work that produces some completed |
| enhancements |
| 1-4 weeks, typically 2 |
| __Sprint__ |
| * Short, sustainable burst of work that produces some completed Stories |
| * 1-4 weeks, typically 2 |
| At line 9 changed 3 lines |
| Roles = Product Owner - 1 |
| Scrum Mater - 1 |
| Team member - 7 +/- 2 (but Scrum master is included) |
| __Roles__ |
| * Product Owner - 1 |
| * Scrum Mater - 1 |
| * Team member - 7 +/- 2 (Scrum master is included) |
| At line 13 removed 4 lines |
| Story = as a <role>, I want <a feature> so that I can <accomplish something>. |
| Each story increases the value of the product. |
| Each completed story is a product increment. |
|
| At line 19 changed 5 lines |
| Maximize ROI |
| Record requirements, often as Stories, and adding them to the Product Backlog. |
| Direct the team |
| Control priorities or backlog |
| No one except the Product Owner may ask anyone to do work or set a priority |
| * Maximize ROI |
| * Record requirements, often as Stories, and adding them to the Product Backlog. |
| * Direct the team |
| * Control priorities or backlog |
| * No one except the Product Owner may ask anyone to do work or set a priority |
| * Holds the vision for the product |
| * Represents the interests of the business |
| * Represents the customers |
| * Owns the Product Backlog |
| * Sets priorities in the Product Backlog |
| * Creates acceptance criteria for the Backlog Items |
| * Is available to answer team member questions |
| At line 25 removed 7 lines |
| * holds the vision for the product |
| * represents the interests of the business |
| * represents the customers |
| * owns the Product Backlog |
| * sets priorities in the Product Backlog |
| * creates acceptance criteria for the Backlog Items |
| * is available to answer team member questions |
| At line 33 removed one line |
|
| At line 36 changed 2 lines |
| Scrum Master acts like a coach keeping the team high-performing and |
| self-organizing. |
| Scrum Master acts like a coach keeping the team high-performing and self-organizing. |
| At line 48 added 2 lines |
| * 7 +/- 2 members (including Scrum master) |
|
| At line 62 changed 2 lines |
| * team members are not restricted to their area of specialty. They |
| do whatever they can to help |
| * team members are not restricted to their area of specialty. They do whatever they can to help |
| At line 74 changed one line |
| Each item is a backlog item or user story |
| * Contains all Stories |
| At line 76 changed one line |
| Most important stories first |
| * Each item is a backlog item or user story |
| At line 78 changed one line |
| Stories on top must be manageable size and well understood |
| * Most important stories first |
| At line 79 added 2 lines |
| * Stories on top must be manageable size and well understood |
|
| At line 93 changed 2 lines |
| Team to do list for the Sprint which is a list of Stories to be completed |
| on that Sprint |
| * Subset of the Product Backlog |
| At line 96 changed one line |
| Created by the Team (not the Product Owner) |
| * Team to do list for the Sprint which is a list of Stories to be completed on that Sprint |
| At line 98 changed one line |
| Each Story is sub-divided into Tasks |
| * Created by the Team (not the Product Owner) |
| At line 100 changed one line |
| Story = done by Team |
| * Each Story is sub-divided into Tasks |
| At line 102 changed one line |
| Task = done by a person |
| * Story = done by the Team |
| At line 104 added one line |
| * Task = done by a person |
| At line 106 added one line |
|
| At line 107 changed one line |
| X = time |
| X = time, |
| At line 143 changed 2 lines |
| * Retrospective - 1-2 hours for each week in the length of the Sprint |
| - last meeting of the Sprint (after Sprint Review) |
| * Retrospective - 1-2 hours for each week in the length of the Sprint - last meeting of the Sprint (after Sprint Review) |
| At line 157 changed one line |
| * Part 1 (how many Stories) |
| __Part 1__ (how many Stories) |
| At line 159 changed one line |
| ** Led by product owner |
| * Led by product owner |
| At line 161 changed one line |
| ** Bring up each Story in order |
| * Bring up each Story in order |
| At line 163 changed one line |
| ** Discuss Story and completion criteria |
| * Discuss Story and completion criteria |
| At line 165 changed one line |
| ** Team members decide how many Stories they can complete in the Sprint |
| * Team members decide how many Stories they can complete in the Sprint |
| At line 167 changed one line |
| ** Product Owner decides which Stories, Team decides how many they commit to for that Sprint |
| * Product Owner decides which Stories, Team decides how many they commit to for that Sprint |
| At line 169 changed one line |
| * Part 2 (how will we do it) |
| __Part 2__ (how will we do it) |
| At line 171 changed one line |
| ** Run by the Team |
| * Run by the Team |
| At line 173 changed one line |
| ** Product Owner answers questions |
| * Product Owner answers questions |
| At line 175 changed one line |
| ** May cause additions or subtractions to the Story list for the Sprint |
| * May cause additions or subtractions to the Story list for the Sprint |
| At line 178 added one line |
| Result of the Sprint Planning Meeting is the Sprint Backlog - list or Stories for that Sprint along with their associated Tasks. |
| At line 178 removed 3 lines |
| Result of the Sprint Planning Meeting is the Sprint Backlog - list or |
| Stories for that Sprint along with their associated Tasks. |
|
| At line 204 changed 3 lines |
| * Stories at the top of the list must be small. Break big stories at |
| the top of the list into smaller stories. Product Owner may do most |
| of this with support from the Team. |
| * Stories at the top of the list must be small. Break big stories at the top of the list into smaller stories. Product Owner may do most of this with support from the Team. |
| At line 220 changed 2 lines |
| Not when Stories are declared done. That was done already. Also not the time |
| to determine what is in the next Sprint. |
| Not when Stories are declared done. That was done already. Also not the time to determine what is in the next Sprint. |
| At line 231 changed 12 lines |
| Identify one or two lessons that could be applied to future Sprints. |
| It is about process improvement. |
|
|
| ---------------------------------------------------------------------- |
|
| Product Backlog |
| Backlog Item or User Story |
|
| Sprint Backlog |
| User Story |
| Tasks |
| Identify one or two lessons that could be applied to future Sprints. It is about process improvement. |