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
The Bad Apple Effect can deeply sabotage a teams performance and development. Even with talented, capable players, their respective teams often underperformed and struggled to progress in their development. Still, these negative attitudes were affecting the whole team's morale and teamwork.
Scrum is designed to empower teams, enhance collaboration, and increase adaptability. Yet, many teams fall into the trap of pre-assigning tasks at the start of a Sprint, believing it boosts efficiency. While the intention is good, this approach contradicts Scrums core principles and hampers performance.
Scope creep is the more common term but you might hear both, especially if you are working in software development. Ultimately, it isn’t the project manager coming up with new requirements and asking the team to “just do it”. What’s so bad about scope creep anyway? It takes its toll on team morale.
For example, take scrum. Scrum is a great framework for helping teams work more productively together. In fact, the name comes from rugby and like it, scrum is a team sport. Teams learn through experience, reflective meetings and specific roles that add structure and manage work.
An effective Sprint Retrospective ensures the team remains cohesive and aligned, leading to sustainable development and innovation. Still, the decision to skip a single Sprint Retrospective can adversely affect the team and the product's development process. With this reflection, teams can iterate on their process.
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.
While often associated with formal positions in a hierarchy and the power to direct others or allocate resources (a common feature of traditional management), the critical aspect for Scrum is decision-making power within a specific scope. Scrum leverages this by intentionally distributing authority.
In the past years, Johannes Schartau, Christiaan Verwijs, and I wrote many articles on Zombie Scrum. Heck, we even wrote a complete Zombie Scrum Survival Guide ! I’d like to believe that since our book, Zombie Scrum completely disappeared. But Zombie Scrum is still present in different shapes and forms. Zombie Scrum?
The scrum methodology was developed as a response to rigid project management approaches such as the waterfall method, which didn’t adapt to the needs of agile product and software developmentteams. We’ll explore the scrum methodology in-depth, but before that, let’s start with a simple scrum definition.
The ScrumTeam delivers a valuable, useful, and usable Increment(s) every Sprint. In my view: It could be a "layer of cake team", in that it cannot in and of itself delivery value without dependencies on other "layers" of the cake. ScrumTeam members strive for net improvements. Self-managing.
Scrum was introduced in 1995. Since then, as more people, teams, and organizations have started using Scrum, the framework has grown into the most used method for agile product delivery. And as the popularity of Scrum started to grow, many misinterpretations of the framework grew with it. The power of Scrum.
Suitable agile metrics reflect either a team’s progress in becoming agile or your organization’s progress in becoming a learning organization. At the team level, qualitative agile metrics often work better than quantitative metrics. A team may have deliberately built some temporary solutions to speed up experimentation.
Of late, I've been noticing an interpretation of the Scrum Master role - the Scrum Master as An FFFCDO for Developers - a Fierce, Ferocious, Fearsome Chief Defense Officer! What is the Scrum Master protecting the Developers from? Who are the persecutors the Scrum Master protecting the Developers from?
TL; DR: 20 Questions a New Scrum Master Should Ask. Twenty questions for you — the new Scrum Master — that fit into a 60 minutes time-box. Start learning how your new ScrumTeam is currently delivering the product and get up to speed: from Product Backlog forensics to metrics to team challenges and technical debt.
Some time ago, someone on Reddit asked whether there would be any other profession that requires attending a 2-day training class and would then pay as well as a Scrum Master job. This attitude is precisely why the 47 Scrum Master Interview Guide exists: Prevent imposters from slipping through the hiring process and causing damage.
Long has spoonfeeding solutions and off-the-shelf feature descriptions prevailed in many developmentteams. Although some issues might have been fixed, I rarely see the full potential of a ScrumTeam being achieved. Going all-in on predefined features fails to capitalize on hidden ideas in the brains of team members.
. Can scrum be used outside software development? I’ve often worked in cases in non-software where I might have had 10 options that I would consider for the team. If you understand more about the business domain and the technical domain, you understand what the team is doing. Absolutely. .
According to the Scrum guide, Scrumteams typically have 10 or fewer people, including Developers, Scrum Master and Product Owner. But what happens with a Scrumteam that includes more than 10 people? What if the Scrumteam has 10, 15 even more people? Some people check out. .
The lecture triggered many thoughts about the relevance of teaching Agile/Scrum. The first paper was a 2012 study on the tensions with remote (off-shoring) teams (Ramesh et al Ambidexterity in Agile Development ISR2012). It confirmed my preconception that regular education struggles to keep up with developments in our field.
Scrum is simple, but that simplicity means that each of its elements is essential. Teams that mess with the framework are messing with Scrum. Teams that make changes to the elements limit Scrum's effectiveness and aren't really using Scrum. . The team struggled to deliver a Done Increment each Sprint. .
During the first year of the pandemic, Scrum adoption more than doubled for software developmentteams. According to the 15th Annual State of Agile Report, the use of agile approaches for software development grew from 37% in 2020 to 86% in 2021. It is, in essence, the plan for what the ScrumTeam will do next.
I’ve been part of the Scrum community for about 12 years. In this period, I’ve noticed a clear pattern in the majority of Scrum-related threads on social media like LinkedIn, Medium, Twitter, and so on. As a community, we excel at putting our fingers on the sore spots of what teams and organizations do wrong.
A Scrum Event is a meeting. Given the poor reputation that meetings have, maybe it's not a surprise. Rather than replicate the name and pain of meetings, the Scrum Events are designed to replace them and be all that you need. The power of the Scrum Events is in the way they're time-boxed and in their purpose. Daily Scrum.
TL; DR: ScrumDeveloper Anti-Patterns. After covering the anti-patterns of the Scrum Master, the Product Owner, and the stakeholders, this article addresses ScrumDeveloper anti-patterns, covering all Scrum Events and the Product Backlog artifact. The Role of the Developers in Scrum.
TL; DR: 70 Scrum Master Theses. The following 70 Scrum Master theses describe the role of from a holistic product creation perspective. The theses cover the role of the Scrum Master from product discovery to product delivery in hands-on practical manner. The Role of the Scrum Master. It is not a mere management role.
TL; DR: Scrum Stakeholder Anti-Patterns. Learn how individual incentives and outdated organizational structures — fostering personal agendas and local optimization efforts — manifest themselves in Scrum stakeholder anti-patterns which easily can impede any agile transition. Do you want to get this article in your inbox?
This article will review a few different thoughts on the DOD, relate the DOD to acceptance criteria, and show an example of a DOD. In the 12 years that I've been a Professional Scrum Trainer through Scrum.org, I've taught many classes on Scrum and seen many misunderstandings related to the DOD.
TL; DR: Scrum Master Interview Questions on Scrum Anti-Patterns. Scrum has proven time and again to be the most popular framework for software development. Given that software is eating the world , a seasoned Scrum Master is nowadays in high demand. Which makes any Scrum Master interview a challenging task.
Long has spoon-feeding solutions and off-the-shelf feature descriptions prevailed in many developmentteams. Although some issues might have been fixed, I rarely see the full potential of a ScrumTeam being achieved. Going all-in on predefined features fails to capitalize on hidden ideas in the brains of team members.
The Change Formula The Change Formula is a highly practical tool developed over the past decade. He guides readers through applying this understanding to various aspects of life, enabling them to recognise how their minds operate, understand and manage their emotions and thoughts, and develop themselves into the people they aspire to be.
For much of the early 2000’s, large companies would shudder at the thought of operating a team in an agile way. The value derived from holding a retrospective is proportional to the talent of the facilitator, and the intimacy of the team. If the facilitation is poor: it’s going to be a bad meeting.
Intended audience: Scrum masters, Product owners, Managers and Agile coaches. The PO’s are then unsure what needs to be developed. For instance, a lead developer or architect prepares the work for sprints ahead, acting as a proxy between the teams and the PO’s, splitting the requirements in tasks per team.
TL; DR: Scrum Master Anti-Patterns — 20 Signs Your Scrum Master Needs Help. The reasons Scrum Masters violate the spirit of the Scrum Guide are multi-faceted. Typical Scrum Master anti-patterns run from ill-suited personal traits to complacency to pursuing individual agendas to frustration with the team itself.
When working in an agile environment, teams take sprints, a short period of time in which you complete tasks. Scrumteams choose this work by looking over their backlog. A scrum framework allows teams to execute in agile project management, the backlog is very important and backlog refinement keeps work flowing.
Sub-title #2: Jeff Sutherland’s book could have been called: “Scrum: Twice the decision-making in half the time leading to half the work and twice the output.”. A discussion is raging at LinkedIn about the Iron Triangle because the co-authors of Scrum say that “Scrum breaks the Iron Triangle”.
TL; DR: ChatGPT Prompts for Scrum Practitioners. Last week, I ran an “interview” with ChatGPT as an applicant for a fictitious Scrum Master position based on questions from Scrum Master Interview Guide. Zur deutschsprachigen Version des Artikels: ChatGPT-Prompts für Scrum Master, Product Owner und Entwickler. ?
Part 1 intends to focus on the ScrumTeam, Part 2 will be released shortly after our Webinar on April 29th and will focus on the “Epic” challenges agile leaders are facing. Product Backlog is not an event in Scrum, but has its place in the Scrum Guide and therefore the Scrum Framework.
According to the 2020 Scrum Guide, Scrumteams are “self-managing, meaning they internally decide who does what, when, and how.” The most empowered Scrumteams in my experience not only decide who does what, when and how, they also control the structure and organization of the Scrumteam itself. .
Scrum defines three specific accountabilities within the ScrumTeam: the Developers, the Product Owner, and the Scrum Master. Scrum Guide 2020. When it comes to the Scrum framework, these three roles with their accountabilities are the minimum required to deliver a potentially “done” Increment.
TL; DR: Scrum 2022 — Getting You Started as Scrum Master or Product Owner. Probably, you are considering how to further your Scrum Master career or Product Owner career in 2022. Good luck with Scrum 2022—just stick to first principles! Join Stefan in one of his upcoming Professional Scrum training classes !
TL; DR: Scrum Master Interview (6): Demand Creates Supply and the Job Market for Agile Practitioners is No Exception. Scrum has proven time and again to be the most popular framework for software development. Given that software is eating the world , a seasoned Scrum Master is nowadays in high demand.
TL; DR: Scrum Stakeholder Anti-Patterns. Learn how individual incentives and outdated organizational structures — fostering personal agendas and local optimization efforts — manifest themselves in Scrum stakeholder anti-patterns that easily impede any agile transformation to a product-led organization. ????
TL; DR: A ChatGPT Job Interview for a Scrum Master Position. Can a large language model, not specializing in anything “agile,” pass a screening interview for a Scrum Master position? So, read on and learn whether Scrum Masters will soon be replaced with a chatbot. ?? Question : Thank you for your application as a Scrum Master!
When people ask me the best way for their team to transition to Scrum, I have to tell them that there isn’t an easy answer because every organization is unique. Keeping that in mind, here are some general steps to consider if implementing Scrum is on your horizon. . Is Scrum the right fit for your business problem?
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