Sprints are used to validate the potential of ideas using sprint methodology to fulfill specified business criteria and evidence needed to approve one or more idea.

Sprints can be created from two different idea sources (Open Ideas & Challenges), but ALWAYS has to be connected to at least one idea. These ideas often show signs of potential, but are either too complex or have too many unanswered variables to approve directly from an Open idea or Challenge.

Typically, Team Leaders are given permission to creates sprints, although this permission can be given to anyone within Selected User Permissions. Check out Managing User Permissions for details on how to do this.
​

Using the right-side navigation, select Ideas to view active ideas in the system. You can use the Filter dropdown to view Trending ideas, Top Votes ideas, Latest ideas, and so on. 

Select the idea that you want to push to a sprint.

Once inside the idea, select the icon in the upper right corner that looks like >>>

Using the right-side navigation, select Challenges to view active challenges in the system. You can use the Filter dropdown to view Countdown (challenges soon to end), historical challenges (challenges that already ended), trending ideas (found in challenges), and more. 

Select the idea that you want to push to a sprint.

Once inside the challenge, review the ideas to find the one or several that you want to promote to a sprint. Select the icon in the upper right corner that looks like >>>

This will direct you to a page to build out the framework and parameters for the Sprint. This includes:

*Ideas in Sprint: This page will always start with one idea in the sprint, but can include more ideas if desired. This is typically done when two or more ideas are similar and should be consolidated to validated together.

*Business Criteria: These are deliverables that further build out more complex ideas. Examples could be; investment estimate, delivery estimate, needed resources and people, etc. 

*Evidence required: This is the type of evidence that is needed from the sprint team in order to approve the idea. Examples could be; proof of cost saving, customer testing, proof of demand, etc.

*Team: This team can consist of many or few individuals that are responsible for providing the business criteria and evidence needed to approve the idea. Teams can be made up of individuals in individual departments of people from multiple departments depending on the idea in question. 

*Remember: Identify a sprint leader who is responsible for ensuring the sprint progresses in a timely manner and has all business criteria and evidence fulfilled before approving or archiving the sprint.

*Sprint Timing: Sprints can be as short as 24 hours, or as long as three years. Due to the nature of sprints though, it is advised to make sprints no longer than one month as often as possible.

*Audience: You can control who can view and comment on the sprint in the same way you can for ideas and challenges. You can make the audience as broad or specific as you want as shown below.

To invite non-employees to participate in the sprint, check out the following article on Creating Groups.

Using the right-side navigation, select Ideas to view active ideas in the system. You can use the Filter dropdown to view Trending ideas, Top Votes ideas, Latest ideas, and so on. Select the idea that you want to push to a sprint.