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
In the ever-evolving landscape of project management, Scrum has emerged as one of the most popular frameworks for Agile development. Despite its widespread adoption, many misconceptions exist about what Scrum truly entails. Scrum is Not a methodology. Scrum is a Framework. Scrum is Not linear. Scrum is a team game.
In Scrum, the approach to measurement emphasizes transparency, inspection, and adaptation, integrating concepts like the Cone of Uncertainty and the strategic use of information radiators to enhance decision-making processes. Scrum emphasizes metrics that provide real value and support effective decision-making.
In Scrum, the approach to uncertainty involves embracing short feedback cycles and to continuously refine understanding of user needs and challenges, thus significantly enhancing adaptability and responsiveness. Don't want to miss any of these blog posts? Have the “From PM to PSM” series weekly in your mailbox.
As project managers transition to Scrum, understanding how to enhance the Scrum framework with complementary practices is crucial. Scrum's minimalistic design includes only essential elements, leaving room to incorporate additional practices that can be adapted or changed as teams evolve and discover more effective methods.
From the Scrum Guide: “Scrum is a lightweight framework…” Let’s have a closer look at what this means? From Cambridge Dictionary: Lightweight “Weighing only a little or less than average” … euh… Scrum is lightweight. Of course, we’re not worried about Scrum tipping the scales physically. Scrum on! Then adapt.
Transitioning to Scrum, this focus shifts significantly. Instead of strictly adhering to initial requirements, Scrum teams aim to deliver maximum value through adaptive planning, iterative development, and frequent feedback loops. Don't want to miss any of these blog posts?
Kanban and scrum are agile project management methodologies that can be used for similar purposes, but each has its unique pros and cons. As a project manager, it’s important to understand the difference between kanban and scrum so you can determine the best approach for your team. What Is Scrum?
From the #Scrum Guide: The Scrum Team turns a selection of the work into an Increment of value. In Scrum, this act of choosing is not done by one person aloneits a collaborative effort by the entire Scrum Team. How does your Scrum Team collaborate to choose the right work? Scrum on!
What does it mean that “Scrum is a … framework…” (from the Scrum Guide). What can Scrum build? Scrum on itself… Nothing. Yet, Scrum brings us a focus working towards goals, and supports us planning towards these. Therefor teams can use Scrum to build (almost?) So, what for are you using Scrum as a framework?
From the #Scrum Guide: "4. Repeat" (in the section Scrum Definition; in a nutshell: 1. A Scrum Team keeps repeating the same steps: Sprint Planning the necessary work and the Daily Scrum Sprint Review Sprint Retrospective. How the team performs the Scrum Events will change. Scrum on! I t simplifies.
From the Scrum Guide: “Each element of the framework serves a specific purpose that is essential to…” Just to be sure we agree… From Cambridge Dictionary: “Essential: a basic thing that you cannot live without“. The purpose of each of the elements of the Scrum framework is essential. Don't want to miss any of these blog posts?
A scrum board is a critical tool for successfully practicing its namesake, the agile framework, scrum. If you’re unfamiliar, scrum is useful for teams that work on complex, adaptive problems. In short, scrum is lightweight, simple to understand, but difficult to master—even with the help of scrum software.
The Scrum Master role carries significant weight – you're accountable for the Scrum Team's effectiveness. That responsibility can be daunting, leading some Scrum Masters to try tackling everything simultaneously (leading to burnout), while others prioritize what feels most comfortable (producing low impact). What did you learn?
In the 2020 version of the Scrum Guide a new thinking model was added to the principles on which Scrum is founded - Lean Thinking. However, not enough justice is done in explaining WHY Lean Thinking was introduced or added to Scrum guide. And this stands true for the other accountabilities on the Scrum Team as well.
As Scrum.org professionals, we have coached, trained and mentored thousands of Scrum Masters and consulted the organizations they work with, and we’ve consistently encountered similar issues that not only limit Scrum Teams from thriving, but also restrict empiricism from working. That’s Mechanical Scrum.
From the Scrum Guide: A Product Owner orders the work for a complex problem into a Product Backlog. Not the usual use of the word when referred to in Scrum Quite a few questions come to mind when I think about this. To the Scrum Teamspecifically to the Developers who are part of it. Don't want to miss any of these blog posts?
From the Scrum Guide: “ We use the word “developers” in Scrum not to exclude, but to simplify. Maybe because we have another initiative called learnhow.simplification.works… Has the introduction of the Scrum framework simplified things for your team? Think about it: how is Scrum simplifying the work, the day-to-day?
In this blog post, you will see 6 professional prompts for the following topics: 1- Creating Sprint Goal 2- Creating Product Goal 3- Removing Impediment 4- Creating Definition of Done (DoD) 5- Improvement Suggestions Based on DORA Metrics 6- Conflict Resolution 1. Collaborative: The whole Scrum Team creates the Sprint Goal together.
In the Scrum Guide, the term backlog appears in two key Scrum artifacts: the Product Backlog and the Sprint Backlog. This definition raises some interesting questions about how the term backlog is applied in Scrum. This definition raises some interesting questions about how the term backlog is applied in Scrum.
How does Scrum HELP you? The Scrum Guide states that Scrum “helps people, teams, and organizations.” Scrum is not the goal itself, and it never should be. Scrum is there to support—not complicate—your journey. So, what’s the real challenge you’re calling on Scrum to help you solve? Scrum on!
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. Scrumban is part of an agile framework, a hybrid of scrum and kanban. It was created as a way to transition from scrum to kanban.
From the Scrum Guide: “Scrum is a lightweight framework … for complex problems.” We often hear that Scrum is designed for ‘complex problems,’ but what does that actually mean? This is where Scrum comes in. Scrum thrives in complexity by providing a framework for teams to learn quickly and respond effectively.
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 development teams. We’ll explore the scrum methodology in-depth, but before that, let’s start with a simple scrum definition. The Scrum Framework.
From the Scrum Guide: “Such tactics for using within the Scrum framework vary widely and are described elsewhere.” A lot of people I meet are looking to Scrum for specific solutions. In its introduction though the Scrum Guides explains that specific actions are to be looked for elsewhere. Scrum on! Why is that?
Scrum is a framework for organizing agile teams, and it’s processes and guidelines are excellent for improving team productivity. One reason scrum is so effective is that it clearly defines the different roles of the team. They act as the project manager for the scrum team, although the agile community generally doesn’t use that term.
A Scrum Master might sound like a character in a role-playing game, but it’s a serious job that’s rooted in leadership. The Scrum Master is responsible for ensuring a true Scrum process over the course of a project. Thanks to its many benefits, Scrum continues to grow in popularity. What Is a Scrum Master?
This blog aims to clarify these misconceptions by exploring what the Sprint Backlog is not and what it truly is, providing clarity and enhancing its effective use in Scrum. Understanding the true nature of the Sprint Backlog is essential for the success of Scrum. The Sprint Backlog is Not static.
“Scrum helps people, teams, and organizations generate value.” From the Scrum Guide) But what does value actually mean? Why would you participate in a Professional Scrum Training? Don't want to miss any of these blog posts? Have the “The Scrum Guide Explored” series weekly in your mailbox. Scrum on!
Scrum is a flexible framework that’s designed to help self-organized teams execute projects quickly in an agile environment. Thus, successful agile sprints make use of scrum software and scrum artifacts to convey key information, deliver transparency and keep the project rolling on time. What Are Scrum Artifacts?
One of the accountabilities that a Scrum Master has to fulfill is to make the Scrum Team effective. This includes the Scrum Master, as well. However, in my experience I have come across only a handful of Scrum Masters who understand the concept and who focus on improving and making themselves effective.
While practices and tools like Scrum or Kanban help teams live those values, no amount of process can overcome unchecked negative behaviours. For more on this, you can explore our related blogs: Why Agile Fails Agile and Scrum: Unravelling the Misconceptions What is a Scrum Master?
The Scrum Guide states: "The Scrum Team and its stakeholders inspect the results and adjust for the next Sprint." Where do adjustments happen in Scrum? Scrum enables adaptation at multiple levels; some examples: Product Backlog Adjusted after Sprint Reviews based on new insights and stakeholder feedback. Scrum on!
Today I’m partnering with Eylean to give you an overview of three agile methodologies: Scrum, Kanban and Scrumban. Scrum, Kanban and a method that blends the two (turning Scrum Kanban into Scrumban) are all quite different. Scrum is a way of managing the work within defined timescales called sprints. A Scrum board.
Over the years, Ive supported numerous Scrum implementations, from experiments within single teams to large-scale, company-wide adoptions. Throughout these experiences, Ive identified consistent red flags and challenges that significantly limit Scrums effectiveness. In this blog post, I share the most critical pitfalls Ive observed.
Trello leans heavily on kanban boards, but Jira offers that and scrum and sprint boards. Boards for scrum, kanban, backlog prioritization and sprint planning Custom workflows to take tasks from inception to completion Reporting and dashboard tools to get a clear picture of the project’s trajectory Trello vs.
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?
Can I put all that stuff from my experiences in one blog post, nope. Vision: The Product Owner needs to have clear vision about the product that is being created by the Scrum Team. As Scrum Guide says, "the Product Owner is accountable for maximizing the value of the Product resulting from the work of the Scrum Team".
From the #Scrum Guide: "Scrum is simple." If Scrum is so simple, why does it often seem so hard? The words in the Scrum Guide arent complex. The words in the Scrum Guide arent complex. Doing" Scrum is straightforward: assign roles, schedule events, create and maintain artifacts. How Do You Keep Scrum Simple?
Scrum is an agile way of working in which projects are broken into blocks, which are called sprints. The sprint planning meeting involves the scrum master, scrum product manager and the scrum team. This is a collaborative effort called a scrum ceremony. Daily Scrum Meeting. Sprint Planning Meeting.
Many teams tweak, adapt, or customize Scrum too soonoften before fully understanding its principles. The advice "try it as is" is grounded in real-world experience: many teams struggle with Scrum not because it doesnt work, but because they never truly tried it as designed. Discomfort is not a reason to modify Scrum.
That’s what is says “The Scrum Guide”. This reflects the Scrum Guide’s role: it provides foundational concepts, not prescriptive practices! Example: don’t go looking in the Scrum Guide for better refinement practices. Scrum is not saying you have to use Jira (even though the tool is pushed on teams a lot!). It’s a Guide!
From the Scrum Guide: “Scrum is a lightweight framework … generate value through adaptive solutions…” What are “adaptive solutions,” and why do they matter so much? Scrum isn’t just about solving problems; it’s about solving them in ways that adapt to your ever-changing environment. Don't want to miss any of these blog posts?
It’s used for tracking work in a project schedule or during a sprint in a scrum. Scrum teams working in an agile environment use a burn up chart to help them measure progress. The scrum team can make better decisions on the delivery scope by having a chart that has up-to-date data that is clearly communicated.
As a seasoned professional in the field of Scrum and Agile, I've often encountered the misconception that Scrum Mastership is confined to the world of software engineering. However, the principles and practices of Scrum are universal and can be applied across various industries.
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