Agile Planning Matrix

The Agile Planning Matrix is a 2x2 matrix used to prioritize tasks and projects in an Agile environment. It helps teams to quickly identify which tasks should be done first and which tasks can be delayed.

At a very high level, the Agile Planning Matrix is used in the context of business, project management.

Agile Planning Matrix quadrant descriptions, including examples
Want to try this template?
Other Templates

What is the Agile Planning Matrix?

A visual explanation is shown in the image above. The Agile Planning Matrix can be described as a matrix with the following quadrants:

  1. Must Do: Tasks that must be done in order to meet the project's objectives. Examples: critical bug fixes, customer requests, regulatory requirements.
  2. Should Do: Tasks that should be done, but are not essential to the project's success. Examples: minor bug fixes, feature improvements, refactoring.
  3. Could Do: Tasks that could be done, but are not essential to the project's success. Examples: refactoring, performance improvements, exploratory work.
  4. Won't Do: Tasks that should not be done. Examples: feature requests, exploratory work, low priority bug fixes.

What is the purpose of the Agile Planning Matrix?

The Agile Planning Matrix is a 2x2 matrix used to prioritize tasks and projects in an Agile environment. It helps teams to quickly identify which tasks should be done first and which tasks can be delayed. The matrix is divided into four quadrants, each representing a different priority level.

The top-left quadrant is labeled 'Must Do'. This quadrant contains tasks that must be done in order to meet the project's objectives. These tasks are usually the most important and should be done first. Examples of tasks in this quadrant include critical bug fixes, customer requests, and regulatory requirements.

The top-right quadrant is labeled 'Should Do'. This quadrant contains tasks that should be done, but are not essential to the project's success. These tasks are important, but can be delayed if necessary. Examples of tasks in this quadrant include minor bug fixes, feature improvements, and refactoring.

The bottom-left quadrant is labeled 'Could Do'. This quadrant contains tasks that could be done, but are not essential to the project's success. These tasks are nice to have, but can be delayed if necessary. Examples of tasks in this quadrant include refactoring, performance improvements, and exploratory work.

The bottom-right quadrant is labeled 'Won't Do'. This quadrant contains tasks that should not be done. These tasks are usually low priority or not relevant to the project's objectives. Examples of tasks in this quadrant include feature requests, exploratory work, and low priority bug fixes.


Want to try this template?

What templates are related to Agile Planning Matrix?

The following templates can also be categorized as business, project management and are therefore related to Agile Planning Matrix: Effort Impact Matrix, Gap Analysis Matrix, Growth Share Matrix, Kraljic Matrix, Outsourcing Matrix, PICK Matrix, Quadrant Analysis, Risk Analysis Matrix. You can browse them using the menu above.

How can I use Agile Planning Matrix in Priority Matrix?

You can get Agile Planning Matrix in your Priority Matrix in just a moment:

  1. Click to sign in or create an account in the system
  2. Start adding your items to the matrix
  3. If you prefer it, download Priority Matrix and take your data with you

Learn more about Agile Planning Matrix, and get free access to lots of other templates, at templates.app. Once you are comfortable with the document, you can easily export to Excel, if you prefer to work that way.

If you have any questions and you can't find the answer in our knowledge base, don't hesitate to contact us for help.