Scrum Training 2021? Scrum is designed to address the complexity of the modern, digital age where ever-changing customer demands determine how we structure our organisations. Scrum depends on the ability of teams to learn from mistakes and self-organise around difficult problems. A lot of the traditional leadership responsibilities (such as planning, quality and customer-communication) are needed at the level of the team. For a leader this means letting go of responsibilities and a possible re-definition of the traditional role. This doesn’t mean we no longer need managers or leaders, but the role will definitely change. Dependent on a teams’ position in the maturity matrix (level 1 to 5) different leadership styles should be applied. As a leader, you should be open to delegate responsibilities and create a plan on how to do so.
Everyone has a voice with agile. This never happened before at Starmark. They had department meetings once a month and discussed how that specific department could run better. Now, every meeting is a company-wide discussion about how the entire company can be better. Team members in different departments can in this way talk to each other to make the entire process smoother. Every morning each work stream gets together for about 10-15 minutes. A different person runs that meeting each day and everybody says what they accomplished yesterday, what they plan to accomplish today, and if there are any blockers- any collaborations that need to occur. Each person should spend no more than a minute.
When we think of agility we often think of being able to move and think quickly and easily. This is often exactly what is expected of us in our jobs. New systems, new technologies, and just new ways of doing things keep businesses competitive in the market. In fact, 61% of organizations experience three or more major changes every year. This constant state of change requires employees to keep up. Employees have to be able to learn about these changes and implement them at a faster pace. All this change requires agility, and to be able to support learning agility, companies need to start creating an agile learning culture. If you already have an active learning culture established and are ready to adjust to change, then you are in the minority. Only 17% of companies consider themselves highly effective at managing change. And only 30% have change and learning teams to support employees through the change process. For you, creating an agile learning culture may not be much of a problem. You probably already do some of the things listed below. But if you have no learning culture, then it might be a little more difficult. Hopefully, these tips will help get you started. Read additional info at Agile Product Management with Scrum.
There can be other meetings for the day or within the week. Keep the flagging of problems restricted to the 15 minute time box and the solutions to the 16th minute or other meetings. When the team sees the need to talk more, this is just part of their self-management. The little bits of motivation and rewards through appreciation during Daily Scrum when everyone is there can boost everyone’s morale. It makes the other members realize they can depend on each other and gives recognition to the person who tries to help out.
Retrospective (also called “retro”) is the core element of Scrum, so it must be held appropriately. Retrospective isn’t just a fancy word. It’s a technique that has its rules. Many Scrum teams turn sprint retrospectives into a meaningless waste of time because they don’t stick to the rules. Remember that a sprint retrospective gives a Scrum team a chance to improve their workflow. For a typical month-long sprint, a retro should take no more than 3 hours. Spending more time on it is inefficient and counterproductive. During a sprint retrospective, team members should do the following: Share their ideas about a just-finished sprint (process, relationships, environment); Decide what went well and what went wrong; Offer improvements and propose a plan for implementing them. As a result, your team will define problems and suggest solutions. Don’t forget that sprint retrospectives require the presence of a Scrum Master who moderates the event and encourages the team. Sprint retrospectives help Scrum teams become more efficient and professional. See extra info on here.