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 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.
Starting with Scrum can feel overwhelming. It’s a framework with defined events, accountabilities, and artifacts that might seem rigid or even intimidating at first glance. The real magic of Scrum unfolds as you practice and improve over time. Scrum boards : Great for visualization, but not required.
The Scrum Master has to keep changing styles and stances as and when needed. However, when someone with not enough knowledge or experience picks up this hat, it often leads to Scrum Master Anti Patterns. Anti-pattern: Scrum Master as a technical lead This person has played a role of technical lead for quite long.
He says, Before complaining that Agile/Scrum/whatever is dead, consider instead that it's become a norm. And each of these vendors had “scrum” teams or rather in the words of Michael Kusters “scream” teams. In Scrum’s perspective, it is the job of the Scrum Master to make the Scrum Teams effective.
Speaker: Eric Naiburg, Chief Operating Officer at Scrum.org
Although Scrum has been around for more than 25 years, it is still new to many. In this session, we provide an overview of the Scrum framework, discuss how Scrum enables agility and ways that empiricism can empower the teams that use it. The 2020 Scrum Guide - ScrumEvents - Scrum Artifacts.
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.
No, the creators of Scrum were not lazy. The Scrum framework is purposefully incomplete, only defining the parts required to implement Scrum theory. Scrum is built upon by the collective intelligence of the people using it. What we mean is that Scrum is a framework within which teams work together to deliver value.
The Scrum way of working is being elevated with the advent of AI. So, we will be seeing a new generation of AI-powered Scrum Masters. To do so, I have created a list of useful AI tools to help Scrum Masters better adapt to this newcomer technology. In addition, it helps the Scrum Team track, manage, and pay back technical debt.
Velocity: In a company that I was working for, a SOW was established that defined that the Scrum Team will deliver 60 points worth of work every sprint. Effect: The Scrum Team started filling up the backlog with unrelated work items just to hit the mark of 60 points of work. Here are some examples of the watermelon or cobra effect.
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.
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 ScrumEvents will change. Scrum on!
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?
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?
As an agile coach I often have Scrum Masters come up to me because management is complaining there are too many meetings in Scrum and that their developers aren't 100% utilised on developing the products. Why is it that so many people walk away from a Scrumevent saying it was a waste of time, boring or not relevant to them?
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).
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. Scrum on! What are these elements?
What is the ‘Navigating the ScrumEvents’ Series? If you or your team are new to Scrum, you can use this as a starting point to answer, “what should we be doing and why?” for each ScrumEvent. The Sprint Sprint Planning Daily Scrum Sprint Review Sprint Retrospective Daily Scrum - What’s The Point?
What are the 5 events in Scrum? Chances are that you said something like “Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective, and…. The Sprint is the most commonly overlooked event in Scrum. In fact, many people don’t even realize that it is an event in Scrum. Can you name them?
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?
One of the clichés about Scrum is that it is “easy to understand but difficult to master” The first part of that is obvious with the Scrum Guide is only eleven pages (if you don’t count the title page, purpose and table of contents). However, the immutable design of Scrum is where challenges occur.
One of the first things you learn about Scrum is that it has five events. One of these events is the Daily Scrum: a short, 15-minute daily check-in for Developers. At the end of our first Sprint, during the Retrospective, someone pointed out that the Daily Scrum alone would add over 250 meetings a year.
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?
What is the ‘Navigating the ScrumEvents’ Series? If you or your team are new to Scrum, you can use this as a starting point to answer, “what should we be doing and why?” for each ScrumEvent. The Sprint Sprint Planning Daily Scrum Sprint Review Sprint Retrospective Sprint Retrospective - What’s The Point?
5 Grundsätze für die effektive Moderation von ScrumEvents Unerfahrene Scrum Master glauben, sie müssten möglichst viele Facilitation-Techniken kennen. Zweckmäßigkeit: Scrum Master helfen dem Team, das Ziel nicht aus den Augen zu verlieren. Scrum Master helfen dem Team, ein gemeinsames Verständnis zu schaffen.
Sprint Retrospective - The event to tap into your improvements. Sprint Retrospective is the concluding event on the Sprint, timeboxed for 3 hours or less for 1 month Sprint. This is an Inspect-Adapt opportunity for the Scrum Team to figure out how they could become more effective in the upcoming sprint. What did not go well?
These events provide a unique opportunity to learn from experts, network with peers, and gain hands-on experience with new tools and techniques. Don’t miss the chance to connect with the global Scrum community! Don’t miss the chance to connect with the global Scrum community!
What is the ‘Navigating the ScrumEvents’ Series? If you or your team are new to Scrum, you can use this as a starting point to answer, “What should we be doing and why?” for each ScrumEvent. Anyone on the Scrum Team can take this on. This can help with Daily Scrum conversations and focus for the team.
Every Scrum team should have a Scrum Master. Scrum Masters are important to the success of Scrum within the organization and impact the Scrum team's ability to deliver value and improve customer outcomes. But Scrum Masters are human. Is the Scrum Master trying to help streamline the Requirements process?
What is the ‘Navigating the ScrumEvents’ Series? If you or your team are new to Scrum, you can use this as a starting point to answer, “what should we be doing and why?” for each ScrumEvent. The Sprint Sprint Planning Daily Scrum Sprint Review Sprint Retrospective The Sprint - What’s The Point?
Früher dachte ich, ich würde die ScrumEvents erfolgreich moderieren, wenn ich folgende Punkte beachtete: Ich wiederholte das Ziel des Meetings, um sicherzustellen, dass es von allen verstanden wird. Seitdem ich das realisiert habe, gestalte ich ScrumEvents anders. Schauen wir uns gemeinsam die Events in Scrum an.
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.
In some of my classes , people tell me they are using Scrumbut they can't call it Scrum. Too much stuff added in the name of Scrum. One student told me her company started using Scrum when they hired a vendor who claimed to be an expert. Now, after that frustrating experience, the company wont call anything Scrum.
What is the ‘Navigating the ScrumEvents’ Series? If you or your team are new to Scrum, you can use this as a starting point to answer, “what should we be doing and why?” for each ScrumEvent. The Sprint Sprint Planning Daily Scrum Sprint Review Sprint Retrospective Sprint Review - What’s The Point?
A fundamental part of Scrum is the ideal of continuous improvement. Scrum Teams are always getting better. The special ingredient that makes these Scrumevents successful is a healthy dose of positivity. In this event, we inspect ourselves and what we can do better. That's never easy.
Scrum is a framework within which teams work together to deliver products in complex environments. The Scrum framework includes five events: The Sprint Sprint Planning Daily Scrum Sprint Review Sprint Retrospective. Each of the five events in Scrum is time boxed. Why are events time boxed?
A project meeting is a regularly occurring event where some or all of the project team and stakeholders gather to discuss the project. Project management meetings are communication events and clear communication is what keeps projects on track. This is a collaborative effort called a scrum ceremony. Daily Scrum Meeting.
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. "
The Scrum framework consists of five events , three artifacts and three accountabilities. These events, artifacts and accountabilities provide a framework within which teams work together to deliver value. The Product Backlog is an important artifact in Scrum. Refinement is an important activity for 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. It defines: 5 values, 3 accountabilities, 5 events, and 3 artifacts This sounds easy to grasp. How Do You Keep Scrum Simple?
Many conferences have early bird pricing so it is worth checking out the events that interest you as soon as you can in case you need to get corporate funding to attend. Make sure you sign up for the free Attend a Conference Checklist before you go to any of these events. Global Scrum Gathering: Austin, Texas, USA, 20-22 May 2019.
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.
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