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
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.
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.
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. Scrumban: An Agile Hybrid.
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 scrumdefinition.
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.
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 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.
However, a ScrumTeam may not always have a Valuable Product Owner. The Product Owner Proxy or Proxy Product Owner: In my past article about practices leading to anti-patterns I mentioned the Proxy Product Owner being a widely used practice, especially in scenarios where you have distributed teams or onshore-offshore models.
Often after exploring the definition of done in our Scrum.org training, and exploring its importance to promote transparency and is a commitment to the increment every Sprint. A common question we get asked is how do we get started with creating a Definition of Done ? Importance of Definition of Done.
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.
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.
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.
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.
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.
The Complex Project Toolkit is really a book about paradigms in project management and how to encourage teams (and project managers) to stay curious and to embrace uncertainty. When you take a look at the Agile Manifesto’s core principles you will find there is definite overlap. Maybe an idea for a follow-up book? Conclusion.
In the first part of this blog series , I explained how to identify the organizational elements to include in your product definition. In this blog, I explain how you can refine your product definition to organize into effective cross-functional teams. That would mean that each team had the skills to cover the whole heat map.
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. That’s where the primary description of Scrum is kept. If it is not an organizational standard, the ScrumTeam must create a DOD appropriate for the product.
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. ?
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.
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”.
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?
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.
. Scrum is not a set of work instructions; it’s a framework. Scrum relies upon the collective intelligence of those using it to figure out how best to apply it in their situation. However, many take this to mean that they should figure out how to modify Scrum to suit their situation. . Don’t customize Scrum. .
The Daily Scrum is the heartbeat of Scrum. It's a key inspect and adapt opportunity for the DevelopmentTeam, encouraging them check their progress towards the Sprint Goal and adjust their plan accordingly. Last week I put together a short video of what a less than perfect Daily Scrum might look like. Scrum Fouls.
People may not see the point when they hear about the Definition of Done in Scrum. They may say, "We are so sick of talking about the Definition of Done," or “Why does this matter?” First and foremost, what is a Definition of Done? The Definition of Done is a document that clarifies these questions.
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.
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.
"There's no predictability/commitment in Agile/Scrum". Over the years I've heard my share of these kinds of statements from various levels of executives: "When my guys run a product development release I really want to know what I will get at the end so I can make business plans accordingly". "In Wait, That was a complex sentence.
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!
As a manager, tackling team and project challenges effectively can often seem like navigating a complex labyrinth. Fortunately, Scrum offers a structured framework that can guide you through. Here's how Scrum addresses ten common challenges that managers face, providing clear solutions through its empirical approach.
On November 18, 2020, Ken Schwaber and Jeff Sutherland released an updated version of the Scrum Guide. In this blog post, I will share what you need to know about the 2020 Scrum Guide. I will start with the most important things you need to know, and then I’ll get into a little more nuance for the Scrum nerds.
In my last post about Professional software teams creating working software David Corbin made a good point. Since that is different for each Product and may change over time you need to focus on Quality and reflecting that quality in a Definition of Done (DoD). Updated to reflect the 2020 Scrum Guide! The 2020 Scrum Guide.
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.
TL; DR: Scrum Master Anti-Patterns. Join Stefan in one of his upcoming Professional Scrum training classes ! Scrum’s Sprint Planning aims to align the Developers and the Product Owner on what to build next, delivering the highest possible value to customers. Shall I notify you about articles like this one?
I think of the three accountabilities in the Scrum framework as creating a balance of power. The Product Owner owns the content and ordering of the Product Backlog, which describes what the team will work on. The Developers own how to deliver their work. And the Scrum Master helps to maintain the balance between them.
This article discusses Business Agility and why some organizations are not able to reap the benefits Scrum has to offer. Covid: I’m back for Scrum chitchat. Hiren : Hey Covid, tell me what’s our Scrum topic of discussion today? Covid: Tell me honestly Hiren, does Scrum really work? Scrum will never fail you.
In this blog post, I share some tips and tricks that may help you facilitate strong Sprint Planning outcomes, so that your ScrumTeam will have a great start into their Sprint. Your team needs to overcome the Groan Zone to avoid weak outcomes that lead to a poor Sprint! Who facilitates Scrum?
Create Scrum Master Interview Questions? Previously, I tested how ChatGPT would answer questions from the Scrum Master Interview Guide; see below. Back in January 2023, I would not have taken the next step in the Scrum Master interview process, inviting ChatGPT to a full-size interview with several Scrumteam members.
Last week, 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.
We all have strengths and weaknesses with the preferred stances of a Scrum Master. Like many of the teams we work with, being ‘key-shaped’ comes to mind – cross-skilled and competent at many things but having a deeper knowledge of certain stances more so than others. A trainer and a teacher are not the same.
The Definition of ‘Done’ is probably the most misunderstood concept of the Scrum framework. Scrum Guide 202 0 The Definition of ‘Done’ provides a shared understanding among Creators-(The ScrumTeam- Developers, Product Owner, and Scrum Master) as well as Inspectors (the stakeholders).
There are plenty of failure possibilities with Scrum. Given that Scrum is a framework with a reasonable yet short “manual,” this effect should not surprise anyone. What if, for example, not all of your Scrumteam’s members feel enthusiastic about the Sprint Retrospective, the critical event when the Scrumteam inspects itself?
TL; DR: Scrum Anti-Patterns Taxonomy As the editing process of the Scrum Anti-Patterns Guide is nearing its end, it is time to take the next step. The brand new Scrum Anti-Patterns Guide offers 180-plus anti-patterns organized by roles, events, artifacts, and commitments. That is helpful for any Scrum practitioner.
We also covered the importance of having an engaged staff - because it often leads to higher performing teams and ultimately, better business outcomes. In this and the next few posts, we’ll break down Gallup’s 12 questions , and how applying Professional Scrum might be just what is needed to help move the needle towards higher engagement.
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