Agile Maturity Assessments
An Agile maturity assessment evaluates an organization, team, or department’s adoption, practice, and proficiency in Agile methodologies. It helps identify […]
An Agile maturity assessment evaluates an organization, team, or department’s adoption, practice, and proficiency in Agile methodologies. It helps identify […]
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
Summary Retrospectives and surveys both play a role in organizational learning, adaptation and improvement. Retrospectives are an integral part of
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 The PDCA (Plan-Do-Check-Adjust) cycle is a framework for continuous improvement that can help organizations and teams solve problems and
In a previous post, we talked about the benefits of team surveys as a method of driving improvement. In this
Summary Retrospectives are a fundamental practice in all agile frameworks. Retrospectives enable Agile delivery teams to continuously improve their performance
Summary Team wishing to enact improvements in either Cycle Time or Throughput can leverage Little’s Law for guidance WIP, Cycle
What are the challenges in building a culture where everyone is engaged in continuous and sustained improvement? First, an organization’s
Agile software development has its roots in the lean manufacturing paradigm developed at Toyota – the Toyota Production System (TPS).