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
SCRUM Team workshop 2
Transcript of SCRUM Team workshop 2
"a time-box of one month or less during which a “Done”, useable, and potentially releasable product Increment is created" (SCRUM guide)
What makes you happy @work?
Share your thoughts:
Code Event #9325
What is a SPRINT fail?
Therefore, a Sprint fails if:
Committed work will be completed outside of the time box
Work is not 'done' (i.e. it's partially complete)
Work is not ready to ship, and requires further changes to do so
But this is in Theory...how is it in practice?
Bugs - Did you know..
from Agile Alliance
First things first: don't call them "Bugs", as they are defects.
Let's look together in JIRA and practice this definitions on couple of "Bugs"
“You were partly correct, I did find a ‘bug’ in my apparatus, but it was not in the telephone proper. It was of the genus ‘callbellum.’ The insect appears to find conditions for its existence in all call apparatus of Telephones.”
Edison, 1878, Letter to Western Union President William Orton.
In 1947 Grace Hopper and her staff started using the word “bug” to describe technical glitches when they found a dead moth [above] in Relay 70 of Harvard's Mark II computer.
Photo: NHHC Collection
A defect is :
a misbehavior of the software we produced.
a non-compliance with defined
A defect is not:
something we discover as missing
something which would make what we developed better
Those are more like changes.
Scrum is for the Product, not for the Project:
"Scrum is a framework for developing and sustaining complex PRODUCTS. A framework within which people can address complex adaptive problems, while productively and creatively delivering PRODUCTS of the highest possible value (Scrum Guide, 2013)."
SPRINTS are experiments
An unsuccessful Sprint is one where at the end we have not learned anything. We did not Inspect and Adapt the results for customizing the Product and Processes
The team did not reach the Sprint Goal and overestimated their capacity during the planning and forecasted too much. At the Sprint Review we honestly demonstrate to stakeholders only what is really “Done”, even if we have just a few things to show. We receive feedback, whatever it is. The Product Owner then decides whether to fund the next Sprint or not. The answer may be either positive or negative. In the case of a positive decision, the Scrum Team goes to the Retrospective where the team inspects itself, processes and tools in order to carry out their adaptation in the next Sprint.
EXERCISE : SUCCESS OR FAILURE?
The team managed to complete a big number of functionality and brought to the Sprint Review exactly what it forecasted (“thanks” to some overtime and lowering quality). But nobody is present at the Sprint Review except the Product Owner. The Development Team never sees the end-users, and other stakeholders are always too busy to visit the Review. There is no feedback on the Increment. Then we skip the Retrospective because we have a lot of work to do. We start the next Sprint.
EXERCISE : SUCCESS OR FAILURE?
We can define our own definition of success
My proposal: We focus on 3 things:
All User Stories Accepted during SPRINT
Defect removal efficiency
Team velocity stability (SP Delivered = SP Committed)
Exercise: Let's estimate!
What about SPRINT GOAL?
More precisely : Accelerated SCRUM Workshop
TIME BOX: 1 hour