Overview of Templates Useful to Scrum Teams

Note: All of these templates are provided to premium members on the Templates for Team-Agility page. Any links on this page from the templates provide more, but not complete info. Go to the Premium Page to sign up if you are not already a member (first month free, no obligation).

The Outcome-based Thinking Mindset  template supports the shift in thinking required from merely working on a literal reading of a backlog item to understanding the intention (the outcome) of the backlog item.

Definition of Done, Definition of Done, Team DoR-DoD Template

  • Definition of Done mindset is one of not starting the implementation (or even the next step in a workflow) until you’ve determine how you will know you are done.  This includes not only immediate functional acceptance criteria but can also adhering to standards and regulations, and meeting non-functional criteria such as creating or updating documentation and obtaining approval from specific stakeholders.  We have found that starting work before making these criteria explicit is one of the leading causes of unpredictability and re-work.
  • Definition of Ready mindset is one of not starting the implementation (or the next step in a workflow) until you’re ready to get it to Done. Over time, a team’s Definition of Ready will expand to incorporate additional readiness elements that the team has found to cause failure, rework, and other types of waste when not attended to.
  • The Team DoR-DoD Template is focused on what a typical software development team may need but it can be applied to other types of backlogs such as shared services and operations backlogs, program and portfolio backlogs.

A Minimum Business Increment (MBI) is the smallest chunk of work from which we can realize business value. An MBI Mindset is one where, to obtain a specific goal or outcome, we always attempt to discover and select the minimum scope needed to realize the desired goal/outcome.

Team-Agility Scorecard This provides a roadmap for improving your team agility.

Components of a good Scrum/Kanban Board

How we agree to new practices

How to do a Retrospection The After Action Review is a simple and powerful tool to help a team learn from their experiences in order to gain immediate, concrete improvements in performance. It is a more general and widely useful approach than the retrospection. An “action” is any major or routine activity or event that a team of people undertakes, especially those events that they or other similar teams will likely repeat in the future.

Classes of Service  The work done by most organizations falls into different types. For instance, a capability you are developing may have to be delivered by a certain key date: If the capability is not delivered by then, the amount of value it delivers drops precipitously or there may even be legal consequences. This is very different from work that “gets done when it gets done.”

Classes of Service are the main types of work done by the organization/team. Different Classes of Service are differentiated by their amount of time pressure or urgency, as well as separate needs such as making sure that at least some items of a given type are worked on.

Agreements to make with other teams and managementThe Guardrails for Lean-Agile transformation are a set of agreements and questions to help the organization assure it is staying on course in its transformation and to be able to make decisions at a local level that are aligned to the rest of the value stream.

Ensuring what’s being built can be delivered.  This should be part of the Definition of Ready for an MBI.

Going  beyond “Scrum-but” (how to change practices that commonly get dropped by those new to Scrum)