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.
Many teams and organizations struggle to get the most out of Scrum. In a previous post “Don’t blame “agile” for existing problems” I shared my analysis why agile or Scrum itself often gets the blame. In this second post out of three I will focus on what the most common mistakes are with Scrum that lead to dysfunctional Scrum.
TL; DR: Scrum Master Engagement Patterns. Last year, I ran a (non-representative) survey on how Scrum Masters are allocating their time when working with a single ScrumTeam. The first article of this series will address the Scrum Master engagement with the DevelopmentTeam.
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 which easily can impede any agile transition. Common Scrum Stakeholder Anti-Patterns. The Sprint.
One might conclude that agile approaches to project management, such as Scrum, mean there is no need for gate reviews. We say the same thing if one adopts gate reviews for every product development project. Let’s explore a typical product development project’s phases, goals, and metrics reviewed at each gate.
As project managers, it’s important that we know how to best support our developmentteams (and vice versa), especially in Agile environments. A lot of the points below relate to teams in Agile environments , but can apply to any type of project team. Secret #7: Motivate the team. Elisa Cepale.
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.
It’s a visual tool that makes it easy for project managers and their teams to see how much work has been done and how much work is left. It’s used for tracking work in a project schedule or during a sprint in a scrum. Scrumteams working in an agile environment use a burn up chart to help them measure progress.
Product features and stakeholder requirements constantly change, and your initial product development plan might look very different as the project evolves. Agile release planning, also known as scrum release planning, is an alternative to the traditional waterfall approach. How do you create a scrum release plan?
The Sprint Goal is mentioned numerous times in the Scrum Guide, however it can be over looked by many teams or seen as an "oh yeah" moment when teams are finishing Sprint Planning. One purpose of the Sprint Goal is to provide focus to the DevelopmentTeam during the Sprint. Not a great place to be in!
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: 70 Scrum Master Theses. The following 70 Scrum Master theses describe the role of from a holistic product creation perspective. The theses cover the role of the Scrum Master from product discovery to product delivery in hands-on practical manner. The Role of the Scrum Master. It is not a mere management role.
In this article, we will debunk 10 common myths about Scrum. Now, I'm not saying that chaos dragons are real, but I am saying that Scrum is not chaos. Scrum can help. Scrumteams can adapt based on feedback received and can shift their focus away from unnecessary features towards features that deliver the most value.
As project managers, it’s important that we know how to best support our developmentteams (and vice versa), especially in Agile environments. Approaches you might consider in an Agile environment are Scrum, Kanban or Scrumban , but there are others. Secret #7: Motivating the Team. This is a guest post from Elisa Cepale.
Often I hear people say that Scrum does not take care of risk: there is no risk log, risk is not on the agenda of the Sprint Review or Retrospective as a standard agenda-item. The DevelopmentTeams need to be accountable for the quality of the product and how it's made. That's a risk right there!
What is a Scrum Master? What are the differences between a Scrum Master and Project Manager? Isn’t a Scrum Master some kind of an Agile Project Manager? There is almost no overlap between the role of Scrum Master and the position of Project Manager. What is a Scrum Master? What a Scrum Master does.
We all know that Scrum is a framework, but for instance, imagine Scrum to be a gauntlet that holds all the six infinity gems. If so -what could be its infinity stones that could fit the scrum gauntlet which makes scrum so powerful and inevitable? Let’s explore together powers of the Scrum Infinity Stones!
A Sprint Review is perhaps one of the most difficult elements in the product development with Scrum. When I started out as Scrum Master, I didn’t attach much importance to this meeting. Therefore, during the first three years in this role, all my sprint reviews were limited to showing the results to the Product Owner.
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.
I am a software developer and Scrum Teacher. I have been in software development for 23+ years and have worked on various technologies and have played the role of a developer, analyst, project manager, delivery manager, scrum master, product owner, and coach. What is the Scrum Framework?
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?
one of the founders of Scrum?—?pointing This picture underscores the most essential rule in Scrum: create “Done” software every Sprint. But many teams struggle with this rule. An increment is considered “Done” by the DevelopmentTeam, but requires further testing and stabilization in the next Sprint.
Looking back a couple of years ago, I had a chance to work with the great team. They are a great team, but not from the beginning.that was a broken team when I came. - The team used Scrum but the Transparency was lost. DevelopmentTeam hid issues from Product Owner when he came to ask. If we failed?
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.
During a recent meetup of The Liberators Network, we got together with 30 enthusiastic Scrum Masters. This post combines the shared experience of a large group of Scrum Masters. Anything less risks keeping assumptions alive about what is needed, how difficult or how valuable it will be. Done” is the driver. Involve stakeholders.
TL; DR: Pure Scrum? Can you rely on pure Scrum to transform your organization and deliver value? While Scrum excels in simplicity and flexibility, applying it out of the box often falls short in corporate contexts due to limitations in product discovery, scaling, and portfolio management. Not always.
It is planned by the Product Owner that the increment that will be inspected tomorrow will be released at the end of the Sprint Review. The Scrum Master says, "The team stays until 9:00 p.m. Is this behavior really aligned with the sustainable pace advocated by the Agile Manifesto and Scrum's values ? . Are you certain?
At your next Sprint Retrospective, why not work with your Scrumteam to identify a New Year's Resolution? Focus on improving your Scrum game in 2024 with one of these five resolutions to enhance collaboration within your team and deliver value sooner to your customers. 4) Try Scrum. 3) Try Flow Metrics What is it?
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.
Scrum is easy to understand, yet difficult to master. The Scrum Guide says so and it's true. If you have worked with Scrum in your organization you probably recognize it also. It's not difficult to start with Scrum. The good thing about Scrum is that the framework is lightweight and therefor it's not difficult to start.
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.
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.
The Project Manager is typically concerned with day-to-day progress of the DevelopmentTeam. They rarely (or never) miss a Daily Scrum, they’re involved during the Daily Scrum and it might just be that they’re asking individual team members what they’ve done, what they’re going to do and if there’s anything blocking them.
Conversation : Developers, exploring the card, communicate with the Product Owner, in order to gain knowledge about the business domain and to be able to offer valuable ideas for implementation. Many important aspects bypassed the developer’s attention turns into re-work of existing features. How to Fill a User Story Canvas.
If you’re having a similar question about the Scrum Master vs the Project Manager, then check out this blog. The Product Owner is one person (not a committee) responsible in the Scrum Framework for maximizing the value. The Product Owner also shouldn’t track and measure team progress. What is a Product Owner?
Welcome back to the Scrum Master blog series with yours truly. As we enter the new year, we are seeing Scrum becoming the most commonly used framework to manage complex product delivery in the industry. For example at iPrice , the company that I currently work with, we have set the bar high for the Scrum Master role.
So how do you scale Scrum to the limit? Meet Peter, he’s a product owner of a new team starting on the greatest invention since sliced bread. In order to meet demands while adding new features, Peter needs to either get more value out of his teams and if that is no longer possible, add more team members.
Did you know the word “Manager” does not show up once in the Scrum Guide ? In this blog post, I’ll explain how it’s possible for managers to work with ScrumTeams so no one has to worry about rebuilding their resume. Scrum is about getting work done, not about addressing organizational structures.
I recently attend the Professional Scrum Master II (PSM II) course and I'd like to share my thoughts with you about it. . I am a Professional Scrum Trainer (PST) and intend to deliver the PSM II course soon. I took the course as part of the process but viewed it with my Scrum Master head and not as a PST. . First, a confession.
In many organisations I see Scrum not producing its anticipated value. But there also is a universal anticipated value of Scrum. The Scrum Guide says about Scrum's purpose: “A framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value.”.
The Product Owner is a critical role in Agile and Scrum. And although the Scrum Guide doesn’t give much guidelines around great product ownership, the role is still absolutely necessary for great Agile and ScrumTeams. A Product Owner guides the efforts of their Scrum or Agile Teams. Scrum Reading List.
What has always struck me in this discussion is the fact that Scrum is a tool useful to accomplish one primary task: delivering value to customers of emergent products in complex environments while mitigating an organization’s exposure to risk at the same time. Timeboxing and delivery : “When things are done, they are done.
In the previous article, we have discussed how Scrum Masters need to master many things. In this article we are going to discuss one of the stances that the Scrum Master need to master, that is the facilitation stance. So we can also say that the Scrum Master is partly responsible for poor decision generated by the group of people.
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.
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