The Latest

Are you considering kanban but not sure how you’ll predict delivery without story points, velocity, and a burndown chart? Or are you part of a Scrum team but feeling like your team could benefit from improved flow within your sprints?

On any team, from infrastructure engineering to development to HR, there is always a looming danger of one individual being the only person capable of performing a key task, either because of their technical skills, domain skills, or busin

In the rush to be more competitive, an organization is often tempted to do an across-the board, "big bang" implementation.

Agile teams ship frequently and change things all the time--by design. In the middle of all this, agile teams need to make sure that their core user flows like sign-in, shopping carts and search features still work on every new build.

On a human level, we crave outcomes and impact. But in software product development, there is something addictive about the "build more and more features" approach that often leaves people frustrated and unsatisfied.

[video:https://www.youtube.com/watch?v=-M9uWjd4WJY&feature=youtu.be width:300 height:200 align:right]

Continuous improvement is the goal of agile teams. But what does it look like when we create a continuous improvement strategy beyond our agile teams and bring it to the company level?