Many organizations have a process or mechanism through which changes are introduced, at a systemic (organizational) level, or at a more tactical level, such as changes to a particular product or set of products. Various change management models exist, with different levels of rigor and complexity. In Agile software development, change management is a continuous...Read More

It is important for Agile teams to be able to set expectations for how much work a they can complete, over a particular time horizon. The considerations that teams take into account for capacity planning purposes include: 1) Team size (also factoring in any expected lack of availability for one or more team members); 2....Read More

In a general Agile team context, there is a limit to how much work that a team can complete during a given time interval, based on evaluation of the past history of that team, along with other data, as available. In Scrum, the immediate time horizon, for planning purposes, is an iteration (Sprint). In Kanban,...Read More

On Agile teams, it is common for events or activities to happen based on a regular, predictable rhythm. In software development, one of the most common manifestations of a cadence is the Scrum notion of running consecutive iterations (Sprints) that last for a consistent amount of time (two weeks, for example). Another example of a...Read More