MPUG

MARCH 8, 2021

Many project managers utilize a Lean-Agile approach when there is high change or churn in project requirements, significant lack of clarity in scope, high complexity to their projects, and/or a larger number of risks associated with such. Earlier, in one of my articles, I had mentioned that Agile is both iterative and incremental in nature.

Lean 64

Lean Software Review Technical Review Agile 64

Velociteach

FEBRUARY 1, 2023

This article presents a framework for modeling project context and considerations for tailoring. Acceptable variances, reporting cadence, and status meetings are addressed in the plan. Team size is known, and the project duration can be time-boxed which simplifies estimating the project’s time and cost and monitoring its performance.

Planning 52

Planning Technical Review Governance Government 52

Leading Answers

MARCH 7, 2019

I wrote this article about the choices of approach we have and ways for new PMs to navigate them.). Yet when projects use new (to us) technology and tackle problems our organizations have not solved before, then risk, uncertainty, and rates of change will be high. (Over at ProjectManagement.com January’s theme was “New PMs”.

Software Review 101

Software Review Technical Review Risk Management Software Developers 101

MPUG

FEBRUARY 19, 2024

Euterpe encourages us to embrace experimentation and risk-taking in pursuit of innovation. Collaboration between project sponsors and stakeholders to develop the scope and best strategy is required for success, including estimations of time and costs. Did this article give you something intriguing and inspiring to think about?

Underperforming Technical Team 52

Underperforming Technical Team Innovation PMI Cadence 52

Herding Cats

JULY 29, 2017

Related articles. IT Risk Management. Why Guessing is not Estimating and Estimating is not Guessing. Estimating Processes in Support of Economic Analysis. Herding Cats: Capabilities Release or Cadence Release. Estimating and Making Decisions in Presence of Uncertainty.

Cadence 28

Cadence Software Engineering Estimate Manufacturing 28

Scrum.org

JANUARY 30, 2023

This article is another excursion into this nascent yet fascinating new technology of generative AI and LLMs and the future of knowledge work. Shall I notify you about articles like this one? A rough estimation of the budget required. TL; DR: Agile Transformation with ChatGPT or McBoston?

ChatGPT 187

ChatGPT Agile Artificial Inteligence Consulting 187

Scrum.org

FEBRUARY 22, 2021

Shall I notify you about articles like this one? Apparently, there is a difference in the inspect & adapt cadence when product strategy and Sprint Backlog are compared to each other. The product roadmap needs to be adapted to the learnings from running product experiments regularly in an appropriate cadence to meet that standard.

Software Review 143

Software Review Technical Review Cadence SCRUM 143

Herding Cats

JULY 27, 2017

So when you hear Continuous Integration (CI) and Continuous Delivery (CD) as buzzwords , ask can you show me your Product Roadmap and Release Plan (either Capabilities release plan or Cadence release plan). Related articles. IT Risk Management. Why Guessing is not Estimating and Estimating is not Guessing.

Cadence 31

Cadence Infrastructure Governance Government 31

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. And teams have a cadence where they’re operating with intent but within constraints. ” Like, what the heck does that even mean? What would you go do?

Agile 62

Agile Underperforming Technical Team Cadence SCRUM 62

Wrike

JUNE 15, 2023

Getting granular with work projects is important as you’re often faced with pressure from several sources: Time limits Budget constraints Client expectations Stakeholder opinion Without a measured or considered approach to how you’ll tackle both major and minor projects, the risk of falling prey to pressure from any of these sources increases.

Energy 36

Energy Budget Cadence Lean 36

Herding Cats

MARCH 23, 2016

The Plan for the delivery of value is shown in the Product Roadmap and implemented in the Cadence Release Plan, or sometimes in the Capabilities Release plan. Related articles. IT Risk Management. Why Guessing is not Estimating and Estimating is not Guessing. Deliver as planned. Fast is a term replaced by Planned.

Planning 39

Planning Cadence Logistics Manufacturing 39

Scrum.org

DECEMBER 7, 2020

Do you want to get this article in your inbox? The main accountability of the Product Owner is driving value for customers and the organization while mitigating risk at the same time. Roadmap planning is—like Product Backlog refinement—a continuous effort, just at an extended cadence. The Product Owner Theses.

Technical Review 210

Technical Review SCRUM Estimate 2020 210

Digite

FEBRUARY 13, 2018

Continuing our theme of helping Agile teams understand the Kanban Method, so they can effectively adopt it for their improvement efforts, I am again honored to publish a guest article by another great friend of ours – Dave White. You will enjoy this excellent article. Many Kanban teams have a Queue replenishment cadences.

Cadence 94

Cadence SCRUM Lean Underperforming Technical Team 94

Scrum.org

APRIL 25, 2022

Shall I notify you about articles like this one? Too much estimating: The Developers even estimate sub-tasks. Remember: the purpose of estimating is to identify misalignment among the Developers regarding the What and How of items from the Product or Sprint Backlog. So don’t waste your time on that.

SCRUM 197

SCRUM Planning Underperforming Technical Team 2020 197

Herding Cats

AUGUST 5, 2017

Managing Cost, Schedule, & Technical Performance Risk Is The Basis Of Good Project Management. Risk management is essential to the success of any significant project. The emerging risks that can be identified early in the project that impact the project later are often termed “known unknowns.” Hope is Not a Strategy.

Risk Management 42

Risk Management Risk Estimate Underperforming Technical Team 42

Scrum.org

JANUARY 27, 2020

Do you want to get this article in your inbox? Too much estimating: The Development Team estimates sub-tasks. Irregular Sprint lengths: The Scrum Team has variable Sprint cadences. Otherwise, transparency will suffer and flawed decisions might be made, reducing value creation and increasing risk.).

Planning 218

Planning Underperforming Technical Team SCRUM Cadence 218

Leading Agile

AUGUST 19, 2020

We’re starting to see HBR articles written more than one. We typically want to have those stories estimated, right? Maybe we’re great at doing user stories and estimation and kind of release planning level stuff. And then I reduce the risk. And the guys that sign that thing, they changed the world.

Agile 87

Agile SCRUM Governance Government 87

Leading Agile

JUNE 29, 2023

Now, let’s talk about why estimating in hours is absolutely critical for what they’re responsible for and what cannot be done without it. Here are some books you need to read, try this article, attend this conference, or go to this two-day course. We had driven down risk early. Let’s consider predictability.

Agile 75

Agile Technical Review Executing Influencer 75

Herding Cats

APRIL 5, 2016

This is the basis of the Agile Product Roadmap and Product Release Plan (either cadence or capability based). If it's knowable, doesn't means it's known, but standard Risk Management has the means to deal with knowns and know unknowns - both reducible and irreducible. Related articles. IT Risk Management. Of course not.

Software Developers 28

Software Developers Software Development Software Review Software 28

MPUG

FEBRUARY 11, 2021

And having that standardized across all of our projects and programs in an organization again is key so that we compare apples with apples rather than comparing apples with pears is often we do when we have a subjective view perhaps of what a risk might be or whether something’s red and blue of green. We have the Power BI Gateway.

Software Review 52

Software Review 2020 Risk Management Governance 52

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. Ron Jeffries’ classic article, “We Tried Baseball and it Didn’t Work” , is an amusing and yet chillingly accurate description of this situation.

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. 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. Wait a minute.

Agile 40

Agile Technical Review Software Review Engineering 40

MPUG

JUNE 1, 2022

In addition to that, as well as the PMI standards plus to lead the way for the immediate processes, the techniques when it comes to things like estimating or requirements management and things along those lines. You have your integration, scope, schedule, cost, quality, resources, communications, risk, procurement, stakeholders, right?

PMI 59

PMI Software Review Estimate Risk Management 59

Leading Agile

AUGUST 20, 2018

But there’s a risk that people will get excited about automation and get ahead of themselves. They asked a software developer what it would take, and he estimated something like 20,000 pounds over several months. Including appropriate tooling in the automated CI process covers most of the remaining risks in this area.

Software Review 60

Software Review Software Technical Review Development Team Review 60