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
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 exploring Lean Thinking through a blog article might not be justifiable.
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.
I remember the first time I heard about Lean Startup. A member of the audience asked, “What do you think about Lean Startup?”. Honestly, I had not heard of Lean Startup. After the conference, I bought Eric Ries’s book - Lean Startup: How Today’s Entrepreneurs Use Continuous Innovation to Create Radically Successful Businesses.
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? What Is Kanban?
Rather than containing a set of work instructions, Scrum is a framework offering general principles. The simplicity of Scrum means that teams can adopt the complementary practices that work for their environment. For example, Scrum doesn’t tell teams that they need to use points. How to do that is up to the Scrum team.
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.
Mike Cohn Mike Cohn is a Certified Scrum Trainer and co-founder of the Scrum Alliance, where he served as Chairman of the Board. A pioneer in Scrum since 1995, Mike has supported Agile adoption at leading companies like Google, Microsoft, Intuit, and Yahoo. Founder of Scrum Inc.,
Plus, we’ll get into scrumban, a combination of kanban with scrum. Learn more History of Kanban Kanban was first introduced in Japan as a lean manufacturing approach pioneered by Taiichi Ohno in the late 1940s. These cards are the sprint backlog and are placed on a board for the scrum team to choose which user story to work on.
The new Scrum Guide 2020 mentions Scrum is founded on empiricism and lean thinking. Lean thinking reduces waste and focuses on the essentials.”. While ScrumEvents remove the need for any other meeting, at times unintended wastes get injected in those events. What is next?
Lean and Agile frameworks have gained significant traction, offering innovative approaches to streamline processes, improve efficiency, and foster collaboration. As we enter 2025, a variety of top-tier conferences dedicated to Lean and Agile practices are on the horizon. The event includes talks in both Japanese and English.
Throughout this blog, I use a variety of terms such as meeting, event, and workshop ostensibly as synonyms. Whilst this is a Professional Scrumleaning piece, facilitation is not an art solely associated with Scrum, and therefore the language I use isn’t either. Does this gardener sound like a Scrum Master to you?
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?
Lean Coffee is a powerful meeting faciliation technique that can be used in coffee shops, conferences, open space, scrumevents or simply replace existing corporate meeting formats. Lean Coffee is easy to learn, empowers participants and increases engagement. It is also fun!
B – Project Management Terms Backlog Backlog is a term from the Agile methodology Scrum, but is also used across industries to track every single thing that is needed to complete a product in development. Event chain diagram This is a visual way of demonstrating the relationship between events and tasks and how they impact one another.
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. .
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?
. Scrum is not a set of work instructions; it’s a framework. Scrum relies upon the collective intelligence of those using it to figure out how best to apply it in their situation. However, many take this to mean that they should figure out how to modify Scrum to suit their situation. . Don’t customize Scrum. .
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!”
TL; DR: Remote Agile, Part 1: Practices & Tools for Scrum Masters, Agile Coaches, and Product Owners. As a Professional Scrum Trainer, I strive to provide training classes without using PowerPoint or digital devices. Typically, there won’t be time to clarify questions around these issues during the event.
Earned Value Analysis Dashboards Road Maps Lean Concepts – Kanban Agile Concepts – Scrum Infographics. Category #2. Visual Project Reporting Tools. Category #3. Visual Project Collaboration Tools. table that shows which project is in which life cycle phase, colour coded to show status) Project Social Media (e.g.
They are derived from my fourteen years of practical experience with XP and Scrum, serving both as Product Owner and Scrum Master and interviewing dozens of Product Owner candidates on behalf of my clients. Scrum is not a methodology but a framework. The Product Owner is also the most vulnerable Scrum role.
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.
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. Though whatever the case, we can say for sure that Scrum is very popular in software development.
In a recent Scrum.org webcast (1) I mentioned that Scrum by its nature, assumes psychological safety exists in order for Scrum as a practice to function. Furthermore I would assert that for Scrum to be truly successful Scrum absolutely requires psychological safety to be established both inside and outside of the Scrum Team. .
TL; DR: Scrum Master Job — 4 Steps to Identify Suitable Employers or Clients. Are you considering a new Scrum Master job? Don’t worry; there are four steps of proactive research to identify suitable employers or clients for Scrum Masters and avoid disappointment later. The Scrum Master Job Market Is Promising.
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 2020 Scrum Guide includes five values that are important to every successful implementation of Scrum. These values don’t get much attention, but the longer I practice Scrum and coach teams, the more important I find them. Focus in the context of Scrum means to focus on the work of the Sprint. Sounds easy, right?
On today’s episode of YOUR DAILY SCRUM: How Do You Facilitate the Daily Scrum without the 3 Questions? Today's question is from Jodie who wants to know about alternatives to the 3 questions when facilitating the Daily Scrum. We are always happy to take questions about the ScrumEvents. Let us know in the comments!
These brief and targeted events are designed to keep the team focused on their goal, ensure transparency on the plans for the day, and quickly highlight any blockers, impediments or challenges. Daily Scrumevents are a powerful way to align team efforts and foster collaboration.
Large Scale Scrum is still Scrum, although there is one case study that is non-Scrum. My thoughts : I think there are possibilities for a Large Scale Scrum implementation to be without Scrum in careful hands. Like Scrum, Large Scale Scrum is based on transparency. How does it differ from Scrum?
As many scrum masters set out on their journey, they are often as new to their role as their manager. This post (inspired by Ben Horowitz author of “The hard things about hard things”) is for scrum masters, and people who work with scrum masters, and explores what good and bad looks like.
„Wie sehen Karrierestufen für Scrum Master aus?“ Diese Frage wird mir wiederholt von verschiedenen Personen gestellt: Sie wird mir von Scrum Mastern gestellt, die ein Rollenprofil oder Karrieremodell in ihren Unternehmen schaffen wollen. Diese Muster wurden auch von viel erfahreneren Scrum Mastern und Experten beobachtet.
XP, scrum, lean, etc.) On the personal advice front, I am very much looking forward to adding events to our knowledge sharing activities within the Major Projects Community. Second, the use of lean and agile tools and methodologies beyond IT, software and manufacturing. Learning the different methodologies in Agile (e.g.
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. Welcome to Lean Startup.
The SAFe method is based on the Lean philosophy and offers a fixed framework in which Scrum and other agile management methods can be scaled to the entire company. The basic concept SAFe divides enterprise agility into three level of abstractions: Team level (Scrum teams). Program level ("project" level). Agile Teams.
Before we talk about the comparison and contrast between Scrum Master and Agile Leader, people often compare and contrast Scrum Master and Agile Coach, and they often ask me, what’s the difference? The oversimplified answer is $200 per day because a scrum master should be working at an organizational level.
The Development Approach and Life Cycle Performance Domain is pivotal for project managers transitioning to Scrum Masters. This domain covers the methodologies and life cycle phases of project management, offering a perspective that's crucial when moving to the iterative and incremental world of Scrum.
TL; DR: Getting Hired as a Scrum Master or Agile Coach Are you considering a new Scrum Master or Agile Coach job? Don’t worry; there are four steps of proactive research to identify suitable employers or clients for getting hired as a Scrum Master and avoid disappointment later. I just received my author copies ! ?
TL; DR: Scrum Tools, Part 1. The Scrum framework is purposefully incomplete, […].” ( Source.) This half-sentence is probably one of the more often misinterpreted statements of the Scrum Guide. On the one side, it defines the necessity to enhance Scrum with other practices and tools.
Over the years I've seen numerous Scrum adaptions, and I thought perhaps it would be interesting, to sum up, some of the common misinterpretations of Scrum. As my journey in the realm of scrum continues, I have a hunch that this blog will never be finalized. . Scrum the abbreviation: It's Scrum, not SCRUM.
The SAFe method is based on the Lean philosophy and offers a fixed framework in which Scrum and other agile management methods can be scaled to the entire company. The basic concept SAFe divides enterprise agility into three level of abstractions: Team level (Scrum teams). Program level ("project" level). Agile Teams.
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. ?
Businesses pursuing an improved ability to deliver customer value using Scrum face numerous challenges. Scrum's focus is on producing a potentially releasable product increment after each Sprint (a Sprint is one time-boxed iteration of one month or less during which a potentially releasable product increment is created).
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.
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