Books Cadence Development Team Review Strategy 
Digite
JUNE 13, 2018
Anderson best articulated its application to software development, in 2013, in the foundational book Kanban: Successful Evolutionary Change for Your Technology Business, and its adoption hasn’t been as universal as Scrum’s during the early days of Agile software development. Creating Your First Kanban Board.
Digite
AUGUST 21, 2017
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.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Digite
MARCH 12, 2018
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. The Dev board value stream follows a Test Driven Development flow. Our Kanban Journey.
MPUG
DECEMBER 28, 2020
My perspective is based on my analysis, my own interpretations, and the interactions I’ve had with Agile practitioners who follow my publications, books, and/or courses. As the saying goes, “Culture eats strategy for breakfast.”. In my view, it’s actually the values and value-system which eat strategy for breakfast.
Scrum.org
NOVEMBER 18, 2020
Think of Product Goals as a stepping stone in the river of complexity One of the more challenging aspects of Product Management is to create a tangible relationship between the work we do today and the business strategy. Well, they are not new, lets take a trip down memory lane to the year 2009 and the book “The Toyota Kata” by Mike Rother.
Scrum.org
JANUARY 10, 2021
Once you accept this, and quality becomes non-negotiable, your Dev e lopers can focus on creating usable increments of working software. Without a regular cadence of delivery of working software any belief that you will get a usable increment is misguided at best. Professional Developers create working software.
Planio
NOVEMBER 11, 2020
The official Scrum Guide describes a sprint retrospective as: A meeting held at the end of a sprint where the Scrum Team can inspect itself and create a plan for future improvements to systems, processes, and workflows. In other words, a sprint review is about the product while the retrospective is about the process.
Expert insights. Personalized for you.
110 
Let's personalize your content