Sprint challenges

The sprint briefing is a document that you provide to all participants to help them prepare for the sprint. First, start with the design sprint challenge, which introduces your team to the sprint goals.

Identify key deliverables

Next, you need to identify the key deliverables, which is what your team actually wants to create at the end of the sprint. For example, you might say we want to have a full prototype that includes the feature update.

Attendees

Then it's on to the logistics. Everyone participating in the sprint needs to know where the sprint will take place and when it will be held. You also want to list who is participating and the name of the Sprint Master. Usually the Sprint Master is the person who sends out the briefing, but that's not always the case. If you want to name a Sprint Master, you should do so before you send out the briefing.

Approvers

Next, add approvers. Do you have some supervisors who need to sign off on the product before launch? This is the right place to note them. If your product needs official approval from the CEO before launch, this should be mentioned in the Sprint Brief. Your Sprint Brief should also include a list of resources. For short-term sprints, there is likely already a team assigned to that project. For long-term sprints, you may need to create a plan to secure additional resources.

Project overview

Next, we have the project overview, where you should explain the current state of the project, mention obstacles that are in your way, mention early successes if you have any, and outline the expected launch plan.

Sprint schedule

Finally, wrap it all up with a sprint plan, an hour-by-hour schedule for the five-day sprint, including break times. This lets people know what to expect and gives them time to prepare so you can keep things moving during the sprint.