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.

ESP Compared to Kanban Method

Digite

David Anderson is a thought leader and pioneer in the field of Lean/ Kanban for Software Development and managing effective software teams. We also anticipate the adoption of the Kanban Cadences to be different.

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.

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. Lean/ Kanban Uncategorized agile Kanban Lean Lean Software Development Project Management Scrum Visual Project Management

SCRUM 65

Essential SAFe 4.0 – How is it Different from SAFe 4.0?

Digite

Lean-Agile Mindset. The biggest challenge that a large organization faces is an absence of a Lean-Agile mindset. is to train the top management and change leaders in Lean-Agile and SAFe principles. Release Train and Cadence. agile Essential SAFe Lean SAFe Essential SAFe 4.0

The Difference Between The Kanban Method and Scrum

Digite

Dave is a Principal Consultant at Depth Consulting Ltd, and Program Director of the KCP Program at the Lean Kanban University. 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. The Kanban Method pulls a great deal of its values from a Lean value system. There isn’t really a “Lean Manifesto” but the works of Taiichi Ono and W.

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. Lean/ Kanban agile Kanban Lean Lean Software Development Management Release Management Scrum

Using Kanban in Marketing

Digite

I was learning several new concepts including Lean, Agile, Application Lifecycle Management (ALM), Project Program Management, etc. I was already aware of Lean principles and their techniques because I got Lean certified in my previous company. Our Cadences.

To See or Not to See?

Digite

As you may all be familiar by now, the few Kanban principles that are most commonly applied to software are Visualization, Map the Value Stream, Limiting WIP, Removing Impediments to flow and Regular Cadence & Measurements for continuous improvements. It is not enough to Visualize.

Kanban and Scrum Together – Not So Fast

Digite

–and– along with an absence of time-boxes or any other time-bound constraint (the Kanban cadences are not constraints). Regarding cadences not being constraints, I would posit that a Replenishment meeting with a cadence of 2 weeks is exactly the same kind of a time-bound constraint as a Sprint Planning meeting that happens every 2 weeks. Lean/ Kanban agile Kanban Lean Scrum WIP WIP limit

SCRUM 40

Kanban to manage Complex/ Quick Moving Situations

Digite

At the same time, we ensure we follow many of the recommended Kanban cadences, including the Daily Standup Meeting, the Weekly Replenishment Meeting (where fine-tuning of the story/ defect prioritization takes place) as well as Release Retrospective and a Quarterly Strategy Review Meeting.

The Tangible Value of The “Intangibles”

Digite

Lean thinking recommends that systems should not be packed to 100% team utilization. Most managements struggle to accept this core Lean principle. This approach can be easily extended to strive for uniform cadence across the value stream.

Beginner’s Guide to Kanban for Agile Marketing

Digite

They must happen at regular intervals, but their cadence doesn’t need to be tied to any other cycle of Kanban. Agile Marketing agile Kanban Lean

SCRUM 52

Agile at Scale – Outcome Driven (or Broken)

Tyner Blain

It is also a characteristic of lean manufacturing. If there were no changes to the plan, they would be faster than a waterfall organization – avoiding death marches and being generally more efficient is an outcome of a frequent delivery cadence.

Agile 459

Difference Between Agile Project Management and Scrum

Brad Egeland

Lean Software Development (LSD): It has seven principles: removal of waste, more learning, decide as late as possible, faster delivery, team empowerment, build integrity in, and see the whole. 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

Development process cadence – how frequently does the team deliver ? This is based on anecdata (thanks Prabhakar for the great word), but my impression is that small companies commonly do this – think Lean Start Up – and large companies rarely do this.

2014 191

Is SAFe Agile?

Digite

This is a key tenet of SAFe framework and referred to as ‘Develop in Cadence’ in the big picture. The heart of a successful SAFe operation is multiple successful Scrum teams developing and integrating into cadence.

Agile 52

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

Leading Agile

A Lean-style value stream analysis could reveal the cost of business as usual is much higher than expected. ” They asked me how they could streamline the workflow and move to a more “agile” delivery cadence. Sounds good.