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.
TL; DR: DevelopmentTeam Anti-Patterns. After covering the Scrum Master and the Product Owner, this article addresses DevelopmentTeam anti-patterns, covering all Scrum Events as well as the Product Backlog artifact. The Role of the DevelopmentTeam in Scrum.
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.
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.
Planning poker® is a great technique for scrumteams. It is a team-based estimating approach to work out the efforts involved for achieving business goals. Even serious developers like gamification! Our company is a part of Wisebits Group and develops an online entertainment streaming service. What we chose.
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. So he began our education, teaching us self-management and relentless focus on Done.
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?
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.
Agile is a project management methodology that allows developmentteams to set up a dynamic work management framework. Agile principles also apply to other project management methodologies derived from agile such as kanban or scrum. Teams that work in an agile environment need flexible project management software.
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.
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?
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.
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.
Intended audience: Scrum masters, Product owners, Managers and Agile coaches. I was working with various groups over the last year and noticed some commonalities in the problems they faced. I advise to start finding one person to be the single Product Owner for all teams. This dynamic is very common for component teams.
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.
Scrum Methodology. What It Is: Scrum is a short “sprint” approach to managing projects. The scrum methodology is It’s ideal for teams of no more than 10 people, and often is wedded to two-week cycles with short daily meetings, known as daily scrum meetings. It’s led by what is called a Scrum master.
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.
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. ?
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.
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.
How team cognition helps us understand what cross-functionality should look like for Scrumteams. What team cognition looks like for Scrumteams, and what signs tell you whether it's there or not. So What Does This Mean For ScrumTeams? What does this mean for your ScrumTeam?
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?
In 2017 I was talking to the head of the Agile Coach Group of a large bank. Smart people come up with the best process that the teams, groups, and branches should follow. They create Spreadsheets with questions/measures to assess how well these teams, groups and branches are complying with the standard way of working.
I facilitate daily standup meetings for our support team. When I started working for White October we followed the conventional “scrum” format, where the team get together, share what’s new, what’s challenging and what’s happening, and everyone gives feedback and makes suggestions to unblock each other. Not really.
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. The participants also agreed that by delivering done software every Sprint, stakeholders start trusting the experience-driven approach of Scrum.
Scrum is a popular Agile project management framework that has been adopted by organizations worldwide. A scrum master is a critical member of a scrumteam, responsible for facilitating the process and ensuring the team follows scrum practices. What is a Scrum Master?
Once you have a draft, review it. Once the vision statement has been reviewed by those who created it, share it with others in the organization, such as project stakeholders, the developmentteam, the Scrum master and Agile mentor, if you’re working within a Scrum/Agile framework.
A few days back I did a Scrum Tapas Video explaining what are few of the rules within Scrum. Besides these rules, there are also certain guidelines which help the ScrumTeams to make the best possible use of Scrum framework to create maximum Business Impact. The impact of it would vary based on team context.
When I started working for White October we followed the conventional “scrum” format, where the team get together, share what’s new, what’s challenging and what’s happening, and everyone gives feedback and makes suggestions to unblock each other. These make the daily scrum fun! Not really.
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.
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.
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 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.
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.
What the Scrum Guide says: “Cross-functional teams have all competencies needed to accomplish the work without depending on others not part of the team. The team model in Scrum is designed to optimize flexibility, creativity, and productivity.” - K. Sutherland, Scrum Guide, 2013. Schwaber and J.
Do you frequently find yourself in Sprint Reviews that only consist of a PowerPoint presentation? Or bored out of your wits because it keeps turning into a huge group conversation where people talk over others or keep revisiting topics that have already been addressed? In this post, we share the design for a Sprint Review.
“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?
Teams/groups then come up with their OKRs. Teams/Groups share their intent with each other and with relevant leaders to help ensure alignment in an environment of empowerment/autonomy. . The Scrum framework provides one example of how such a cadence could look. To inform about why rather than prescribe what/how.
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.
DevelopmentTeam Organises Its Own Work. The DevelopmentTeam is both self-organising and cross-functional and by the end of each Sprint provides an increment that is ‘done’ and releasable. The team defines how to organise work in a Sprint. The Scrum Guide, 2017). No need to conduct a code review.
We know from experience that the best way to unleash teams is to ask questions instead of giving (your) solutions. The best teams we know invest heavily in learning the skills to ask the right questions at the right time and then work together to answer it. These questions are designed for ScrumTeams that develop products.
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.
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