Leading Agile

APRIL 20, 2023

As the world of business increases in complexity, it will take more than user stories, estimation, and OKRs to build a trustworthy system that management can delegate into. Do we solve it by putting in specific practices in place like scrum of scrums or dependency boards or like that’s a set of practices.

Agile 62

Agile Underperforming Technical Team Cadence SCRUM 62

Scrum.org

APRIL 25, 2022

TL; DR: Scrum Master Anti-Patterns. Join Stefan in one of his upcoming Professional Scrum training classes ! Scrum’s Sprint Planning aims to align the Developers and the Product Owner on what to build next, delivering the highest possible value to customers. Shall I notify you about articles like this one?

SCRUM 201

SCRUM Planning Underperforming Technical Team 2020 201

Digite

MARCH 17, 2017

As the PI has 5 iterations with multiple teams working in cadence to achieve a common vision, it is important for these teams to assemble and plan out the course of action for the entire PI duration. The meeting also helps the teams understand any dependencies amongst themselves and any risks to be addressed.

Planning 60

Planning Engineering Cadence Risk Management 60

Digite

FEBRUARY 13, 2018

In this article, he outlines the similarities of the two as WIP Limiting, Pull-based systems – with cadences and a focus on learning – while also explaining their differences. A question that I often get while speaking with people is: What is the difference between Kanban and Scrum? You will enjoy this excellent article.

Cadence 94

Cadence SCRUM Lean Underperforming Technical Team 94

Leading Agile

AUGUST 19, 2020

They did a great job of getting the message out Scrum and the Scrum certification did a great job of getting the message out. Does it mean that we start Doing Scrum, right? Those are the things that get in the way of making Scrum not work in a lot of organizations. We typically want to have those stories estimated, right?

Agile 100

Agile SCRUM Governance Government 100

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 217

Technical Review SCRUM Cadence Estimate 217

Digite

MARCH 2, 2018

It is then up to them – or some business function like sales or support – to have the conversation with your customers that they need to accept new releases at a certain frequency or they may be at a risk of not getting the support they might need on an old version of the product. At the other end as well, there can be two issues.

Underperforming Technical Team 71

Underperforming Technical Team Software Review Cadence Software 71

Digite

MARCH 2, 2018

It is then up to them – or some business function like sales or support – to have the conversation with your customers that they need to accept new releases at a certain frequency or they may be at a risk of not getting the support they might need on an old version of the product. At the other end as well, there can be two issues.

Software Review 66

Software Review Underperforming Technical Team Cadence Software 66

Scrum.org

JANUARY 27, 2020

The Product Owner introduces the business objective the upcoming Sprint is supposed to meet, the Scrum Team collaboratively creates a Sprint Goal, and the Development Team forecasts the work required to achieve the goal by picking the appropriate items from the Product Backlog, transferring them to the Sprint Backlog.

Planning 222

Planning Underperforming Technical Team SCRUM Cadence 222

Leading Agile

JUNE 29, 2023

Old ways of working won’t solve it, and simply implementing practices like Scrum, DevOps, FinOps, or ProOps are not sufficient to create the organizations we need for the changes we must make. If they put themselves at risk for us and we fail to deliver, their personal interests are jeopardized. We had driven down risk early.

Agile 75

Agile Technical Review Executing Influencer 75

Workamajig

JANUARY 11, 2021

Accept: A response to a project risk where the project manager accepts the risk and takes no action to evade it, i.e. 'accepting' the risk. This is usually in case of risks that are unlikely to occur or minor enough so as to not affect the project's outcome. Actual dates are different from planned or estimated dates.

Underperforming Technical Team 78

Underperforming Technical Team Project Life Cycle Estimate Risk Management 78

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

Herding Cats

APRIL 16, 2019

Business, Technical, Systems, Risk, and Project Management Briefings and Presentations. Risk Management (#RM). Business, Technical, Systems, Risk, and Project Management. But in fact, risk management is part of the other 4 principles as well. Table of Contents (Click the Name to go to Section). Management Processes (#MP).

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Leading Agile

FEBRUARY 11, 2019

High WIP levels and failure to recognize delivery capacity, identify scarce resources, and consider estimates led to intense pressure to deliver late in the project schedule. Zombie Scrum describes the impact on delivery teams. One of the roles or functions of the Product Manager is that of Product Owner, in the Scrum sense.

Agile 115

Agile Underperforming Technical Team Software Review Technical Review 115

MPUG

OCTOBER 16, 2019

You’re going to see this coming out at a very fast cadence. A lot of times I like to have fun, certainly in doing estimating. But there are people who are building tools, but they remember the competency of what’s being organized, structured and delivered is on a very different cadence. Add a bucket.

Agile 40

Agile Technical Review Software Review Engineering 40