Capabilities Release or Cadence Release

Herding Cats

So do we pick a Capabilities Release or a Cadence Release? Cadence release puts value out on a periodic basis. Those capabilities don't always show up in the Cadence, but that's a separate issue as well. . IT Risk Management.

7 Factors for running an effective Kanban Replenishment Meeting


In 2015, in a blog post called Kanban Cadences , David Anderson laid out a set of 7 Kanban cadences or meetings that provide comprehensive opportunities for feedback, planning, and review in an enterprise.

Risk Management in Five Easy Pieces, with Apologies to Jack

Herding Cats

Managing Cost, Schedule, & Technical Performance Risk Is The Basis Of Good Project Management. Risk management is essential to the success of any significant project. These risks can be mitigated with a good risk management process. Risk management structure.

Risk 48

ESP Compared to Kanban Method


He highlights this with the adoption path for Kanban cadences (meetings) as to how Kanban is bottom-up and inside-out approach whereas ESP is the top-down and outside-in approach. We also anticipate the adoption of the Kanban Cadences to be different.

GAO Cost Estimating and Assessment Guide Applied to Agile

Herding Cats

Either a Cadence Release Plan or a Capabilities Release Plan. Uncertainty creates risk. Risk Management is how Adults Manage Projects - Tim Lister. Conduct Schedule Risk Analysis. Uncertanty creates Risk. The GAO Cost Estimating and Assessment Guide has 12 steps.

How effective is your benefits management framework?

Kiron Bondale

Benefits management, like project risk management, is practiced poorly by most organizations. This analysis should focus on assumptions and risks impacting benefits realization.

2017 181

Have we learned anything?

Kiron Bondale

Frequent identification – either on a fixed cadence such as in a sprint ending retrospective or just-in-time based on a team’s recognition that there is something of value to be captured and shared.

2018 190

The Difference Between The Kanban Method and Scrum


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. Incremental delivery of software also mitigates risk and maximizes the opportunity to learn from a business, process, and technical perspective. Cadences. Scrum prescribes a cadence and that all activities happen within that timebox. This also includes cadences. Introduction.

Agile Through a Matrix Lens

Tyner Blain

Development process cadence – how frequently does the team deliver ? “Agile” is something most teams do wrong*, without realizing they’re doing it wrong. A good 2×2 matrix acts as a lens, helping to convert information into insight.

2014 191

Agile Release Train (ART)


Program Increments (PIs) provide a development timebox (default 10 weeks) that uses cadence and synchronization to facilitate planning, limiting WIP, provide for aggregation of value and assure consistent retrospectives.

Agile 72

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). IT Risk Management.

Unravelling PI Planning


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. System Arch/ Engineering – to help establish inter-team dependencies and risks.

The Tangible Value of The “Intangibles”


CoS is a risk categorization mechanism for any work item. This approach can be easily extended to strive for uniform cadence across the value stream. One of the important aspects of The Kanban Method is Class of Service (CoS).

2016 52

Beginner’s Guide to Kanban for Agile Marketing


Your situation is unique and you deserve to develop a unique process definition tailored and optimized to your domain, your value stream, the risks that you manage, the skills of your team, and the demands of your customers.


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

Leading Agile

But there’s a risk that people will get excited about automation and get ahead of themselves. Including appropriate tooling in the automated CI process covers most of the remaining risks in this area. It seemed a high-risk situation to me. Sounds good.

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. IT Risk Management. A popular mantra in Agile is deliver fast, deliver often. In some domains this may be applicable.

Common Ground for a Conversation about Estimating

Herding Cats

Can these two Features 2015007 and 2015008 going to make into the next Cadence release, scheduled for the end of November?". This is the Value at Risk conversation. What are you willing to risk of you make that decision without the needed accuracy and precision to "protect" your decision for a loss ? Neil Killick posted a good question, what's the common ground for talking about estimates.

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). 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. IT Risk Management. Risk Management is How Adults Manage Projects. Risk Management is How Adults Manage Projects. Qualitative Risk Management and Quantitative Risk Management.

2016 36

Kanban = Continuous Delivery? Not Necessarily


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.

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


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. We do product releases every 4-6 weeks, and these get deloyed to our SaaS servers – that cadence is well established.

Use This Free Project Status Report Template for Fast and Easy Project Reporting

Project Bliss

You can break out the different areas for individual status indicators, so any that need attention due to risk are highlighted and easy to see. You can also incorporate any risks that have occurred and how the team is addressing them. Photo by Green Chameleon on Unsplash.