As well-intentioned as teams are, it’s really hard to finish absolutely everything by the end of a sprint. A team may have grabbed eight product backlog items (typically user stories), but only finish six or seven of them. The other items are often close to done, but this isn’t horseshoes so close doesn’t count.
But what about the estimates on those unfinished product backlog items? Should they be re-estimated? And should the team get partial credit for the work they did complete? Let’s consider each of these questions, starting with partial credit.
Continue reading…
Scaling Agile Has Never Worked… and Never Will
Burger story
You can use storytelling to explain why slicing work is important. An colleague Rene de Leijer shared me the following story:
You are on holiday in the USA and driving already for hours on route 66 from the Grand Canyon to Las Vegas. Your stomach is roaring and your eyes are looking for a real American hamburger (sorry for the vegans). You see yourself eating one with both hands holding it in front of your mouth. And finally, in a small village, you see a strange burger cottage. Do you want to eat something in that weird place or keep on searching for another place to eat? But maybe that will take an extra hour. So yes you decide to stop and ease your hunger. The sign on the door says “Pull”, so you pull the door and it does not open. “Whahahaha” you hear someone laugh. You really feel weird on this and get a little but irritated, being hungry is not helping on this. You order a huge burger and the man behind the bar says “I will get you something in a minute, sir”. After 1 minute he puts a delicious piece of bread on a napkin and asks if you need some ketchup on your burger. And after my confirmation, he put some ketchup on the bread. After 3 minutes he puts an incredibly tasty burger on the bread, you really smell it and are eager to take a bite. “Sorry the burger is not finished yet” he says and my stomach is roaring all the time, while I am staring at that delicious piece of meat. 1 minute later, he puts some lettuce on top of the burger and only 2 minutes later some extra ketchup. “We are almost there sir” I hear him say. And finally, some onions and the last piece of bread are adding on top of it. “Well sir, now you can eat your burger, we have done everything in our power to give you the best burger you have ever tasted”. I pick up the burger and take a huge bite, and I spit it out, the bread is soggy, the burger cold and my hunger is vanished . How would you feel if you are this person, I think very disappointedly and he is leaving to find some other food? And do you see a comparison with our way of developing? Do you think the customer would enjoy if we deliver him every 2 minutes a small slice (top-down) of the burger
?
Agile Rhapsody
Scrum Quiz: Pubquiz
Vragen Scrum Quiz
- Welk nieuw element in de Scrumguide 2020 is toegevoegd als verantwoordelijkheid van de Product Owner?
- Product Vision
- Purpose
- Product Goal
- Performance metrics
- Eén van de verantwoordelijkheden binnen Scrum is anders genoemd in de Scrum Guide 2020, welke?
- Het Development team vervalt en hier komen Developers voor in de plaats
- De Product Owner vervalt en wordt nu Value Maximizer genoemd
- De Scrum Master vervalt en hier komt Facilitation Expert voor terug
- De projectleider krijgt als nieuwe rol meer body in de Scrum Guide 2020
- In volgorde van tijd, maak een jaarlijn van wanneer de verschillende onderwerpen zijn ontstaan:
- Scrum, SAFe, Agile Manifest
- Agile Manifest, SAFe, Scrum
- Agile Manifest, Scrum, SAFe
- Scrum, Agile Manifest, SAFe
- Welk artefact hoort bij het Increment?
- Sprint Goal
- Definition of Done
- Sprint Backlog
- Review
- Wat waren de founding fathers van de Scrum guide Jeff Sutherland en Ken Schwaber van elkaar?
- Neven
- Vakgenoten
- Oud- collega’s
- Prijswinnaars
- Waar komt de term Scrum vandaan?
- American Football
- Schaken
- Basketball
- Rugby
- Tijdens de Sprint Planning wordt in de Scrum Guide 2020 nadruk gelegd op:
- Het ‘waarom’ van een Sprint
- ‘wat’ gaan we doen deze Sprint
- ‘hoe’ pakken we werk aan deze Sprint
- Alle bovenstaande
- Welke commitment behoort bij de Sprint Backlog?
- Developers
- Daily Scrum
- Sprint Goal
- User Stories
- Wat is het aantal wereldwijd behaalde Scrum.org certificeringen in januari 2021?
- 100.000
- 250.000
- 500.000
- 1.000.000
- Welke Scrum.org certificering is het meest behaald?
- PSM1 (Scrum Master)
- PSPO1 (Product Owner)
- PSK1 (Kanban)
- PAL1 (Leadership)
- Wat zijn de 5 Scrum values?
- Honesty, Focus, Respect, Fun, Courage
- Openness, Courage, Commitment, Fun, Focus
- Extraversion, Focus, Commitment, Openness, Integrity
- Openness, Focus, Commitment, Respect, Courage
- Hoe vaak per maand Googelt men “Scrum” in Nederland?
- 140x
- 1400x
- 14000x
- 140000x
Antwoorden
- Product Goal
- Het Development team vervalt en hier komen Developers voor in de plaats
- Scrum, Agile Manifest, SAFe,
- Definition of Done
- Vakgenoten
- Rugby
- Alle bovenstaande
- Sprint Goal
- 000
- PSM1
- Commitment, Focus, Openness, Respect, and Courage
- 14000x
Gekopieerd van: https://agilescrumgroup.nl/scrum-quiz/
How To Give Negative Feedback?
A favorite frameworks for providing negative feedback is the CEDAR™ model from Anna Wildman. CEDAR is an acronym for the steps involved in providing feedback.
Context: Set the context for the person. Describe the problem, the role their behavior had in creating or exacerbating the problem, and the effects it had.
Examples: Provide one or more examples to illustrate the behavior. Don’t go overboard here. One example may be enough but never give more than three.
Diagnosis: Talk to the person about why they behaved as they did. My favorite approach is simply to ask, “What caused you to act that way?” or perhaps “What caused you to say that?”
Action: Ask the employee what actions they will take next. This could be aimed at correcting an existing problem or preventing it happening again. Get the person to state clearly what their goal is and name specific actions they’ll take to achieve it.
Review: End a discussion by establishing a plan to review the person’s progress. Ask them when you should meet again. Before then, observe the person. Look for an opportunity to praise them sincerely for any progress they’ve made.
TEAM VALUES
A great exercise to do with your team, as copied from https://scrum-agile.nl/?page_id=256
Start by individually answering the following questions:
- At work, I get inspired by…
- I’m proud to be part of a team that…
- What I can offer my colleagues is…
Shared the outcome with each other and talk about the outcomes.
Then answer the following questions:
- My Personal top 5 values are…
For inspiration you can use a list of values from https://scottjeffrey.com/core-values-list/
After writing down 5 values, you challenge them by asking the following questions for each value:
- If you were to start a new organization, would you build it around this core value regardless of the industry?
- Would you want your organization to continue to stand for this core value 100 years into the future, no matter what changes occur in the outside world?
- Would you want your organization to hold this core value, even if at some point in time it became a competitive disadvantage—even if in some instances the environment penalized the organization for living this core value?
- Do you believe that those who do not share this core value—those who breach it consistently—simply do not belong in your organization?
- Would you personally continue to hold this core value even if you were not rewarded for holding it?
- Would you change jobs before giving up this core value?
- If you awoke tomorrow with more than enough money to retire comfortably for the rest of your life, would you continue to apply this core value to your productive activities?
(source: https://www.jimcollins.com/tools/vision-framework.pdf )
If you can answer a values with “yes” on all questions, you got a winner.
Collect all values that were answered with a yes on all questions, and from those values look for similar personal values within the team.
Tutorial: How to build a ‘Now, Next, Later’-Roadmap in Jira with just 3 easy steps
Major Changes To the Scrum Master Responsibilities Left Many Confused
In this article, Willem-Jan Ageling will discuss the evolution of the Scrum Master.
Using Brain Science to Boost Your Scrum Events
This article is published in Agile NXT. This article describes some of the concepts Evelien Roos learned and how you can apply “brain science” to make your Scrum events more effective.
https://articles.xebia.com/using-brain-science-to-boost-your-scrum-events