Make your Scrum team great again

Editor's Notes

• #4: Classify audience Have you ever heard about Scrum? Are you using Scrum in your team? How many events/meetings in Scrum? What are they? What are Scrum roles? What questions are often asked in Daily Meeting? What is sprint? “With Scrum, a product is built in a series of iterations called sprints that break down big, complex projects into bite-sized pieces” Have you ever heard about “Scrum Goal”? What do you understand about “self-organizing”?
• #6: Warm up questions relating to Scrum Planning Which activities you often do in Scrum Planning? If you are ScrumMaster? If you are Develoment Team Your SM always decides the estimation? Your SM always solves issues (impediments) by himself? Your SM is technical expert? => He feels a strong need to advise people what to do? Manage the meeting?
• #7: You might wonder: where does it say that the Scrum Master doesn’t lead the events? And if the Scrum Master doesn’t lead them, who does? What IS the Scrum Master’s role at the events? To answer this let’s take a deep-dive into Scrum.
• #10: ScrumMaster is neither manager of the Scrum meetings, nor responsible for scheduling them. Instead, ScrumMaster shall be a facilitator, who takes care about the form of the conversation, not the content.
• #11: Taking care of the team, solve issues (impediments) for them, plan meetings… It’s easy to get there as it seems to be helpful. But only in the short term. Long-term, it will create unconfident people who rely on ScrumMaster and never take over responsibility and ownership. Instead, you shall show them they can solve most of their problems by themselves, and be a good coach, facilitator and servant leader. Facilitation is more than just leading Scrum meetings. As a facilitator, a ScrumMaster should know how to make conversations efficient and smooth. A ScrumMaster should know how to help people and team to agree and make a decision. The ability to facilitate is critical for team success.
• #12: Being a technical expert is dangerous for ScrumMasters. They feel a strong need to advise people on what to do. If you know a better solution, it’s just easier to tell them, then help them to figure it out. Instead, ScrumMaster shall trust the team they are the experts and coach them so they become better.
• #13: Warm up Report to Scrum Master Discuss technical things It is over 15 minutes Don’t share impediments
• #14: The Development Team uses the Daily Scrum to inspect progress toward the Sprint Goal and to inspect how progress is trending toward completing the work in the Sprint Backlog.
• #15: The Development Team uses the Daily Scrum to inspect progress toward the Sprint Goal and to inspect how progress is trending toward completing the work in the Sprint Backlog.
• #18: I like to start a new team like this: I’ll definitely run the first two or three meetings. Then I shift to simply announcing, “OK, everyone, it’s time to start.” I might say, “Who wants to go first?” But I’ll soon stop saying even that. After a few meetings like that, I’ll switch to visibly looking at my watch when the meeting is ready to start and, if necessary, I’ll clear my throat loudly enough that people get the point. I’ll then stand silently until someone says, “Oh, I guess we’re supposed to start.” After a few days of looking at my watch and clearing my throat, I’ll simplify and just look at my watch at the designated start time. After a couple of days of that, I’ll stop even looking at my watch. I’ll just stand there and wait for the team to decide to get started. I definitely don’t stay silent during the entire meeting. I may need to coach a person into providing more detail, or I may politely interrupt someone (“Maybe we should go into the details after the daily scrum”). 
• #19: Warm up Physical board or using jira, tfs?
• #20: When practicing Scrum, we can make the sprint backlog visible by putting it on a Scrum task board. Team members update the task board continuously throughout the sprint; if someone thinks of a new task, she writes a new card and puts it on the wall.
• #22: At any point in time, the total work remaining to reach a goal can be summed. The Product Owner tracks this total work remaining at least every Sprint Review. The Product Owner compares this amount with work remaining at previous Sprint Reviews to assess progress toward completing projected work by the desired time for the goal. This information is made transparent to all stakeholders. Various projective practices upon trending have been used to forecast progress, like burn-downs, burn-ups, or cumulative flows. These have proven useful. However, these do not replace the importance of empiricism. In complex environments, what will happen is unknown. Only what has already happened may be used for forward-looking decision-making.
• #23: This is a powerful alternative to a Sprint Burndown. At the end of every Daily Stand-up meeting the team asks themselves; how confident are we that we will be able to finish each User Story by the end of the Sprint? The answer is represented by a Confidence Smiley. When a smiley shifts (from green to orange, or from orange to red) the team grabs the opportunity to discuss what they need to do, how they can help out, and if they need to alert Product Owners and Stakeholders on changes in the forecast. Confidence Smileys offer an instant and simple overview of the team’s sprint progress for anyone else as well.
• #24: If you for some reason become blocked while working on a task, preventing you from moving forward ‐ add a red blocker note on top of that task. This makes the reason known for everyone, and also works as a follow‐up reminder. Review the blockers during the Daily Stand‐up and discuss how to address and resolve each of them. The description clearly states why you are blocked, who you are waiting for (and why), or what the problem is. To make it even clearer, write your own name and the date you became blocked in the corner of the Post‐it.
• #30: Warm up Which retrospective technical are you using? Has no idea on retrospective? There are few of silent people It is not important so you think you can ignore this meeting?
• #36: During a discussion some people might be very outgoing and talking and talking and you can hardly stop them. Some other people like to stay in the background and don’t say much. They just give their opinion when you ask them directly.
• #37: When you skip generating insights, your team may not understand how events, behaviors, and circumstances affect their ability to develop software Lead the team to examine the conditions, interactions, and patterns that contributed to their success. Investigate breakdowns and deficiencies During a discussion some people might be very outgoing and talking and talking and you can hardly stop them. Some other people like to stay in the background and don’t say much. They just give their opinion when you ask them directly.
• #40: You identified a list of possible root cause of the problem and potential solutions. Now you want to decide what you want to do differently in the next Sprint.