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.
There is an important difference between the Scrum Master accountability, as described in the Scrum Guide 2020, and the Scrum Master role, as it is lived in different organisations. You can be a Scrum Master, while your job description and role in the organisation may slightly differ.
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.
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?
ScrumScrum is a lightweight framework that helps people, teams, and organisations generate value through adaptive solutions for complex problems. UX designers focus on understanding users' needs, preferences, and pain points to design solutions that meet those requirements and expectations.
At a recent Professional Scrum Master Advanced course, we were discussing how to promote engagement at the Daily Scrum when Mark Kuzik , lean champion and Director at Argus Machine in Canada suggested shaking things up by trying Management by Exception at the Daily Scrum. Are we on track to meet the Sprint Goal?
For example, take scrum. Scrum is a great framework for helping teams work more productively together. In fact, the name comes from rugby and like it, scrum is a team sport. Teams learn through experience, reflective meetings and specific roles that add structure and manage work. How Scrumban Combines Scrum and Kanban.
Users have also bought Trello for personal task management as it’s a simple way for individuals to manage tasks, set reminders and meet deadlines. Trello leans heavily on kanban boards, but Jira offers that and scrum and sprint boards. Some use it for client pipeline management, too. Who Uses Trello?
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 scrummeetings. It’s led by what is called a Scrum master.
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.
. Lean Coffee Poster The premise of Lean Coffee is relatively straight forwarded. Lean Coffee increases the engagement level significantly among the participants. In the early days of Lean Coffee, the choice of beverage was often coffee and the tool itself is also referent to Personal Kanban.
Adopt Strategic Alignment Tools: Choose appropriate tools based on your context: For startups or new initiatives: Lean Canvas and Now-Next-Later Roadmap. Lean experiments for testing hypotheses. Whole-Team Refinement: Involve the entire Scrum team in refinement activities, avoiding the Involving the Scrum teamwhy?
If you’ve ever wondered whether Scrum can work for hard deadlines, the answer is – yes! Not only can Scrum work in these situations, but in my experience, using this agile framework increases the probability of meeting challenging deadlines. Lean Thinking. Let me demonstrate these concepts with a story. Empiricism.
TL; DR: HoA #42: Lean Roadmapping and OKRs w/ Janna Bastow. In this energizing 42nd Hands-on Agile session on Lean Roadmapping, Janna Bastow, the go-to-authority on product roadmaps, talked about being lean while creating and maintaining your roadmap and how objectives and key results (OKR) may help meet that challenge. ??
The kanban methodology was first developed as a lean manufacturing system to help with production planning , scheduling and control. Make process policies explicit and share them with your team, preferably during meetings when you can address their questions, comments or concerns. Kanban vs. Scrum: What’s the Difference?
Lean Coffee is a powerful meeting faciliation technique that can be used in coffee shops, conferences, open space, scrum events or simply replace existing corporate meeting formats. Lean Coffee is easy to learn, empowers participants and increases engagement. It is also fun!
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. Doing" Scrum is straightforward: assign roles, schedule events, create and maintain artifacts. How Do You Keep Scrum Simple?
Agile, Scrum, and traditional project management methods each offer unique benefits depending on the nature of the project and the industry. Scrum Framework Scrum is a specific framework within the Agile methodology that provides a structured approach to managing complex projects.
“Ich bin ja ein großer Fan von Scrum, aber. viel zu viele Meetings!”. Ich komm vor lauter Meetings nicht zum Arbeiten!". Sätze, die ich häufiger von Vorgesetzten, von Entwicklern und auch von Scrum Mastern und Product Ownern höre. Daher diskutieren wir in meinen Professional Scrum Master Trainings immer wieder darüber.
The new Scrum Guide 2020 mentions Scrum is founded on empiricism and lean thinking. Lean thinking reduces waste and focuses on the essentials.”. While Scrum Events remove the need for any other meeting, at times unintended wastes get injected in those events. Defects: Are we sharing meaningful information?
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.
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. It is commonly employed in Agile and Lean projects, often in response to end-user feedback in product development cycles.
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. .
TL; DR: The Scrum Guide Reordered. The Scrum Guide Reordered 2020 is based on about 95 percent of the text of the Scrum Guide 2020, extending its original structure by adding additional categories, for example, on self-management, commitments, or accountability. The Origin of the Scrum Guide Reordered. Scaling Scrum.
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.
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.
The only purpose of doing Scrum is to create a DONE Increment. In Scrum Teams Definition of Done enables transparency around quality and releasability of the Increment. However, more often than not the Definition of Done stops at meeting acceptance criteria and completing a few levels of testing.
. 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. .
Scrum is a framework for an agile workflow. In scrum there are daily scrums , which are short meetings at the beginning of the work day. When working in scrum, there are things called user stories. Let’s outline two of the most popular agile frameworks so you can adopt and adapt to fit your team.
Why perfect is the enemy of good - using lean change to apply agile in context. Importantly, unlike many Agile coaches and training programmes, our teams of Agile Coaches, Scrum Masters, Product Owners and Skilled Engineers all come from a project delivery background. agile-scrum-training Don’t run before you can walk.
Earned Value Analysis Dashboards Road Maps Lean Concepts – Kanban Agile Concepts – Scrum Infographics. Mind Mapping Process Mapping Storyboarding Root Cause Analysis Charting, Diagramming and Graphing Drawing and Sketching Wireframes Use Cases and user stories. Category #2. Visual Project Reporting Tools. Category #3.
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. Otherwise, agree on the rules of the game at the beginning of the meeting. Tips & Tricks.
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?
” Mr. Harned founded the Digital PM Summit as a place for digital project management professionals across industries to meet once a year to discuss big ideas and developments relevant to the project management world. He writes consistently on his blog about software development and lean, Kanban and agile development principles.
Some organizations, such as the Project Management Institute (PMI), will ask you to meet some requirements to be allowed in the program, such as having a bachelor’s degree, months of project management experience or even another project management certification. Scrum is part of Agile, which has become a standard in IT projects.
The book “ The Lean-Agile Way – Unleash Business Results in the Digital Era with Value Stream Management ” by Cecil ‘Gary’ Rupp, Richard Knaster, Steve Pereira, and Al Shalloway provides a comprehensive roadmap to optimize processes, improve products, and enhance service delivery.
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. .
Daily Scrum events are a powerful way to align team efforts and foster collaboration. To have an effective Daily Scrum, the team should focus on: 1. Aligning Work with Goals: By inspecting and adapting the efforts and progress made towards the sprint goal, the Daily Scrum helps maintain alignment with the product goal and vision.
TL; DR: A Remote Daily Scrum with a Distributed Team. This eighth article now looks into supporting a distributed Development Team organizing a remote Daily Scrum. The Purpose of the Daily Scrum. The Daily Scrum is held every day of the Sprint. The Daily Scrum is an internal meeting for the Development Team.
Scrum Alliance reports 1.5 Predictive, agile, and lean/Kanban can be viewed as the corners of a triangle with a near-infinite array of options. Agile (Scrum). Lean/Kanban. Throughout the development lifecycle, there will be periodic status meetings and reviews. Agile (Scrum) Agile is a mindset, not a methodology.
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?
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. ?
This is why I appreciate A Scrum Book ( which I co-authored). Take the Daily Scrum, for example. If you dont have the problem that a Daily Scrum is meant to solve, then forcing it doesnt make sense. Lean Thinking: Focuses on continuous improvement rather than a fixed set of rules. Do you need it? That depends.
The goal of lean kanban is to start with no limits and monitor the WIP. The scientific approach of incremental change is the basis of lean and agile principles. This is an essential practice in lean manufacturing and serves kanban well by keeping teams working at capacity. New work can now be pulled by the 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