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 developmentteams. We’ll explore the scrum methodology in-depth, but before that, let’s start with a simple scrum definition.
I think that a lot of people are surprised to learn that Scrum is not just for software development. Scrum was first presented in 1995 by Ken Schwaber and Jeff Sutherland. Later, the Agile Manifesto, written in 2001, identified 12 principles and 4 values which are important to the smooth operation of Agile teams.
But it’s best defined by scrum as a model. Scrum is a way to manage a project within an agile framework and is made up of three roles: product owner, scrum master and team. The product owner is focused on the business side of the project, the scrum master is the expert, who acts like a coach. What Is a Sprint?
Our team leader was educated with Scrum and wanted to see if it would work. This led to large-scale transformations where the principles of Agile were applied beyond developmentteams, often with varying degrees of success. Scrum’s simplicity is its strength, but many still haven’t unlocked its full potential.
The secret to scrum is simplicity, even in the face of complexity. And although scrum is simple at heart, it can be difficult to master. Scrum requires self-organizing teams that can quickly solve problems in unpredictable environments. Scrum ceremonies are meetings that are unique to scrumteams.
TL; DR: A Remote Sprint Review with a Distributed Team. This seventh article now looks into organizing a remote Sprint Review with a distributed team: How to practice the review with virtual Liberating Structures, including and giving a voice to team members, stakeholders, and customers.
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.
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.
In this blog post I explain why the Sprint Goal is key for an effective implementation of Scrum and how it is widely present in the Scrum framework by exploring its “lifecycle”. . Scrum is defined as a framework to address complex problems while delivering products of the highest possible value. This is the core of Scrum!
TL; DR: Demand Creates Supply and the Job Market for Scrum Masters 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. Do you want to get this article in your inbox?
Being an effective and successful Scrum Master requires a wide variety of skills, knowledge, and experience. This variety is captured in the stances of a Scrum Master. The Scrum Master is expected to act as a teacher, impediment remover, facilitator, coach, mentor, and change agent. Create a virtual Scrum Quiz.
TL; DR: Scrum Master Interview Questions (1). 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 methodology, but a framework.
TL; DR: 15 Sprint Review Anti-Patterns. Answering this question in a collaborative effort of the ScrumTeam as well as internal (and external) stakeholders is the purpose of the Sprint Review. Given its importance, it is worthwhile to tackle the most common Sprint Review anti-patterns.
With the launch of the Kanban Guide for Scrumteams in 2018, its 4 flow metrics have gained more popularity amongst the Scrum community. It has helped Scrumteams shed a new perspective on how to manage the flow of product backlog items (PBIs) through their sprint backlog all the way to a production environment.
One thing that every team has had in common is that, at one time, they were new to Scrum. When I engage with teams to discuss implementing the Scrum framework, they often raise potential impediments to adopting Scrum. Below are the five most common objections to Scrum and why they don’t hold any weight. .
A good product vision will be aspirational, offering reasons as to why the team is working on the product now, and for whom. It should motivate teams to see this not merely as another job but a mission that fulfills an important need. The product vision is also a way for a manager to stay present in the project without micromanaging.
TL; DR: A Remote Daily Scrum with a Distributed Team. We had a look at common remote agile anti-patterns; we analyzed remote Retrospectives, Sprint Plannings as well as remote Sprint Reviews based on Liberating Structures. The Purpose of the Daily Scrum. The Daily Scrum is held every day of the Sprint.
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!
TL; DR: The Scrum Guide 2020. The Scrum Guide 2020 is available now: Change is coming to make Scrum more accessible and inclusive beyond software development. Learn more about the changes, download the brand new and free Scrum Guide 2020 Reordered to spot patterns quickly, and join the Scrum community discussion.
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 have redesigned our Scrum Framework poster and have made some changes. . . . Here is an explanation of the elements we have presented differently compared to the Scrum.org poster [1] and the reasons why: . Scrum Events . The heart of Scrum is a Sprint, a time-box of one month or less” [2]. Scrum Artifacts .
During a recent meetup of The Liberators Network, we got together with 30 enthusiastic Scrum Masters. And what will make your future success possible (Future~Present)? This post combines the shared experience of a large group of Scrum Masters. In most of the success stories, the involvement was not limited to the Sprint Review.
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.
In August 2018, Scrum.org launched the Professional Scrum Master II class. The intention of this class is to offer the Scrum community an advanced class designed to support Scrum Masters in their professional development. What is the value of Liberating Structures for Scrum Masters?”.
Scrum, an agile framework for small teams, especially harnesses the benefits of retrospection. Scrum works under the assumption that customers regularly change their minds about what they want or need. The entire team is present for the sprint retrospective. The Scrum Master’s Role in a Sprint Retrospective.
By now, most organisations are using Scrum, however, many of them feel like the agility of their organisation has degraded, and they might be right! Inclusive Scrum is about looking at the full value chain and organizing your Product development effort around that. Whereas low agility Scrum might actually hurt your agility.
Scrum is not a one-size-fits-all solution, a silver bullet, or a complete methodology. Instead, Scrum provides the minimal boundaries within which teams can self-organize to solve complex problems with an empirical approach. You may also discover that the way your team uses Scrum is not as light-weight as it could be.
As per Scrum Guide – The Sprint Goal is an objective that will be met within the sprint by implementing the Product Backlog , and it guides the DevelopmentTeam on why it is building the Increment. During the Sprint Planning , the product owner presents business objectives for the Sprint and an ordered Product Backlog.
The 2019 Scrum Master Trends Report by scrum.org and the State of Agile 2018 shows numbers that provide insight in the maturity of agile adoptions. More than 80% of the Scrum Masters (respondents) claim their organization is in or below a “still maturing” level. Pre-Scrum waterfall . Starting with Early Scrum.
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.
As Scrum Trainer I get to meet a lot of teams and hear of many different ways to do Scrum. Most are valid ways, yet some seem more aligned with the values of Scrum or the purpose of the specific Scrum Element. In this post we'll have a look at the Sprint Review. Yet, there is nothing to be done about it now.
“Scrum” is a phenomenal subject – i.e. if you are familiar with it. As an Agile project manager, I have seen my fair share of so-called “Scrum Masters” and “Agile Experts” claiming to be masters of their craft. The truth, however, is that they don’t know a lot of things about Scrum and Agile. Introduction – Why Scrum?
While everyone will appreciate the effort, participating in a 2-day workshop does not mean that they mastered navigating the waters of dual-track Scrum, for example. Instead, the management ought to provide the teams with goals and guidance on how to achieve these, along with funding sufficient to meet the objectives.
Do you frequently find yourself in Sprint Reviews that only consist of a PowerPoint presentation? Or entirely without users, customers and other stakeholders present? Our experience, as well as that of Scrum Masters we meet, is that the Sprint Review often takes the shape of a demo — nothing more.
This article is the fourth in a series of “Kanban and Scrum – Stronger Together”. In the most recent post in Steve Porter’s series, Yuval Yuret presentsScrum in a manner that is intended to educate Kanban teams. The presentation of these principles have been refined and one addition was made for clarity.
The Scrum Guide on the Sprint Retrospective. The Scrum Master encourages the ScrumTeam to improve, within the Scrum process framework, its development process and practices to make it more effective and enjoyable for the next Sprint. Source : Scrum Guide 2017. Sprint Retrospective Anti-Patterns.
Now let’s have a look if this can also work out for your Daily Scrum. What does the Scrum Guide say about the Daily Scrum? The DevelopmentTeam uses the Daily Scrum to inspect progress toward the Sprint Goal and to inspect how progress is trending toward completing the work in the Sprint Backlog.
Most people, as well as me, are used to Scrum (or more likely Zombie-Scrum or Scrum-But ), but I believe it is too early to do proper Scrum here. Or rather one column per stage for the tasks (i.e., “in development”, “in testing” etc.)? Also, we have quite diverse roles in the team (i.e.,
The 2019 Scrum Master Trends Report by S crum.org and Age of Product and the State of Agile 2018 show numbers that provide insight in the maturity of agile adoptions. More than 80% of the Scrum Masters (respondents) claim their organization is in or below a “still maturing” level. Pre-Scrum Waterfall . Starting with Early Scrum.
Scrum meetings are an integral component of a work environment which adopts the Scrum methodology. They are considered to be an invaluable source of collecting information and feedback from the developmentteam and help in keeping the team aligned with the Sprint goals. Types of Scrum Meetings.
I looked at how this can work out for your Daily Scrum , and now we've arrived at the last specific event of Scrum: the Sprint Review. A small reminder from the Scrum Guide: “A Sprint Review is held at the end of the Sprint to inspect the Increment and adapt the Product Backlog if needed. So they do.
Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. You can observe implicit coordination in Scrumteams when you look at how work moves across a Scrum board, or on- and of the Sprint Backlog. This is also why the Scrum framework includes the Definition of Done.
On June 30th Christopher Handscomb and I presented a webinar based on our joint research on the topic of the value of enterprise agility. Of course, a C-Level exec does not have to learn Scrum or Kanban to the level of detail required by teams and supporting functions, but getting some appreciation and understanding is a must. . .
The first part contains my personal journey in becoming a Scrum Master, the second part includes recommendations for new Scrum Masters. Part 1 — Becoming a Scrum Master. Nine years ago I changed my title from Project Manager into Scrum Master. Do you have any recommendations for my Scrum Master journey?”.
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