Would you like to inspect the original subtitles? These are the user uploaded subtitles that are being translated:
1
00:00:00,170 --> 00:00:05,075
Hi, again. We've covered the
basics of sprint planning.
2
00:00:05,075 --> 00:00:08,510
Now, let's build a five-day
design sprint brief.
3
00:00:08,510 --> 00:00:11,805
The sprint brief is a document
that you'll share with
4
00:00:11,805 --> 00:00:15,420
all your attendees to help
them prepare for the sprint.
5
00:00:15,420 --> 00:00:17,220
Let's check out the things that
6
00:00:17,220 --> 00:00:19,260
make up a design sprint brief.
7
00:00:19,260 --> 00:00:22,380
Start with the design
sprint challenge.
8
00:00:22,380 --> 00:00:26,310
This introduces your team
to the sprint objectives.
9
00:00:26,310 --> 00:00:29,145
Think back to the cycling
app from earlier.
10
00:00:29,145 --> 00:00:31,575
If you created a brief
for that sprint,
11
00:00:31,575 --> 00:00:35,670
the design challenge might be
build exciting new features
12
00:00:35,670 --> 00:00:37,830
for the cycling app in time
13
00:00:37,830 --> 00:00:40,320
for relaunch later in the year.
14
00:00:41,320 --> 00:00:44,690
Next, you need to identify
the key deliverables,
15
00:00:44,690 --> 00:00:46,790
meaning what your
team actually wants
16
00:00:46,790 --> 00:00:48,890
to create by the
end of the sprint.
17
00:00:48,890 --> 00:00:50,420
For the cycling app,
18
00:00:50,420 --> 00:00:52,295
you might say that
we want to have
19
00:00:52,295 --> 00:00:55,735
a complete prototype that
includes the feature update.
20
00:00:55,735 --> 00:00:57,990
Then it's on to logistics.
21
00:00:57,990 --> 00:01:01,640
First, everyone participating
in the sprint needs
22
00:01:01,640 --> 00:01:03,170
to know where the sprint will
23
00:01:03,170 --> 00:01:05,250
happen and when it will be held.
24
00:01:05,250 --> 00:01:07,130
You also want to list who's
25
00:01:07,130 --> 00:01:10,450
attending and the name
of the sprint master.
26
00:01:10,450 --> 00:01:12,830
Usually, the sprint master is
27
00:01:12,830 --> 00:01:15,380
the person who sends
out the brief,
28
00:01:15,380 --> 00:01:17,540
but that's not always the case.
29
00:01:17,540 --> 00:01:20,015
If you want to designate
a sprint master,
30
00:01:20,015 --> 00:01:22,415
you should do it before
you send the brief.
31
00:01:22,415 --> 00:01:24,820
Next, add approvers.
32
00:01:24,820 --> 00:01:26,840
Got some higher-ups
that need to sign
33
00:01:26,840 --> 00:01:28,835
off on the product before launch?
34
00:01:28,835 --> 00:01:30,550
This is the place to note it.
35
00:01:30,550 --> 00:01:33,500
If your cycling app needs
the official approval of
36
00:01:33,500 --> 00:01:36,725
Ms. Cycling Enthusiast
CEO before launching,
37
00:01:36,725 --> 00:01:38,970
the sprint brief
should mention it.
38
00:01:38,970 --> 00:01:40,535
Your sprint brief should
39
00:01:40,535 --> 00:01:42,890
also include a list of resources.
40
00:01:42,890 --> 00:01:45,080
For short-term sprints, there's
41
00:01:45,080 --> 00:01:48,095
probably a team already
assigned to this project.
42
00:01:48,095 --> 00:01:50,840
For long-term sprints,
you may need to create
43
00:01:50,840 --> 00:01:53,660
a plan to secure
additional resources.
44
00:01:53,660 --> 00:01:56,105
For example, with
the cycling app,
45
00:01:56,105 --> 00:01:58,370
you might need to
assign resources from
46
00:01:58,370 --> 00:01:59,750
engineering to take on
47
00:01:59,750 --> 00:02:02,290
the work needed to
launch the new feature.
48
00:02:02,290 --> 00:02:04,880
Next, we have the
project overview
49
00:02:04,880 --> 00:02:06,440
where you should
explain the current
50
00:02:06,440 --> 00:02:07,625
state of the project,
51
00:02:07,625 --> 00:02:09,890
call out roadblocks
that stand in your way,
52
00:02:09,890 --> 00:02:12,185
state early wins if you have any,
53
00:02:12,185 --> 00:02:14,070
and outline the
estimated launch plan.
54
00:02:15,070 --> 00:02:18,745
Finally, you wrap it all
up with a sprint schedule,
55
00:02:18,745 --> 00:02:20,780
an hour-by-hour schedule of
56
00:02:20,780 --> 00:02:23,570
the five-day sprint,
including break times.
57
00:02:23,570 --> 00:02:25,280
This lets people know what to
58
00:02:25,280 --> 00:02:27,620
expect and gives
them time to prep,
59
00:02:27,620 --> 00:02:30,565
so you can keep things moving
along during the sprint.
60
00:02:30,565 --> 00:02:32,630
You're done! You've planned
61
00:02:32,630 --> 00:02:35,300
your design sprint and
created your brief.
62
00:02:35,300 --> 00:02:37,190
The only thing left to do now
63
00:02:37,190 --> 00:02:39,410
is to put the sprint in motion.
64
00:02:39,410 --> 00:02:41,330
If you're still a little confused
65
00:02:41,330 --> 00:02:43,340
about what goes in
the design brief,
66
00:02:43,340 --> 00:02:46,950
you'll find some great
examples in the readings.
67
00:02:46,950 --> 00:02:50,090
Next up, we'll learn
more about the role of
68
00:02:50,090 --> 00:02:54,210
an entry-level UX designer
in the sprint process.4929
Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.
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
Faroese
Finnish
Galician
Georgian
German
Greek
Guarani
Haitian Creole
Hausa
Hawaiian
Hebrew
Hmong
Hungarian
Icelandic
Indonesian
Irish
Italian
Japanese
Kazakh
Kinyarwanda
Kirundi
Kongo
Korean
Krio (Sierra Leone)
Kurdish
Kyrgyz
Laothian
Latin
Latvian
Lithuanian
Luganda
Luo
Luxembourgish
Macedonian
Malagasy
Malay
Maltese
Maori
Mauritian Creole
Moldavian
Mongolian
Myanmar (Burmese)
Montenegrin
Nepali
Norwegian
Pashto
Persian
Polish
Portuguese (Brazil)
Portuguese (Portugal)
Quechua
Romanian
Romansh
Russian
Samoan
Scots Gaelic
Serbian
Sesotho
Setswana
Seychellois Creole
Shona
Sindhi
Sinhalese
Slovak
Slovenian
Somali
Spanish
Swedish
Tajik
Thai
Tigrinya
Tonga
Turkish
Turkmen
Ukrainian
Uzbek
Welsh
Wolof