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. or a simple Priority or Rank, usually defined jointly by the stakeholders, etc.

The Potential of Agile

Tyner Blain

Quality should be defined from the outside in, just like your product. When you define quality as “how many bugs there are” you are thinking too small. Where the agile process enables higher quality – better fitness function – is through the iterative cadence.

Agile 312

A Comprehensive Guide to Agile Project Management


The two most popular methods of agile, Kanban and Scrum, rely on boards that look like this: The different stages can be defined in the following ways: Backlog: The complete list of tasks, created and prioritized by the product owner.

Agile 137

How do your pods divide and conquer?

Kiron Bondale

Component-centric pods divide work based on a defined solution design or architecture. A good practice with agile delivery is to keep team sizes small to reduce the number of communication channels.

2016 170

How effective is your benefits management framework?

Kiron Bondale

The specific frequency of these re-forecasts is context-specific, but a minimum cadence should be established at the portfolio level to support normal portfolio monitoring and reporting practices. Benefits management, like project risk management, is practiced poorly by most organizations.

2017 181

Live from Product404, in Atlanta: Agile RoadMapping

Leading Agile

Scott “went Agile” in 2001 and has since carved a niche helping companies with long-term planning horizons to connect their strategy to iterative and incremental development cadences. ? ?. This talk covers techniques and approaches to developing and communicating roadmaps to your organization.

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. A predictive rhythm defines when the release will be released. The variability of the development work is minimized through the planned cadence.

How should I handle an agile-waterfall hybrid project?

Kiron Bondale

Things to consider when faced with such a hybrid project are: Orchestrating delivery cadence from each work stream to ensure that consuming work streams are not incurring prolonged delays in receiving components from providing ones.

Agile 156

Difference Between Agile Project Management and Scrum

Brad Egeland

We recommend using Agile if: The final version of the product is not defined. Unknown end-goal: If your project’s end goal is not defined then Agile will work for you. Teams can ship software on a regular cadence by fixed-length iterations called sprints that last for one to two weeks.


Agile Through a Matrix Lens

Tyner Blain

Our first step is to define our two axes. Requirements and expectations are immutable – this is the typical expectation within a large bureaucracy; someone built a business case, got funding, and allocated a team to deliver the product as-defined.

2014 191

Why Write Requirements

Tyner Blain

The intersection of value with feasibility, timing, and cost is what defines what your team can accomplish. There is a lot of advice out there for how to write requirements. There is not as much discussion about why to write requirements.

2013 228

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. Clearly defined, objective milestones are established.

Agile 72

Shift from Annual to Continuous Planning to Enable Agility [Webinar]


Define your demand management process. Having a regular cadence that allows you to measure value against new demand is incredibly valuable, as it isn’t disruptive when measured against the annual plan and allows you to forecast on a regular basis.

GAO Cost Estimating and Assessment Guide Applied to Agile

Herding Cats

The order of the needed Capabilties in defined in the business strategy. . Either a Cadence Release Plan or a Capabilities Release Plan. The GAO Cost Estimating and Assessment Guide has 12 steps. These describe the increasing maturity of the project's artifacts.

Handling Unplanned Work

Leading Agile

Lightweight methods are designed to support an approach whereby we define a goal — a capability our customers or our organization needs in order to meet business (or other) objectives — and a direction for product design that seems likely to achieve that goal.

2018 72

Scrum or Kanban for Application Support teams?


Frequently, especially in a Scrum environment, it can be difficult to match the cadence of doing both. Are there explicit policies defined on how they shall select the work they do on a day-to-day basis?


Beginner’s Guide to Kanban for Agile Marketing


WIP limits may be Kanban’s core defining feature, but it’s not all you need. Anderson defines five core properties that make for a successful implementation: Visualize Workflow.

Agile 72

What Are OKRs? How to Use OKRs for Planning (and Achieving) Your Goals


You might want to set a cadence that includes: OKR planning sessions: Bring together a small group of people that work together to plan and talk through objectives and key results for the next cycle. How did Google grow from 40 to 88,000 employees and $100+ billion in global revenue?

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. Showing up fast is defined by showing up when needed. The need is defined in the Capabilities Based Planning process. .

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

Leading Agile

” For instance, they would fully define the database schema before starting any other work. This could be the only Story the team tackles in their first development cadence or iteration or Sprint or what-have-you. Welcome back!

2018 62

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

Leading Agile

Are stakeholders involved in defining the examples? It isn’t reasonable for (say) ten development teams to share (say) two statically-defined test environments whose configurations differ wildly from production. Sounds good. What are “all the things,” by the way?

Using Kanban in Marketing


Our Cadences. Each card in the Events lane has a pre-defined To-do list. The pre-defined To-do list provides clarity of the overall work that needs to be done, work completed and the remaining tasks to be done to complete each Event.

Risk Management in Five Easy Pieces, with Apologies to Jack

Herding Cats

This Plan needs to define: How the products and services will be “matured” as the project progresses? It serves no purpose to have a risk plan and the defined mitigations in the absence of a risk communication plan. Herding Cats: Capabilities Release or Cadence Release.

Risk 48

Same Same but Different †

Herding Cats

Regular delivery of incremental business value - defined in a Product Roadmap, scheduled in a Cadence or Capability release plan. Much of the conversation in social media around agile techniques seems to be based on the differences between the variety of choices of a method, a process, or a practice and definitions of terms for those choices. There seems little in the way of shared principles, when in fact, there is a great deal of sharing of principles.

Kanban = Continuous Delivery? Not Necessarily


If it is a production support environment, there may be some SLA (service level agreement) goals to be met (response time, resolution time, etc.) – which would again need some pre-defined frequency of releases in order to meet those SLAs.

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?". It's been suggested Estimates are the smell of dysfunction , but not root cause is defined, nor any Corrective Actions. Neil Killick posted a good question, what's the common ground for talking about estimates. In this post I'd suggest predictability is very difficult to achieve in the presence of uncertainty.

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


If it is a production support environment, there may be some SLA (service level agreement) goals to be met (response time, resolution time, etc.) – which would again need some pre-defined frequency of releases in order to meet those SLAs. If your unpredictable release schedule is a (perceived) problem, it can be easily fixed by defining an explicit policy to do releases every 1, 2 or 4 or 6 weeks, whatever is acceptable in the business context.

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). People have defined skills and capabilities. There 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. You Can’t Understand Agile Without Understanding Hayek. Let's look at Hayek's paper. " The Use of Knowledge in Society ," F. Hayek , The American Economic Review , Vol.

2016 36