Remove Article Remove Cadence Remove Estimate Remove Process

Common Ground for a Conversation about Estimating

Herding Cats

Neil Killick posted a good question, what's the common ground for talking about estimates. All estimates have two attributes - accuracy and precision. The values of these two attributes are what those needing the estimates are after. With the knowledge of the two values of these two attributes the decision makers can assess the "value" of the estimate. That request comes from those asking for the estimate. But that dysfunction is not "caused" by the estimate.

2016 40

New PM, New Choices

Leading Answers

I wrote this article about the choices of approach we have and ways for new PMs to navigate them.). Likewise, there are defined, repeatable IT projects that can (and have been) successfully managed using meticulous planning, detailed estimation, and formal change control procedures. Here, formal planning and estimation are difficult because we don’t know what we will encounter. Consider the process of designing a new car or home.

2019 87

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Quote of the Day

Herding Cats

Related articles. 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. NoEstimates Estimating Governance Management Performance-Based Project Management® Planning Quotes

Releases and Deadlines in Agile

Herding Cats

Cadence Release - when a fixed period ends, go with what is ready to go. Cadence Release paradigm, is a flow-based approach. The variability of the development work is minimized through the planned cadence. Focusing on meeting the needs of the customer or market is key to success in the Cadence approach. Success of the Cadence approach relies on: Schedule margin is needed to protect the deliverables. Related articles. Process is King.

The Difference Between The Kanban Method and Scrum


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. 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. You will enjoy this excellent article. Cadences.


Risk Management in Five Easy Pieces, with Apologies to Jack

Herding Cats

These risks can be mitigated with a good risk management process. For risks that are beyond the vision of the project team a properly implemented risk management process can also rapidly quantify the risks impact and provide sound plans for mitigating its effect. A good risk management process is proactive and fundamentally different than issue management or problem-solving, which is reactive. No Point Estimate of Cost or Duration can be Correct. Related articles.

Risk 37

Is Macroeconomics and Social Science the Same as Software Development?

Herding Cats

This is the basis of the Agile Product Roadmap and Product Release Plan (either cadence or capability based). But margin, management reserve, analysis of alternative is standard project management process of dealing with the indeterminate elements of projects. Related articles. Domain and Context Are King, Then Comes Process and Experience. Five Estimating Pathologies and Their Corrective Actions. Why Guessing is not Estimating and Estimating is not Guessing.

2016 36

An Incremental Paradigm

Herding Cats

We live in a golf course community , where our waste water is processed locally inside our area. The grass is green, the solid waste is hauled away for further processing, and we receive the benefit of lower costs. 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.

Handling Unplanned Work

Leading Agile

Process: Uncertainty about what to do when unexpected work arises. Band-aids: Working around the effects of the problem instead of improving the process. We did our short-term planning last week and we came up with an idea of what work we would be able to complete in the next iteration or cadence. Process. They aren’t clear about the process. What happens when the actual time to complete a piece of work differs from our estimate?

2018 82

Leveraging Agile to Get Predictable

Leading Agile

We’re starting to see HBR articles written more than one. And they’re counting on the fact that all of the planning processes, all the project management, or all the Agile or all whatever, is going to help them make promises, okay? Agile isn’t ever really about Agile.

2020 89

Questioning Agile Dogma

Leading Agile

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. The combination of high WIP (work in process), multiple and uncoordinated project assignments per individual, lack of coordination of scarce resources, and inattention to cross-team dependencies during planning led to unpredictability in software delivery.

Agile 93

Is Your Agile Project Healthy?

Project Management Essentials

If the answer is convincingly Scrum or Kanban, they are probably following a process. Watch out for contract terms and engagement practices, such as: Fixed-scope projects and burdensome change management processes; Arrangements where communications between the product owner and the team are filtered through an intermediary; Unnecessary or burdensome documentation and approvals; and. There is an unclear or vague process for making decisions.


Deliver Fast or Deliver as Planned (Update)

Herding Cats

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. The need is defined in the Capabilities Based Planning process. . The notion of agile is the basis of all military process, not just 5 coders in the room with their customer. Related articles. Why Guessing is not Estimating and Estimating is not Guessing.

2016 35

What’s Worse Than Not Automating Your Software Delivery Pipeline?

Leading Agile

The company wanted to automate their dispatching process. They asked a software developer what it would take, and he estimated something like 20,000 pounds over several months. Instead of automating their current process, they advised the company to set up a paper-based procedure that would be easy to change or discard, and work out any kinks that way. When they had their process worked out using notebooks and slips of paper, they were ready to automate. Sounds good.