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
One of the first things that I usually hear after describing the Scrum framework and its five events to someone new to Scrum is, “that’s a lot of meetings!” . . Examining the five events, the first thing to point out is that the Sprint is not a meeting; it’s a container for all the other events. The Sprint.
Many well-meaning Scrum practitioners have misconceptions about Scrum, which sometimes leads to creating “rules” that do not exist in the framework. Scrum is deliberately incomplete because the framework is used in complex environments where simple best practices won’t fit all situations.
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?
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?
Now, you might be thinking what exactly a dance has to do with cadence in Agile? Let’s start first with the definition of cadence. Cadence – Definition and Basics. One can define cadence in Agile as follows: Cadence is a regular, predictable pattern of development work in Agile. Working with Single Cadence.
Every Scrumevent has a maximum allowable time period to carry it out, called a timebox. When I tell someone that the Sprint Planning event is timeboxed at eight hours, I usually receive shocked looks. There seems to be a misunderstanding about applying timeboxes in Scrum. ScrumEvent Timeboxes. Eight hours!”
One of the first things that people new to Scrum learn about is the five events. The five events in Scrum are 1) the Sprint, 2) Sprint Planning 3) Daily Scrum, 4) Sprint Review and 5) the Sprint Retrospective. When people first start learning about Scrum, it can seem like Scrum requires many meetings.
When my team first started holding a daily scrum meeting, it honestly felt awkward. From the lessons I’ve learned through experience, I’ve compiled nine best practices that have helped our daily scrum meetings stay focused and efficient. The Purpose of the Daily Scrum Meeting. Keep the Daily Scrum Meeting Short.
Scrum is the most popular Agile framework. According to the latest State of Agile survey from Digital.ai, 90% of teams who are using an Agile framework are using Scrum. I like to think that this is because Scrum is a goldilocks framework … with just enough - but not too much - structure. That is the power of Scrum.
In Kürze: Die 4 Elemente der Scrum Empirie. In seinem Theorieteil verweist der Scrum Guide auf die drei Elemente der Scrum Empirie: Transparenz, Inspektion und Adaption. Ein viertes Element, das die Grundlage für die Empirie bildet, ist jedoch in einem Satz über die Scrum-Werte versteckt. Die Theorie der Scrum Empirie.
The teams at his company had well established cadences for their Scrumevents; well-oiled Daily Scrums that are done within 15 minutes and result in transparency of what the team will do for the next 24-hours. The Scrum Guide is explicit in stating that Scrum is a framework.
Scrum, in its more general definition, is a simple framework to help us address complex challenges. Product development is the subset of complex problem domains where Scrum took root first; by explicitly acknowledging software and new product development to be complex work, serving to deliver complex products in complex circumstances.
In Scrum, the Product Owner is accountable for maximizing product value for the customer. That’s the focus of the entire Scrum framework, where value is delivered frequently and incrementally. But sometimes, the customer can jeopardize the value the Scrum Team is set to deliver. Sometimes, there’s a middle ground.
I was hired by a bank to help them to get started with agile and Scrum. Most people who see the value of the Scrum Master role will agree that a seasoned scrum master can support up to three experienced teams when sprinting. But is one Scrum Master enough to start up three teams from scratch simultaneously? Day 4 and 5.
SAFe includes Scrum - so how come many Scrum practitioners and thought leaders consider it unsafe? It takes advantage of established frameworks and techniques that work well - Scrum being the first and foremost of those. SAFe's Scrum Master is more of an Agile Team Lead. I hear a lot of questions and claims.
In December 2020, my friend Adrian Galarza and I delivered a Scrum.org Scrum Pulse Webinar - A Cycle Time Journey: 164 to 8 Days in 6 Months that summarized the journey of Adrian’s Scrum Team. STAKEHOLDER ENGAGEMENT: How did the scrum masters engage stakeholders outside the team to show up and collaborate more? BACKGROUND.
Figuring out the right Cadence . It’s all about finding the “goldilocks” cadence that provides frequent enough transparency and the opportunity to inspect and adapt at the right level. There can be a different cadence for everyone involved in achieving an OKR as compared to the cadence involving all stakeholders interested in that OKR.
I was hired by a bank to help them to get started with agile and Scrum. Most people who see the value of the Scrum Master role will agree that a seasoned scrum master can support up to three experienced teams when sprinting. But is one Scrum Master enough to start up three teams from scratch simultaneously? Day 4 and 5.
TL; DR: Scrum Master Anti-Patterns. The Sprint Planning is a core event that defines how your customers’ lives will improve with the following Product Increment. Join Stefan in one of his upcoming Professional Scrum training classes ! This resulting plan is created by the collaborative work of the entire Scrum Team.
Each agile framework provides its own ceremonies but given that Scrum is still the most commonly referenced one, let’s focus on that framework’s events. The Scrum Guide calls sprints the heart of Scrum as these time boxes set the cadence for all other events.
In its theory section, the Scrum Guide refers to the three elements of empiricism: transparency, inspection, and adaptation. However, a fourth element, foundational to enable empiricism, is hidden in a sentence on Scrum Values. Read on and learn more about the complete picture of Scrum’s empiricism. ???? Empiricism.
TL;DR: The Scrum Product Owner in 58 Theses. The Product Owner theses also address the Product Owner’s part in Scrumevents from Sprint Planning to Sprint Review to Sprint Retrospective, and the Daily Scrum. The Product Owner is also the most vulnerable Scrum role. Do you want to get this article in your inbox?
Recently, I connected with Evan Cook, the founder of Head Down Heart Up (HDHU), a fitness and nutrition organization that has “The Perfect Fitness Framework,” which is a program based on Scrum, designed to simplify food and fitness. When did you start using Scrum, and why did you choose it as the model for the Perfect Fitness Framework?
This question "What is the duration of a Sprint" is seemingly simple, but depending on the interviewing situation, company, interviewer, and their familiarity with Scrum you might need to give them more or less details and answer additional questions your answer might bring up. Scrum, But. Sprint Duration - Where Size Matters.
A new version of Scrum guide was released last month. It contains commitments for each of the Scrum artifacts. Product Goal also reflects one of the values of Scrum: “Focus.” Now, every artifact in Scrum comes with a commitment. The formal artifacts in Scrum are three: Product Backlog. Commitment based Artifacts.
Sprint Planning is a core event, defining how your customers’ lives will improve with the next Product Increment. According to the Scrum Guide, the Sprint Planning answers two questions: “What can be delivered in the Increment resulting from the upcoming Sprint?”. Source : Scrum Guide, 2017. Diagram source: Scrum.org.
What is one of the most important aspects of holding the Scrum Master accountability? Read on to see why your mindset and what you bring of yourself to your Scrum practice are critical to success. Read on to see why your mindset and what you bring of yourself to your Scrum practice are critical to success. Open and curious.
SAFe includes Scrum - so how come many Scrum practitioners and thought leaders consider it unsafe? It takes advantage of established frameworks and techniques that work well - Scrum being the first and foremost of those. SAFe's Scrum Master is more of an Agile Team Lead. I hear a lot of questions and claims.
The following five simple events derived from Scrum offer leaders and managers a way of regularly checking-in with their teams, always being present for them without falling into the pitfalls of micro-management. These five events from Scrum strongly support a decentralised command approach. #1 1 – Planning.
If you’re also an experienced Scrum practitioner, you probably associate the time you started to use Scrum with the time you started to release more frequently. Transcending Scrum and the Sprint Increment? Before you recycle your copies of the Scrum Guide – can I ask you a couple of questions though?
We are Scrum practitioners. And Scrum is an Agile framework that organises teams using five events, three roles and three artefacts. . Skilful use of the Scrum framework creates environments biased toward action and optimised for transparency, learning and adaptation. agile-scrum-training. As an example.
If you’re also an experienced Scrum practitioner, you probably associate the time you started to use Scrum with the time you started to release more frequently. Transcending Scrum and the Increment? Before you recycle your copies of the Scrum Guide – can I ask you a couple of questions though? You were pretty proud.
My fellow PST, Glaudia Califano, and I were sitting in a café (at a time prior to the current lockdown due to Covid-19), having agreed to meet up with a Business Analyst who had reached out to us to have a chat about Scrum and Agile. The purpose of completing PBIs is so the goals of the Scrum team are met. . was our next question.
Like many Scrum Masters, Agile Coaches and Agile Managers, I am beginning to understand organizations are complex adaptive systems. One of the powerful properties of Scrum is that it makes a very clear distinction in roles, events and artifacts. Let’s look at a Scrum example. Image by D.
I’ve always been intrigued by the different ways in which Scrum Teams go about their Sprint Reviews. The time needed to prepare and conduct yet another “Scrum meeting” is not typically seen to be a priority under such conditions. “A good review from the critics is just another stay of execution” -- Dustin Hoffman. It is no soft option.
Same with Scrum! Same with your Development Team(DT) or Scrum Team(ST) : Are you having fun? Great DT's considers their Scrumevents as an opportunity for collaboration and conversations. Barry Overeem, his insightful white paper on “ Characteristics of a Great Scrum Team”. Consistency always beats intensity.
By Lavaneesh Gautam , Professional Scrum Trainer Effective Stakeholder Engagement is key to the success of the product and one of the essential skills all product people should have. By Lavaneesh Gautam , Professional Scrum Trainer Question 1: What Message Do We Want To Provide? release roadmap) events as well.
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 presents Scrum in a manner that is intended to educate Kanban teams. Values shouldn’t be expressed as goals like they are in the Scrum Guide. Disclaimer.
In both SAFe/Scrum it is a self-managing team of self-managed teams with a couple of key roles at the team of teams level. . Scrum theory emphasizes Empiricism and Self-management, coupled with Flow in recent years. Scrum theory emphasizes Empiricism and Self-management, coupled with Flow in recent years. Lean/Agile Leadership.
Develop on Cadence; Release on Demand. In SAFe®, this is known as Develop on Cadence, a coordinated set of practices that support Agile Teams by providing a reliable series of events and activities that occur on a regular, predictable schedule. Agile Team and Agile Release Train Cadences. Scrum Master.
Scrum vs. Kanban is one of the most trending comparisons in the world of agile methodology! However, while Scrum and Kanban both have differences, their principles are the same. Both Kanban and Scrum will help you to build high-quality products and provide better services with less hassle. Scrum vs. Kanban: The Definitions.
The Professional Scrum Trainer (PST) community helps bring our mission to life by delivering classes around Scrum and working with customers directly. Your Professional Scrum Trainer (PST) supports the classroom sessions as an expert in the subject matter and by facilitating exercises, simulations, and constructive discussions.
It is this predictable cadence of show-and-tell sessions that creates the dolphins-versus-submarines comparison. XP has the practice “informative workspace,” Scrum encourages “transparency,” and Kanban development talks about making “process policies visible.” Frequent demos mean the project never disappears for long.
Continuing our theme of facilitating Scrum and Kanban, we’re honored to publish another guest blog post by Dave White on ‘Kanban and Scrum Together – Not So Fast’. Here Dave white has shared his thoughts on the article ‘Kanban and Scrum Together’ written by Steve Porter. KANBAN AND SCRUM TOGETHER – NOT SO FAST.
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