Send the link below via email or IMCopy
Present to your audienceStart remote presentation
- Invited audience members will follow you as you navigate and present
- People invited to a presentation do not need a Prezi account
- This link expires 10 minutes after you close the presentation
- A maximum of 30 users can follow your presentation
- Learn more about this feature in our knowledge base article
Transcript of Scrum
Ideas come in from multiple sources
Basically anyone !
Hello I am a Product Owner !
The most important part of Scrum!
I help organize all the pieces into a prioritized list of things to do. This way, the team will be able to work on the right thing!
I also write up User Stories to help everyone understand the task at hand.
What is a User Story?
User stories are 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. - Mike Cohn
FYI: User stories are not actually prescribed in Scrum, but their usage is a very common practice.
There we go, much better
We really care about this product, we can't wait, let us know how we can help!
We agree on what to work on, and when
Of course, more lego's keep coming in...
...and more stories keep getting made
So we know what we want, how do we get it done?
We are the most important part of Scrum!
Introducing the Scrum Team
Scrum teams normally range between 5-9 people
Team members can be from any part of the organization, normally comprised of Developers, Quality Analysts, DBA's, Release Engineers and Business Analysts
Team members are fully committed to doing whatever it takes to get the project done with a high quality standard.
Team members must communicate with each other, and work together to obtain their goals.
This is a repeating process that continues on throughout the life of a product. Its a great indication that the project is useful, needed and desired by its end users.
If your backlog grows "stale", this is a sign that things may not really be what they seem.
Constant grooming and upkeep of the Product Backlog ensures that the project stays on track, and that the team is working on the most important thing.
A ScrumMaster differs from a traditional project manager in many key ways, including that the ScrumMaster does not provide day-to-day direction to the team and does not assign tasks to individuals.
A good ScrumMaster shelters the team from outside distractions, allowing scrum team members to focus maniacally on the goal they have selected. - Mike Cohn
These three roles are the
defined roles in the Scrum process.
The Product Owner
I am the most important part of Scrum.
We have a team, we have a product owner, we have a ScrumMaster, hopefully we have a Product Backlog. Now what?
The work gets done in "Sprints" or "Iterations". These sprints are normally 2-4 weeks in duration.
The team gets together to decide how many stories they can tackle in the next sprint, and commits to getting them done before the Sprint ends.
What does Done Mean?
The Anatomy of a Sprint
At the end of the Sprint, we have a potentially deliverable product.
We have created something of value, and if the Product Owner deems it important enough, we should be able to take it to production.
Daily Scrum - a 15 minute meeting where the Team, ScrumMaster and Product Owner stand in a circle and discuss the stories in the sprint. The most common "agenda" for this meeting, is each member discusses:
Today I plan to...
* if any issues are blocking this person from being productive, they discuss that here as well, even if its well known
Sprint Planning - A meeting held, normally the first day of the sprint, to decide what stories will be committed to during the sprint. These conversations are expected to be fairly detailed, as upon leaving this meeting, the team should feel totally confident they can complete all the stories they have selected.
from the Agile Manifesto:
At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
Industry Standard Agenda for a Retro:
Set the stage
Decide what to do
Inquiry over Advocacy
Dialog over Debate
Converse over Argue
Understand over Defend
-- Tips --
So lets put it all together, so far
What is Scrum ?
Lets go back now and fill in some gaps:
At Heartland, we also have Product Managers. These folks help the Product Owner get the Product Backlog under control.
What kind of work?
The 4 Scrum Rituals
Many companies use a concept called
to help estimate stories. Story Points are a way of evaluating stories based on effort, not off duration.
They are "relative" numbers, not exact measurements.
You and I are both going to walk to the building next door. You think it will take you 5 mins, but since I am on crutches, due to a twisted ankle, I think it will take me 10.
We will never agree on how long it takes to walk to the building.
Why not just use hours or days?
But we could agree, that it will take each of us twice as long to get to the building two doors down.
Also note here that complexity didn't change, we know
to get there, and how to walk. Its just more
to get to the second building.
I want to get to the building next door.
I want to get to the building two doors down.
I want to get to the building over there.
The backlog must be in the best condition it can be. Having too few or too many stories is a sign that the project is not under control. Also, having a Backlog Grooming meeting with the whole team or certain members of the team will help the non-technical and technical people communicate and ensure the story is complete.
I N V E S T
The 4 "Official" Artifacts of Scrum
Sprint Burndown Chart
Release Burndown Chart
Stories found in the Product Backlog are usually bigger in nature, as the team should not spend too much time breaking them down until it is work that is actually going to be done.
Some people call them
, some categorize them as
There are several ways to help teams estimate stories. One of the most common is "Planning Poker". Each team member gets cards, and after the details are vetted out, each team member places a card, their estimate, face down. All reveal their estimate at once, and if there are any that are higher or lower than the group "norm", then discuss to find a good estimate.
Once teams are together for a few sprints, they will average out to a certain Velocity. Velocity is the amount of story points, a team can accomplish ("Done"), within the time constraints of the Sprint. Any story NOT completed by the end of the sprint, is not included in the teams velocity.
We can use this velocity to help determine how much work to allow into a sprint.
Cool Chartz !
Review the work that was completed and the planned work that was not completed
Present the completed work to the stakeholders (a.k.a. "the demo")
Incomplete work cannot be demonstrated
During the sprint review, the project is assessed against the sprint goal determined during the sprint planning meeting. Ideally, the team has completed each product backlog item brought into the sprint, but it's more important that they achieve the overall goal of the sprint.
Scrum is a fairly simple framework for effective team collaboration on complex projects.
Scrum is an iterative and incremental agile software development framework for managing software projects and product or application development
Scrum is founded on empirical process control theory, this asserts that knowledge comes from experience and making decisions based on what is known.
The team model in Scrum is designed to optimize flexibility, creativity, and productivity.
Identify and prioritize market problems (epics)
Provide vision to the PO and scrum team
Stay in regular contact with the PO
Put enough sprints together and you can get to a release.
Put enough releases together,
and you get a product.
Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.