Welcome to the sprint!In the Sprint, you will build a realistic product/ process in 5 days.

Sprints have their origin in software development and manufacturing fields. Google Venture formalized the process.(SPRINT by Jake Knapp)

Rules of the Sprint:1. The Facilitator is in charge of the

schedule and taking notes. 2. The Decider makes the tough

decisions.3. The Scrum Master keeps the

team on task.4. No devices in the room (laptops

or cell phones). *step out if you need to.

5. 6-10 people on the Sprint team

RPPR Sprint TeamMelinda MichaelAllison MeaghanKelly AmyJackson (Paige)ManzoorCody

Sprint Challenges:Abbreviated format

(Traditional Sprint: 5 days/6 hrs ea vs. FSP Sprint: 5 days/2 hrs ea)Room schedulingRolling white boardIndividual schedules

How the sprint works:

Nobody knows everything, so you share info.

Ask the experts

Invite experts on the problem to the Sprint. Talk to one person at a time. Facilitator takes notes on board and team takes “How Might We” Notes

This is a simple diagram of the process or problem with around 5-15 steps. This will be how it currently looks-NOT how you want it to look. It helps you to identify the problem.

“How Might We” Notes

Identify “broken” parts of the process and decide where to focus.

This day is the biggest departure from the workgroup model we currently use.

Group brainstorms don’t work, so you sketch alone.

Your sketches will look like this:

We did not combine our sketches into “storyboards,” as recommended due to time restrictions…but we should have.

Sticky decision

Choose the best sketches with silent review and structured critique.

Sticky decision

We combined Decision Day with Sketching Day on Wednesday… leaving us Thursday and Friday to re-map the process build our materials.

Thursday: Re-MappingWe designed what the process should be.

At this stage, we had developed a shared understanding of the process and of RPPR handoff timepoints.

Determined we needed: • RPPR Process Checklist• SPO Final Review Checklist• GCO Sub Document

Checklist• 2 SPO Email Templates• 1 GCO Email Template

We spent Friday building the RPPR Process Checklist.

We assigned the other materials needed to individuals and set up a follow-up meeting to go over them.

One of the challenging parts of the Sprint was that just as we discovered what materials we needed to build, we ran out of Sprint time to build them. More time dedicated to future Sprint sessions will help with this

The 5-Day Sprint ended!

GCO Subsite Document Checklist

SPO Final Review Checklist

Sprint Follow Up SurveyWhat could have improved the Sprint?-More time allocated (62.5%)-Dedicated room space (62.5%)-Prior education on the problem (37%)

Sprint Follow Up Survey

Sprint Follow Up Survey

Sprint Follow Up Survey

Sprint Follow Up Survey

Sprint Follow Up Survey

Analysis• We should consider the Sprint

model for future problem-solving opportunities

• We should seek opportunities to bring individual problem-solving techniques into group problem-solving sessions

Recommendations for future Sprints• 3-4 hours/day• Dedicated room space, if

possible• Allow for “storyboarding” • Multiple shorter sketching

sessions• Offer a summary of the

problem to the Sprint team in advance to help promote understanding

…But what about the RPPR Process? Did the Sprint solve it?SPOs and GCOs have begun using the checklists, templates, and the process created in the Sprint. We will check in at the 4-month point to determine if we need to modify it.*We anticipate that our pending new systems may yield the need to modify as well.

Want to learn more about the Sprint session?Check out the Sprint folder on the G Drive to see our documents, pictures, templates, survey, etc. You can also read the article I’ve been writing about it in that folder.(An Analysis of Collaborative Problem-Solving Mechanisms in Sponsored Projects: Applying the 5-Day Sprint Model)

Thank you to this fantastic first Sprint team and to Aaron and Melinda for letting us try out this problem-solving model here in FSP!