Scrum.org

OCTOBER 2, 2018

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?

Cadence 127

Cadence Development Team Review Software Review Technical Review 127

The IIL Blog

SEPTEMBER 13, 2023

Definitions Assumptions are things we know we do not know. Open or closed are the most common. Date opened and closed are always used. Dates : Multiple dates may be documented in the log: Opened, Closed, Next Review. He also holds multiple Agile certifications from Disciplined Agile, Scrum Alliance, and Scaled Agile.

Risk Management 88

Risk Management Risk Cadence 2016 88

Agilemania

FEBRUARY 22, 2021

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.

SCRUM 52

SCRUM Lean Software Review Cadence 52

Leading Agile

JULY 3, 2023

10 years ago, it seemed that a little Scrum here and some coaching there would suffice. Different change cadences. The package is changing at one cadence and maybe you’re trying to innovate and change at another cadence, right? So you definitely can have that right. Type of tightly coupled integrations.

Software Review 119

Software Review Fractional CTO Technical Review Agile 119

Leading Agile

NOVEMBER 24, 2020

The Assumptions of Scrum. So, what does Scrum say about dependencies? And if you look at the way that Scrum is architected, you’ll notice that it assumes a lot, including that each team: Consists of six to eight people. The Reality of Scrum. At one point in time, Scrum came up with this idea of Scrum of Scrums.

Agile 125

Agile Technical Review SCRUM Cadence 125

Agilemania

DECEMBER 2, 2021

Apply cadence and synchronize with cross-domain planning. Finally, let’s cut the suspense and closely at the common reasons to use SAFe. Incorrect definition of Epics: In other Agile frameworks, Epics refer to the long-term projects that are currently in progress. SAFe comes just behind Scrum and is fast becoming popular.

Technical Review 98

Technical Review Agile Software Review Lean 98

MPUG

MARCH 8, 2021

An example of this type can be the Scrum framework. It’s usually based on a cadence. As shown in the above figure, there is no regular timeboxed iteration, but incremental delivery can happen in cadence. To address this issue of improperly refined backlogged items, one can use the Definition of Ready (DoR) skill.

Lean 64

Lean Software Review Technical Review Agile 64

Leading Agile

APRIL 20, 2023

But I think I think it’s important we all know what just kind of Scrum, Agile, the whole world knows that if we have to escalate every decision, it just takes forever. But basically agile small teams working together are close to the surface. Like why do we need to actually give teams empowerment? So that’s the topic.

Agile 62

Agile Underperforming Technical Team Cadence SCRUM 62

Leading Agile

MARCH 23, 2022

What do you do with planning cadences? But what they’re really doing was like scrum with technical practices and things like that, I ever more aligned, it felt like to me was Scrum. I mean, everybody’s like very familiar with Agile and Scrum and things like that but I wouldn’t call them agile coaches per se.

Agile 140

Agile Consulting Influencer Underperforming Technical Team 140

Leading Agile

AUGUST 13, 2018

Scrum calls the list the Product Backlog.) Fortunately, contemporary lightweight software delivery methods based on time-boxed iterations (like Scrum) or continuous flow (like Kanban) include mechanisms to handle unplanned work gracefully. They have a plan for completing the items on the list. There will be stress. Cognitive Bias.

Software Review 83

Software Review Technical Review Cadence SCRUM 83

Scrum.org

MARCH 11, 2024

This article covers the three Scrum accountabilities (formerly roles) and addresses interferences of stakeholders and IT/line management with this crucial Scrum event. Your single best investment to improve your professional standing ; order the Scrum Anti-Patterns Guide book now! ? Source : Scrum Guide 2020.

Technical Review 163

Technical Review Underperforming Technical Team Software Review SCRUM 163

Scrum.org

MARCH 28, 2022

Welcome to the Sprint anti-patterns article from my series on Scrum anti-patterns, covering the three Scrum roles—pardon me: accountabilities—and addressing the contributions of stakeholders and the IT/line management. Join Stefan in one of his upcoming Professional Scrum training classes ! Source : Scrum Guide 2020.

SCRUM 162

SCRUM Technical Review Software Review Consulting 162

Scrum.org

MAY 16, 2024

In Org Topologies™, “the Product gap” is the space between the team-level product definition and the customer-level perception or whole business-level of the Product. In our Scrum classes, we teach that Product Owners are value maximizers. We should focus on closing the product gap by elevating both the PM role and the teams. (We

Agile 166

Agile Software Review Cadence Engineering 166

Scrum.org

DECEMBER 7, 2020

TL;DR: The Scrum Product Owner in 58 Theses. The Product Owner theses also address the Product Owner’s part in Scrum events 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?

Technical Review 211

Technical Review SCRUM Estimate 2020 211

Leading Agile

MARCH 29, 2023

It’s just means that, by definition, they aren’t Agile.” The most common small team Agile methodologies are Scrum and XP, maybe Kanban, or a combination of the three. Scrum focuses more on management activities. Agile teams, by definition, operate independently, in close proximity to an actual customer or product owner.

Agile 130

Agile Underperforming Technical Team Cadence Governance 130

MPUG

DECEMBER 28, 2020

A new version of Scrum guide was released last month. It contains commitments for each of the Scrum artifacts. This definition of the ‘goal’ can create confusion for many who understand project-program-portfolio management and how goals aligns with the vision, mission, strategy, and objectives of an organization. Sprint Backlog.

Cadence 116

Cadence SCRUM 2020 Agile 116

Scrum.org

JANUARY 14, 2021

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.

Cadence 137

Cadence Technical Review Development Team Review Lean 137

Scrum.org

JULY 31, 2023

The other 4 people worked as a Scrum team focusing on New Business Lending products. The dedicated teams were able to deliver in a regular Sprint cadence, which was much faster than before (weeks instead of months). It definitely did. A huge amount of time was wasted waiting. Gradual change is more complex to manage.

Technical Review 153

Technical Review Software Review 2022 2021 153

Leading Agile

OCTOBER 3, 2023

When I first started thinking through this idea, I was actually really thinking about the idea of practices because back in 2010, a little bit earlier than that, Jim Kundiff, the Scrum Alliance, and those guys were really popularizing the CSM certification, PMI was doing the PMI ACP or a lot of us were part of that. So think about scrum.

Governance 62

Governance Government SCRUM Agile 62

MPUG

MAY 18, 2022

I’ll also invite you to stay on after the event and the recording closes. A lot of people don’t like that, but whatever your scrum team decides to do is right for your team. Another way that you may want to use Excel with your work, the reports that Microsoft uses are not what scrum teams and Agile teams are used to seeing.

Agile 59

Agile Underperforming Technical Team Software Review Cadence 59

Leading Agile

FEBRUARY 11, 2019

Zombie Scrum describes the impact on delivery teams. To prevent the Zombie Scrum or Delivery Trap phenomenon, our operational model keeps planning, execution, and tracking coordinated horizontally across dependent Delivery Teams and vertically through the Portfolio, Program, and Delivery levels. See this and this for more information.

Agile 99

Agile Underperforming Technical Team Software Review Technical Review 99

MPUG

OCTOBER 16, 2019

You’re going to see this coming out at a very fast cadence. That is a best practice is to be as close to the customer or the person who is actually viewing and defining what is the stakeholder that I want or what I’m representing. We want to keep them as close to the team that’s building. Did you want to close?

Agile 40

Agile Technical Review Software Review Engineering 40

PM That Works

MAY 9, 2020

And when I first got involved in the Agile space, there were a couple you know, you had your product owner and your Scrum Master certification, you know, there was a handful. It's really the revenue stream is certification, which is why you pick just about any of the frameworks, or any of the organizations providing certification.

Agile 40

Agile Consulting Certification Executing 40

Herding Cats

APRIL 16, 2019

Open Loop / Closed Loop Project Controls - project management is a closed loop control system. A steering target is established, actions are taken, variances are assessed, corrective actions are taken to close the loop. RFETS was a nuclear bomb manufacturing plant, built in 1951, operating until 1989, and closed in 2005.

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Workamajig

JANUARY 11, 2021

Administrative Closure: A list of the requirements necessary to formally close the project. Projects might additional calendars as well to show resource availability, communication cadence, etc. Final Account: The account that's responsible for finally closing a contract. Sometimes, this technique is also called 'Scrum Poker'.

Underperforming Technical Team 78

Underperforming Technical Team Project Life Cycle Estimate Risk Management 78

Agilemania

MAY 17, 2021

The organizations start with few teams initially, and it is easier to follow simple & lightweight frameworks like Scrum or Kanban at this stage. The most important skills for an agile coach include: Strong understanding of Scrum and Kanban. Experience as a Scrum master or with the agile methodology. Scrum@Scale.

Agile 98

Agile Lean SCRUM Development Team Review 98

Agilemania

MAY 17, 2021

The organizations start with few teams initially, and it is easier to follow simple & lightweight frameworks like Scrum or Kanban at this stage. The most important skills for an agile coach include: Strong understanding of Scrum and Kanban. Experience as a Scrum master or with the agile methodology. Scrum@Scale.

Agile 84

Agile Lean SCRUM Development Team Review 84