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.
There is an important difference between the Scrum Master accountability, as described in the Scrum Guide 2020, and the Scrum Master role, as it is lived in different organisations. You can be a Scrum Master, while your job description and role in the organisation may slightly differ.
ScrumScrum is a lightweight framework that helps people, teams, and organisations generate value through adaptive solutions for complex problems. Both Scrum and Lean UX embrace an iterative and incremental approach. Scrum divides work into fixed-length Sprints, delivering usable Increments in each Sprint.
Agile has migrated from software development to touch just about every corner of the project management universe, and Scrum is one of the most popular frameworks for implementing it. ” Let’s begin by briefly defining Scrum. What Is Scrum? Scrum was developed by co-creators Ken Schwaber and Jeff Sutherland.
This free agile sprint plan template incorporates the entire scrum team to motivate and challenge them to drive success. There’s space to list the date when the issue has closed as well as who on the team is responsible for dealing with it. A column with the status tracks whether the issue is open or closed.
The role of the Scrum Master is often misunderstood. What was their interest in Scrum? What did they bring to the role of Scrum Master? Its helpful to consider WHO were the early adopters? Try to imagine 1995 through ~2005. It was common they had a well-established career. They had been a manager of teams for many years.
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.
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.
We’ll look closely at each software to see who wins in a Trello vs. Jira bout. Trello leans heavily on kanban boards, but Jira offers that and scrum and sprint boards. They also share features that foster collaboration allowing teams to access the software whether in the office, working remotely or in a hybrid environment.
The scrum master is a key member of the scrum team, but also a somewhat misunderstood one, which can make the hiring process problematic. Put simply, the scrum master is the person responsible for promoting and supporting scrum. However, as important as the scrum master is, the position is not project leader.
And - like the Scrum framework itself - it is easy to understand but can be hard to master. Even with the best intentions, Scrum teams might embrace the idea of incremental delivery, but still end up working on extensive requirements documents. Use this information to influence what the Scrum team works on next.
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.
Incremental delivery is the superpower behind the Scrum framework. Scrum is based on Empiricism, which requires Transparency, Inspection, and Adaptation. Incremental delivery is what makes Scrum work—it’s how teams stay aligned, learn, and adjust to keep delivering real value. But Scrum teams deliver value piece by piece.
In Scrum, the Definition of Done (DoD) plays a critical role in ensuring quality and transparency. A Definition of Done is a shared understanding among the Scrum team of what constitutes a finished Product Backlog item. Imagine two Scrum teams at the Scrum Cookie Company. But who defines this important concept?
AI has become a significant part of our lives, and there are claims that Scrum Masters may be replaced by AI. The answer to this determines if AI poses a real threat to Scrum Master roles. A Scrum Master's responsibilities can be divided into two main categories. In this video, Im gonna explore the validity of such claims.
Below are a few of the most common misconceptions about Scrum. . . During Sprint Planning, the Scrum Team choses a Sprint Goal, selects Product Backlog items they believe will best accomplish the Sprint Goal, and creates a plan for delivering the selected Product Backlog items. The Scrum Guide doesn’t define roles.
AI has become a significant part of our lives, and there are claims that Scrum Masters may be replaced by AI. The answer to this determines if AI poses a real threat to Scrum Master roles. A Scrum Master's responsibilities can be divided into two main categories. In this video, Im going to explore the validity of such claims.
To become a great Product Owner, I believe the PO should have following characteristics: Respected Vision Achiever Entrepreneurship Negotiation Empowered Collaborative Inspiring Proficient Available Respected: Scrum guide says, " for the Product Owner to succeed, the entire organization must respect his or her decisions. "
When Scrum Teams experience a work quality issue, they sometimes shift the responsibility for quality control to the Product Owner as a solution. Not only is this impractical, but it's also anti-Scrum. The Product Owner is accountable for maximizing the product's value resulting from the Scrum Team’s work. Here's why.
Remember that Scrum is founded on empirical process control, and that inspection is one of the three pillars. Each of the Scrum accountabilities participates in one or more inspections. So how about the Scrum Master in the Scrum Team. The Scrum Master can ask a lot of questions for this. Some examples include.
If you’ve ever wondered whether Scrum can work for hard deadlines, the answer is – yes! Not only can Scrum work in these situations, but in my experience, using this agile framework increases the probability of meeting challenging deadlines. Let me demonstrate these concepts with a story. This team faced a significant challenge.
Scrum - The Leader’s Perspective. If you’re leading Scrum Teams or generally are a leader in an organization that’s leveraging Scrum? Are you feeling a bit left out after reading the Scrum Guide ? The Scrum Guide describes the leadership required by the Product Owner, Scrum Master, and Developers.
A lot of people are passionate about Scrum, and why not? The 15th annual State of Agile Report reveals that over 90% of the teams working within an agile framework use Scrum. Last week, we talked about common misconceptions related to the Daily Scrum. This topic is discussed in Scrum.org’s Applying Professional Scrum class.
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. We are also very good at contrasting this with the ideal state of Scrum.
TL; DR: Scrum Team Failure This post on Scrum team failure addresses three categories from the Scrum anti-patterns taxonomy that are closely aligned: Planning and process breakdown, conflict avoidance and miscommunication, and inattention to quality and commitment, often resulting in a Scrum team performing significantly below its potential.
While not mentioned in the Scrum Guide and not part of Scrum, acceptance criteria are foundational guidelines to ensure the work item meets the required standards and fulfils the user's needs. This focus on predefined criteria helps maintain quality and functionality, aligning the final product more closely with user needs.
It’s something that a Scrum Team’s stakeholders, customers, managers and many others want to know. To get to an answer that provides meaningful information, your Scrum Team first needs to decide how to estimate. Estimation is a complementary practice in Scrum, which means that the Scrum Guide doesn’t tell teams how to do it.
TL; DR: Value Creation in Scrum. As a tactical framework, Scrum is good at delivering Increments into customers’ hands. As we work in iterations, we probably do that several times per month, mitigating risk by closing feedback loops. As a result, value creation in Scrum is not as straightforward as you might have thought. ??
We started the Scrum Guide for Leaders series with a discussion of what Scrum means for you as a Leader. Next, we discussed the conditions where Scrum's Empiricism, Self-Management, and Continuous Improvement can thrive. Next, We are turning to the Scrum accountabilities/roles. Scrum Team. Product Owner.
These organizations offer a variety of certifications that focus on different project management methodologies such as agile or scrum, or specific project management knowledge areas such as project scheduling, resource management or risk management. Scrum is part of Agile, which has become a standard in IT projects. Price: $300.
In this blog post, we focus on one specific question that was raised: “How to measure the success of an Agile Coach or Scrum Master?”. The success (or failures) of an Agile Coach or Scrum Master is not that straightforward to measure, and any causality with the success of a team you coach is difficult to prove.
Above: Pichler's (2024) strategy stack The product strategy Unlike a projects that focus on managing and delivering requirements, product strategy focuses first on the customer satisfaction gap with Scrum providing key strategic and tactical feedback loops regarding the success of the solutions developed to close that gap.
Welcome to Scrum Sutra — a series where I shall share a 3-min overview of each element of Scrum and how it connects with the other elements in the bead to form Scrum Sutra. Successful use of Scrum depends on people becoming proficient in living five values.” — Scrum Guide 2020.
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. ????
In Scrum, part of the Product Owner accountability is to provide a forecast that sheds light on possible answers to the when will we get there question. In Scrum, a forecast is not a plan. Why can’t we make promises about the future with Scrum? How do we forecast in Scrum? What is a forecast? Nor is it a promise.
In 2010 I started my first assignment as a Scrum Master. Mostly intended to help myself reflect on my role, receive feedback from other Scrum practitioners, and make improvements accordingly. Over the years, the sum of these blog posts resulted in the paper “ The 8 Stances Of A Scrum Master ”. The 6 Scrum Master Stances.
When I started my journey as a Scrum Master about 12 years ago, I read many books about Scrum. Although I’m not a highly technical guy, I have always worked closely with software development teams and the book contains so many great ideas that benefit development teams. I wrote this article with a big smile on my face.
TL; DR: Scrum Anti-Patterns GPT Can a Custom Scrum Anti-Patterns GPT align teams with Scrum principles? Dive into how leveraging custom GPTs might offer a novel path through Scrum’s common hurdles, focusing on creating actual customer value in the face of organizational and team-level challenges. ?
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?
When working with a brand-new Scrum team, whether it's a new member joining or a Scrum Master guiding the team, the challenges often stem from preconceived notions. It's not about the tools or techniques they think they know; it's about the foundational understanding of Scrum's essence. At its heart, Scrum is about empiricism.
I paint a Scrum-friendly environment and culture with words, which helps you imagine the ideal Scrum environment to inspire, encourage and guide your organization to move toward it. by building and delivering done increments early and often and closing the Sprint learning loops. They use metrics to lighten their way with data.
Reporting limitations, again requiring buying plug-ins to close the gap with commercial products Lacks advanced resource management features, such as capacity planning and workload balancing No mobile application Kanban boards only exist as plug-ins, which still aren’t fully functional Redmine Reviews G2: 4.0 Caterra: 4.5 Capterra: 4.1
TL; DR: My Top Ten Worst Scrum Anti-Patterns. I recently was invited to a Scrum.org Webinar, and I picked a topic close to my heart: the worst Scrum anti-patterns. So, without further delay, here are my top ten of the meanest, baddest Scrum anti-patterns I have experienced. ?? My Top Ten Worst Scrum Anti-Patterns.
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