Capabilities Release or Cadence Release

Herding Cats

Agile developers like to toss that phrase around as an alternative to having a plan for the delivered value we'll replace planning and estimating with early and often delivery. To suggest you can make such a decision without estimate requires you intentionally ignore this principle.

GAO Cost Estimating and Assessment Guide Applied to Agile

Herding Cats

The GAO Cost Estimating and Assessment Guide has 12 steps. Either a Cadence Release Plan or a Capabilities Release Plan. These describe the increasing maturity of the project's artifacts. There are not specific to Agile Software Development. But here's how they are connected. Step .

The Potential of Agile

Tyner Blain

The potential to provide better predictions – but only if you invest in estimation skills, and only if you culturally make a distinction between prediction and commitment. To do this, you have to be able to estimate with confidence.

Agile 299

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.

Don’t Say NoGet Them to Understand Your Team Delivery Capacity

Leading Agile

Let’s say that on average stakeholders request a couple of large items, a couple of medium-sized ones, and five small ones in any given cadence, iteration, release, or whatever unit of time your organization uses for such matters.

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. The Capabilities are laid out Cadence Releases in the chart below.

Quote of the Day

Herding Cats

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

Risk Management in Five Easy Pieces, with Apologies to Jack

Herding Cats

The answers to each of these questions require making estimates in the presence of uncertainty. No Point Estimate of Cost or Duration can be Correct. The use of point estimates for durations and costs is the first impulse in an organization low on the project management maturity scale.

Risk 48

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). Five Estimating Pathologies and Their Corrective Actions. Why Guessing is not Estimating and Estimating is not Guessing. NoEstimates Agile Economics Estimating GovernanceThere a popular notions in the agile development world that authors like Hayek and Taleb speak to how software development works. Let's look at one example.

2016 36

The Difference Between The Kanban Method and Scrum

Digite

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. Cadences. Scrum prescribes a cadence and that all activities happen within that timebox. If you didn’t guess, this cadence is called the sprint duration. In the Kanban Method, cadences are just as important as they are in Scrum. This also includes cadences. Introduction.

An Incremental Paradigm

Herding Cats

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). Why Guessing is not Estimating and Estimating is not Guessing.

Handling Unplanned Work

Leading Agile

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. What happens when the actual time to complete a piece of work differs from our estimate?

2018 68

Build a CI/CD Pipeline in the Cloud: Part Two

Leading Agile

This gives them confidence that the development team knows what they’re doing, so they won’t need to ask for revised estimates every day for the next umpteen months. Welcome back!

2018 62

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. Why Guessing is not Estimating and Estimating is not Guessing. A popular mantra in Agile is deliver fast, deliver often.

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

Leading Agile

They asked a software developer what it would take, and he estimated something like 20,000 pounds over several months. ” They asked me how they could streamline the workflow and move to a more “agile” delivery cadence. Sounds good.

Kanban = Continuous Delivery? Not Necessarily

Digite

We do product releases every 4-6 weeks, and these get deployed to our SaaS servers – that cadence is well established. On the one hand, the delivery team is not able to precisely estimate when it can deliver a release.

Unravelling PI Planning

Digite

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. Img Src: Youtube.com/VanceLowe.

Team using “Waiting for Release” column on their kanban board

Digite

We do product releases every 4-6 weeks, and these get deloyed to our SaaS servers – that cadence is well established. On the one hand, the delivery team is not able to precisely estimate when it can deliver a release. Here’s is another question that I recently answered on a discussion forum –. “My My team is using Kanban board but they seem to prefer to collate a couple of tickets then ‘do a release’ as appose to releasing each ticket.