Scrum
a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems.
Scrum Team
The Scrum Team consists of one Scrum Master, one Product Owner, and Developers.
Product Owner
- the primary interface between the team and the Business Owner
- responsible for maintaining and prioritizing the backlog of tasks to be performed
Scrum Master
- to keep the development team productive
- to ensure that their issues, concerns, and roadblocks are taken into consideration by the Product Owner
Development Team
- responsible for delivering the product
- typically cross-functional
- self-organizing and defines the rules dictating how they work together
Customer
the group or organization who is sponsoring the project and who will ultimately use it.
Business Owner
represents the customer and is the source for application requirements
Product Backlog
- a list of the requirements the application must meet
- requirements are expressed as user stories of the format
user stories (stories)
- short statements identifying the type of person, the functionality they need to perform in their own terms, and the value they expect to achieve from it
- “As a … I want to … So I can …”
- Sagas, Epics, & User Stories
main processes in Scrum
the sprint, sprint planning, the daily Scrum meeting, the sprint review, and the sprint retrospective
Sprints
- application development cycles
- A fixed number of user stores are assigned to each sprint
Sprint Planning
- at the start of each sprint
-
Daily Scrum Meeting
- the goal is to make sure that there is transparency across the team to both successes and roadblocks.
- Not intended to solve issues or problems.
Sprint Review
- to demonstrate the working product to the customer
- all hands meeting
Sprint Retrospective
is conducted by and for the Scrum Team to promote continuous improvement.
story points
a measure of relative effort or difficulty required to complete a given story
Burn-Down Chart
graphical view of the number of stories in the backlog that have been completed against the total number remaining across sprints
velocity
a measure of average rate that stories are completed across sprints
Product Backlog Refinement
- the activities of adding detail, estimates, and order to items in the Product Backlog
- also known as just “Refinement” or “Backlog Grooming”
epic (Jira)
- a large body of work that can be broken into many smaller pieces of work - stories
- an abstract view of what we are trying to achieve
story (Jira)
- aka user stories
- the written requirements from the end-user perspective and smaller pieces of work within an Epic
- what is required to achieve the Epic
- none technical
task (Jira)
- define all the related work that has to be done to complete the story
- technical
