This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
Continuous development is so important, and learning new skills helps you stay current in the job market. I’ve worked with Scrum teams and Agile developmentteams, I used Kanban during lockdown to help plan our days and the homeschooling, but I can’t say that I’m experienced in Agile ways. Scrum Master Specialization 4.5
TL; DR: DevelopmentTeam Anti-Patterns. After covering the Scrum Master and the Product Owner, this article addresses DevelopmentTeam anti-patterns, covering all Scrum Events as well as the Product Backlog artifact. The Role of the DevelopmentTeam in Scrum. Do you want to get this article in your inbox?
In this blog post, I'll share with you an exercise to help make transparent expectations of each Scrum Team member, by driving conversations about what team members already understand and where there are potential misunderstandings that need to be changed. The Scrum Guide no longer mentions Scrum Team roles.
The Scrum Mythbusters exercise helps you address the common myths and misunderstandings about Scrum and helps teams discover how Scrum is intended as a simple, yet sufficient framework for complex product delivery. . Scrum Mythbusters is one of the first exercises we start the Scrum.org Professional Scrum Master II class with.
TL; DR: A Remote Sprint Review with a Distributed Team. This seventh article now looks into organizing a remote Sprint Review with a distributed team: How to practice the review with virtual Liberating Structures, including and giving a voice to team members, stakeholders, and customers.
Other teams hold their meetings around the Kanban board or whiteboard so everyone can refer to that if they need to. In Scrum, the developmentteam attend the daily standup meeting. Agile team roles are quite specific, and yet, at the same time, you often find everyone mucking in to get the job done in a multi-skilled team.
TL; DR: 15 Sprint Review Anti-Patterns. Answering this question in a collaborative effort of the Scrum Team as well as internal (and external) stakeholders is the purpose of the Sprint Review. Given its importance, it is worthwhile to tackle the most common Sprint Review anti-patterns. Are we still on the right track?
A Sprint Review is perhaps one of the most difficult elements in the product development with Scrum. Therefore, during the first three years in this role, all my sprint reviews were limited to showing the results to the Product Owner. Since then, the Sprint Review became something special to me. . Team Voice.
Even though it’s a short daily get together, it helps to have some fun standup meeting ideas to break the monotony and keep team morale high. In Scrum, the developmentteam attend the daily standup meeting. Depending on your agile team structure , you might choose the attendees at the daily standup differently.
I like to do assessments from time to time, beyond the regular meetings and updates. One assessment tool offered in the PMBOK involves some emotional intelligence and a scorecard: the stakeholder engagement assessment matrix. Scope the Work Scoping is an exercise in “getting real” about goals and objectives.
The purpose of qualitative metrics is to gain insight into how one or more of an organization’s Scrum Teams are progressing with agile. The interval to test via self-assessment is every 4–12 weeks, with teams of lesser fluency running their tests at the lower end of this range. Question 44: First Steps of a New Scrum Team.
TL; DR: Faking Agile Metrics — An Eye-Opening Exercise. Imagine you’re a Scrum Master and the line manager of your team believes that the best sign for a successful agile transformation is a steady increase in the Scrum Team’s velocity. Moreover, if the team fails to deliver on that metric something is wrong with the Scrum Team.
Instead of trying to figure out an answer within your team, explore it together with stakeholders. We’ve successfully used this exercise with virtual teams. The Daily Scrum is where the DevelopmentTeam plans their collaboration towards achieving the Sprint Goal for the next 24 hours. Sprint Review.
Scrum Anti-Patterns: From Product Backlog to Sprint Review. I added new questions on Scrum anti-patterns, from the Product Backlog to the Sprint Planning to the Sprint Review, to provide more insight into the Scrum value creation process and the organization’s return on investment. Question 45: Scrum Master Anti-Patterns.
Using the budgeting process as a Stage-Gate® to exercise control through the back door : The budgeting process is hard to align with agile requirements like the longevity of teams. Instead, the management ought to provide the teams with goals and guidance on how to achieve these, along with funding sufficient to meet the objectives.
Scrum.org says "PSM II is an advanced course helping students to understand the stances that characterise an effective Scrum Master and servant-leader while diving deep into how they serve the DevelopmentTeam, Product Owner and organisation. How a Scrum Master services: The DevelopmentTeam. Who Should Attend?
Any of the examples will impede the team’s productivity and might endanger the Sprint goal. The Scrum Master must prevent them from manifesting themselves: The Scrum Master has a laissez-faire policy as far as access to the Developmentteam is concerned. Remember: Product Backlog item creation is a Scrum Teamexercise.).
No matter the frequency of your retrospectives you should always watch out for the following Sprint Retrospective anti-patterns from the Scrum Team, the DevelopmentTeam, the Scrum Master, as well as the organization: Sprint Retrospective Anti-Patterns of the Scrum Team. Sprint Retrospective Anti-Patterns.
Based on the classroom exercises, you’re excited to try new concepts and apply the magic cure-all that will solve all waterfall-based project problems. The developmentteam should know what needs to be done, so just call the customer when it’s ready. Adopting Agile is an Exercise in Change Management.
Yet, in reality, some of the best leaders are quiet, introverted people who care deeply for their teams and stakeholders and quietly grind away toward a common goal. It can be learned and exercised on a small scale before being brought to bear on larger groups. This is another instance where having diversity on the team is helpful.
On the one side, they address typical Scrum events such as Sprint Planning, Sprint Review, and the Sprint Retrospective. When a weak DevelopmentTeam meets a commanding Product Owner, focusing on shipping new features, the team may end up as a feature factory, churning out new code while neglecting the technical foundation.
Consider a cadence that involves Planning, Reviewing, and Retrospecting with a clear distinction between the team working on the OKR and its stakeholders. . After identifying the few real OKRs, assess who’s needed to work towards each of them. The Scrum framework provides one example of how such a cadence could look.
We had a look at common remote agile anti-patterns; we analyzed remote Retrospectives, Sprint Plannings as well as remote Sprint Reviews based on Liberating Structures. This eighth article now looks into supporting a distributed DevelopmentTeam organizing a remote Daily Scrum. Do you want to get this article in your inbox?
Daily Scrums are an important part of Scrum, but not all Daily Scrums need to be formal — a DevelopmentTeam should not have a Daily Scrum for the sake of having it; it serves a different purpose than ticking off a box on a checklist. A small, experienced, and co-located team may use a morning coffee break for their Daily Scrum.
My project managers were cross trained as scrum masters to help transform their developmentteams. In my classes and consulting practice, I encourage people to identify and thoroughly assess their stakeholders. This exercise always yields valuable insights. Our teams should be a source of creativity and innovation.
Due to the COVID-19 crisis, chances are that everyone in your organization is working from home. This includes your Product Owner and DevelopmentTeam. Start a “Scrum Question of the Week” exercise. At the start of the week, you offer the team a question about the Scrum theory & principles. Things to try….
That’s why a product roadmap is the backbone of every great developmentteam. Review and align your roadmap with other internal teams. Ask past users for reviews. Roadmaps are an exercise in prioritization. Roadmaps establish trust between you and your developmentteam.
But many teams struggle with this rule. An increment is considered “Done” by the DevelopmentTeam, but requires further testing and stabilization in the next Sprint. Or work is considered “Done” by the DevelopmentTeam, but the install package still needs to be created. It is tempting to fall into “shades of Done”.
What team cognition looks like for Scrum teams, and what signs tell you whether it's there or not. What research in this area tells us about how you can design, support, and encourage teams to developteam cognition and become high-performing. Pictures of a session where we created a skill matrix with a team.
Reassigning Team Members : Frequently moving team members between Scrum Teams disrupts the building of trust and undermines the stability and effectiveness of teams. In the absence of this feedback, teams may engage in gold-plating under the assumption that they are adding value.
Follow-up question : Why is it beneficial that the team adheres to the values and practices of Scrum? This can help improve the overall quality of the team's work and ensure that the team is meeting its goals. Question : Should a Scrum Master remove problems on behalf of the Scrum Team?
Business stakeholders meet regularly with the agile team at a lower level of engagement. In Scrum, this engagement may take place in refinement meetings or at the Sprint Review. The most efficient and effective method of conveying information to and within a developmentteam is face-to-face conversation. Conclusion.
This is an ongoing process in which the Product Owner and the DevelopmentTeam collaborate on the details of Product Backlog items. During Product Backlog refinement, items are reviewed and revised. The Scrum Team decides how and when refinement is done. The DevelopmentTeam is responsible for all estimates.
This is an ongoing process in which the Product Owner and the DevelopmentTeam collaborate on the details of Product Backlog items. During Product Backlog refinement, items are reviewed and revised. The Scrum Team decides how and when refinement is done. The DevelopmentTeam is responsible for all estimates.
Former students of classes are eager to learn more about exercises they’ve experienced and would like to use them as a Scrum Master. How is the PSM II class going to help me pass the PSM II assessment? Future students ask questions related to what to expect and how to prepare.
A Scrum Team’s communication with stakeholders should not be run through a gatekeeper (e.g. solely through the Product Owner) because this hurts transparency and negatively affects the team’s performance. There is greater respect among stakeholders for the product delivery teams. Question 03: Impediment Remover.
This has always been a huge struggle for us and most of the teams we’ve been part of. Unfortunately, many developers and developmentteams still burn more hours than are probably good for them. When stress remains present for a longer period of time, what strategies do you have individually and as a team to cope with it?
While the DevelopmentTeam is responsible for delivering the increment, the Product Owner is responsible for maximizing value by deciding about the content and the order of the Product Backlog. . Amazing Decisions, a company developing and selling digital products. Introduction . Amazing Decisions . This is Kathryn.
Validation: Regular assessment with stakeholders to ensure alignment. Diagram from Scrum.org PSPO course Visualizing the Dilemma: A Product Owner's Scenario Consider a bank scenario - A customer applies for a mortgage, and the bank provides various services like KYC verification, Credit Assessment, Loan Underwriters, etc.
Without a clear definition of done , your developmentteam doesn’t know what they’re working towards, your stakeholders are free to increase the scope, and your users most likely end up with a product that’s cluttered, confusing, and unusable. When can the developmentteam change the definition of done (and how should they do it?).
As a Scrum Master, you develop and help others develop strategies to become more successful with Scrum. How is the DevelopmentTeam going to collaborate to achieve the Sprint Goal? How does management interact with Scrum Teams? You decide to use Mad Tea , a Liberating Structures in Development.
As a Scrum Master you can use every PSM-II exercise with your own Scrum Team and organization. Using plenty of Liberating Structures and serious-and-fun exercises, we wanted to build and structure what the group already knew. After the class, you will be eligible for the PSM II assessment certification. In a Nutshell.
Empiricism via working integrated increments every Sprint - System Demo & Nexus Sprint Review meeting a common Definition of “Done”. The Nexus Sprint Review and the System Demo are similar events happening on a similar cadence - every several weeks (Sprint/Iteration). No team-level Sprint Review.
They are considered to be an invaluable source of collecting information and feedback from the developmentteam and help in keeping the team aligned with the Sprint goals. Sprint Review Meeting. Usually, the entire team is expected to be present during this meeting, including the product owner and the Scrum master.
We organize all of the trending information in your field so you don't have to. Join 100,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content