Afrikaans
Akan
Albanian
Amharic
Arabic
Armenian
Azerbaijani
Basque
Belarusian
Bemba
Bengali
Bihari
Bosnian
Breton
Bulgarian
Cambodian
Catalan
Cebuano
Cherokee
Chichewa
Chinese (Simplified)
Chinese (Traditional)
Corsican
Croatian
Czech
Danish
Dutch
English
Esperanto
Estonian
Ewe
Faroese
Filipino
Finnish
French
Frisian
Ga
Galician
Georgian
German
Greek
Guarani
Gujarati
Haitian Creole
Hausa
Hawaiian
Hebrew
Hindi
Hmong
Hungarian
Icelandic
Igbo
Indonesian
Interlingua
Irish
Italian
Japanese
Javanese
Kannada
Kazakh
Kinyarwanda
Kirundi
Kongo
Korean
Krio (Sierra Leone)
Kurdish
Kurdish (Soranรฎ)
Kyrgyz
Laothian
Latin
Latvian
Lingala
Lithuanian
Lozi
Luganda
Luo
Luxembourgish
Macedonian
Malagasy
Malay
Malayalam
Maltese
Maori
Marathi
Mauritian Creole
Moldavian
Mongolian
Myanmar (Burmese)
Montenegrin
Nepali
Nigerian Pidgin
Northern Sotho
Norwegian
Norwegian (Nynorsk)
Occitan
Oriya
Oromo
Pashto
Persian
Polish
Portuguese (Brazil)
Portuguese (Portugal)
Punjabi
Quechua
Romanian
Romansh
Runyakitara
Russian
Samoan
Scots Gaelic
Serbian
Serbo-Croatian
Sesotho
Setswana
Seychellois Creole
Shona
Sindhi
Sinhalese
Slovak
Slovenian
Somali
Spanish
Spanish (Latin American)
Sundanese
Swahili
Swedish
Tajik
Tamil
Tatar
Telugu
Thai
Tigrinya
Tonga
Tshiluba
Tumbuka
Turkish
Turkmen
Twi
Uighur
Ukrainian
Urdu
Uzbek
Welsh
Wolof
Xhosa
Yiddish
Yoruba
Zulu
Hi, again. We've covered the basics of sprint planning.
Now, let's build a five-day design sprint brief.
The sprint brief is a document that you'll share with
all your attendees to help them prepare for the sprint.
Let's check out the things that
make up a design sprint brief.
Start with the design sprint challenge.
This introduces your team to the sprint objectives.
Think back to the cycling app from earlier.
If you created a brief for that sprint,
the design challenge might be build exciting new features
for the cycling app in time
for relaunch later in the year.
Next, you need to identify the key deliverables,
meaning what your team actually wants
to create by the end of the sprint.
For the cycling app,
you might say that we want to have
a complete prototype that includes the feature update.
Then it's on to logistics.
First, everyone participating in the sprint needs
to know where the sprint will
happen and when it will be held.
You also want to list who's
attending and the name of the sprint master.
Usually, the sprint master is
the person who sends out the brief,
but that's not always the case.
If you want to designate a sprint master,
you should do it before you send the brief.
Next, add approvers.
Got some higher-ups that need to sign
off on the product before launch?
This is the place to note it.
If your cycling app needs the official approval of
Ms. Cycling Enthusiast CEO before launching,
the sprint brief should mention it.
Your sprint brief should
also include a list of resources.
For short-term sprints, there's
probably a team already assigned to this project.
For long-term sprints, you may need to create
a plan to secure additional resources.
For example, with the cycling app,
you might need to assign resources from
engineering to take on
the work needed to launch the new feature.
Next, we have the project overview
where you should explain the current
state of the project,
call out roadblocks that stand in your way,
state early wins if you have any,
and outline the estimated launch plan.
Finally, you wrap it all up with a sprint schedule,
an hour-by-hour schedule of
the five-day sprint, including break times.
This lets people know what to
expect and gives them time to prep,
so you can keep things moving along during the sprint.
You're done! You've planned
your design sprint and created your brief.
The only thing left to do now
is to put the sprint in motion.
If you're still a little confused
about what goes in the design brief,
you'll find some great examples in the readings.
Next up, we'll learn more about the role of
an entry-level UX designer in the sprint process.
Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.