7 Factors for running an effective Kanban Replenishment Meeting

Digite

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.

A Comprehensive Guide to Agile Project Management

Redbooth

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

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 299

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 179

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 169

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.

SCRUM 180

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)

Digite

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 73

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.

Scrum or Kanban for Application Support teams?

Digite

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?

SCRUM 66

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

Planio

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?

2018 72

Beginner’s Guide to Kanban for Agile Marketing

Digite

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.

SCRUM 52

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

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. .

Using Kanban in Marketing

Digite

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

Kanban = Continuous Delivery? Not Necessarily

Digite

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.

2018 52

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.

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

Digite

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.

2018 46

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.

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.