Remove Blog Remove Cadence Remove Development Team Review Remove Process
article thumbnail

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. I believe this may be of interest to other teams as well, hence this blog post.

article thumbnail

11 Proven Stakeholder Communication Tactics

Scrum.org

There are plenty of opportunities for stakeholders to interact responsibly with a Scrum Team. The two formal Scrum events that come to mind are: Sprint Reviews. The Sprint Review is Empiricism at work: inspect the Product Increment and adapt the Product Backlog. Sprint Reviews are a zone free from death by PowerPoint.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

A Review Of Scrum For Kanban Teams

Digite

Inspired by Steve Porter’s efforts to bring process practitioners closer together and educate Scrum practitioners, I’m writing a shadow series of posts that will follow the Kanban and Scrum – Stronger Together series and continue my own efforts to clear up misconceptions between practitioners of these methods. Disclaimer.

article thumbnail

Improving SAFe Through Professional Scrum

Scrum.org

To use the leadership styles model we discuss in the Leading SAFe class - the starting point is more of an orchestrating and technical expert kind of leadership stance and the goal should be to evolve towards a more serving the team and the process style over time. See a recent blog post I wrote about this).

SCRUM 136
article thumbnail

How I transformed “multiple Scrum teams” into “multiple team Scrum”

Scrum.org

In this blog I want to share some common collaboration problems and solutions I experimented with. I advise to start finding one person to be the single Product Owner for all teams. The other “fake PO’s” should be moved inside the development teams as subject matter experts so they can provide detailed requirements.

article thumbnail

Kanban to manage Complex/ Quick Moving Situations

Digite

Also, we have quite diverse roles in the team (i.e., In the usual Scrum process, the P.O. We started with a single Kanban board, but with 2 separate swim lanes for the product manager and the dev team – see below – Planning Lane for the Product Owner. Dev Lane for the main dev activity.

article thumbnail

Improving SAFe thru Professional Scrum

Scrum.org

To use the leadership styles model we discuss in the Leading SAFe class - the starting point is more of an orchestrating and technical expert kind of leadership stance and the goal should be to evolve towards a more serving the team and the process style over time. See a recent blog post I wrote about this).

SCRUM 113