Extensions Home | About Scrum Extensions

Proposing a Scrum Extension

This document explains the process of submitting and publishing an official extension to Scrum. Anyone may propose a Scrum Extension.

It may be helpful to read these instructions while referencing the below process diagram. 

1 – Submit a Draft Proposal

  1. Document your proposal using this template.
  2. Find a sponsor for your proposal.

    This is a person or community who can speak to the proposal's usage and effectiveness. This person or community must co-sign your proposal as a supporter. This ensures your idea has found support amongst others who see value in it.
  3. Email the proposal to scrumguide@scrum.org

2 – Advisor Review

You will be contacted by a member of the Proposal Review Team. This person will help you get the proposal ready for posting as a formal proposal.

This is an iterative process not subject to a timeline. However long it takes to prepare the proposal for acceptance as a formal proposal, that’s how long it takes.

Once your advisor determines the proposal is ready for public, it will be posted online with other proposals at Scrum.org.

3 – Public Review

After the extension proposal has been published online, the author will start the public review process by starting a thread about the extension on the Yahoo Scrum Development group. Additionally, authors are encouraged to market their extensions for feedback from the community.

The Public Review phase will last at least 60 days. This ensures proposals are available for community review for sufficient time to allow community scrutiny and feedback.

Proposals will stay posted publicly to encourage community review and feedback to the authors. Discussions or feedback during this period may prompt refinements of the proposal. Your extension advisor will work with you during this time if revisions are needed.

4 – Extension Review Team Consideration

Once your extension has been through the 60-day public review period, your extension advisor may submit the proposal to the Scrum Extension Review Team. The team will consider the proposal.

If accepted, the proposal will be published to the official list of Scrum Extensions at Scrum.org. If not accepted, the team will provide feedback to the author through the extension advisor, and the author may re-submit after revisions have been made.

A Picture of the Process