Continuous Improvement – The Kaizen Way
Summary The Lean Model of continuous incremental improvement has proven to be effective vs episodic, large-scale improvement projects. Lean focuses […]
Summary The Lean Model of continuous incremental improvement has proven to be effective vs episodic, large-scale improvement projects. Lean focuses […]
Retrospectives play a key role in continuous improvement. However they often fail to deliver due to lack of vision/strategy, dysfunctional team cultures, and no real follow-through on improvement actions.
Summary Retrospectives are a fundamental practice in all agile frameworks. Retrospectives enable Agile delivery teams to continuously improve their performance
Summary Well-designed surveys can provide data and other actionable insights in support of continuous improvement. Surveys can be used to
Summary Retrospectives and surveys both play a role in organizational learning, adaptation and improvement. Retrospectives are an integral part of
If an organization is not agile at a basic team level, it’s going to be really difficult to build an
An Agile maturity assessment evaluates an organization, team, or department’s adoption, practice, and proficiency in Agile methodologies. It helps identify
In a previous post, we talked about the benefits of team surveys as a method of driving improvement. In this
WIP limits are the key to establishing and optimizing the flow of work in a system. When WIP limits are
Our goal is to deliver maximum value at minimum cost. We seek to achieve this via a relentless focus on
The Monte Carlo Method can be used to analyze past data and then predict a range of future outcomes. This can be applied to situations where there is no single deterministic answer, like software development planning.
Are your retrospectives actually moving the needle, or are you just having fun? Summary Agile delivery teams aspire to continuously
Summary The basic measures of flow are: WIP: The number of items in progress – started but not finished Cycle
The Kanban Method can be applied as flow accelerator for software delivery frameworks. Adopting the Kanban Method for software development creates efficient and predictable flow of value.
SAFe Development Model: Define Requirements: Once a quarter a Product Manager creates a new set of requirements – aka the
“People don’t want to buy a quarter-inch drill. They want a quarter-inch hole!” – Harvard Business School Professor Theodore Levitt “If
Weighted Shortest Job First (WSJF) A method for objectively ranking and sequencing Product Backlog items Ensures items of highest value
“Change is not mandatory. Neither is survival”. W. Edwards Deming Agile Transformation is a means to an end. Agility is
Quick update on the book. Both the paperback and Kindle versions have been revised and updated, and are now available
Team wishing to enact improvements in their delivery performance can look to Little’s Law for guidance.