📺 Develpreneur YouTube Episode

Video + transcript

What Is A Sprint?

2023-05-16 •Youtube

Detailed Notes

This is an overview from one of our SDLC/Agile classes (https://school.develpreneur.com/p/software_development_life_cycle).

You can find out more through our online classes at https://school.develpreneur.com and register for free. Registration will add you to our email list and you will periodically receive coupons for courses as well as notifications of the latest releases.

Transcript Text
thank you
[Music]
welcome back to building better
developers today we are going to talk
about one of these sort of foundational
kinds of things but it's also something
that a lot of people have questions
about
what is a Sprint where is the value in a
Sprint
these are common questions particularly
what is a Sprint how does it work I
think a lot of people have an idea these
days developers have gotten into that
agile approach to software development
but
I don't know that you've maybe stepped
back and said what's the value of a
Sprint why are why would we do that
now first let's step into the definition
a bit about the what is a Sprint
the shortest way or a very
straightforward way to define it is that
a Sprint is a predefined period to get
something accomplished so yeah it may be
a day a week a month a year but you
could essentially say that you know and
it yes there are different time frames
are going to sort of a different meaning
specifically because a Sprint is usually
going to be a shorter period so maybe
weeks if it's a year that's probably a
marathon or something like that thinking
to the physical real world race
application of a Sprint
a Sprint is going to be a short High
Energy race you are running a Sprint is
actually most people attribute that to
running as fast as they can for a short
period of time
the software development concept of that
is very similar to it we're going to run
hard
and get to our destination
now one of the things that a Sprint
helps us with
is that we're doing bite-sized pieces
think about that race concept a little
bit we are going for a short period of
time which means we're not going to be
able to do a lot during that
you're not going to be doing
you know a front end and a back end a
middle tier and
hundreds of hundreds of pages and things
like that
this is where we're saying okay we're
going to focus on
a feature or a group a small grouping of
features
this allows us to really do it right
essentially we're not going to have to
worry about Switching gears and what are
we working on here this thing's only
partially done things like that
another thing we get from Sprints is we
get regular wins we get to the end of
that Sprint and we are done we have
accomplished something
obviously you know if you don't get
anything done during the Sprint then
it's a regular loss but typically what
it is is that we build a Sprint or plan
a Sprint so that we are making progress
and we have a marker of the Sprint
completed and we made the progress to
whatever that point was
and with this because it's bite-sized
pieces and things like that we can
easily make adjustments to where we want
to go
think of a big software application
that's got a lot of different features
and lots of forms and reports and pages
and things like that
within the Sprints you may only tackle
you know a report or two or a page or
two or one or two features
and you can really get those done but in
the meantime there may be other things
going on in the background the industry
may change things like that that we now
have not invested in all of these other
pieces we've only invested in these
little pieces at a time which means that
we can easily make adjustments think
about running a race like a a marathon
where you are heads down you're just
your head down driving forward to your
goal
the best way the most efficient way to
do so to complete that marathon is to go
heads down and go you know you're going
from point A to point B
and just go get on the road and go
if you don't necessarily know where B is
where point B where your destination is
you're going to have to look up
periodically you're gonna have to pick
your head up slow down a little bit
assess where you're at and then decide
where you're going to go
that does take time but does allow you
to more easily adjust so if you don't
know where B is if you don't know where
your destination is
then you want to regularly pick your
head up assess where you're at and make
some adjustments
another thing and really this is the I
think the best value of a Sprint when
we're thinking about that race again
you're running hard you are driving
towards your destination when you
complete the Sprint
you get to recover you think about if
you can picture in your mind Racers
running a Sprint remember or think about
them
running really hard and they're just all
out trying to get to that finish line
and then
cross the finish line they slow down a
little bit maybe they walk around take a
deep breath and they recover
and depending on where they're at and
what they're doing
that allows them to you know recover get
a drink of water whatever it is and then
maybe 30 minutes later hour later
whatever it is
come back and do another Sprint
so now you are making progress you know
you're winning that race or you're
racing that race anyways you're racing
that Sprint and then you get to recover
and go right into the next one
so you are steadily making progress
at very High pace for a while and then
you adjust you rest you can make some
adjustments and then you go do it again
and so you are able to get the benefits
of focus
of being able to really get into
whatever that challenge is that feature
is that software that you're building
that specific piece of it and really
understand it really do it well not have
distractions get it done and then move
on to the next one
it's a you know so you get it done put
it on the shelf or whatever it is deploy
it
and then you move on to the next thing
and this allows you to have that that
benefit of what Focus gives you so
you're not spending time Switching gears
you're not spending time trying to
adjust to another feature or another
section of code you're in the code
you're that is what you're doing and I
think all of us realize that there is
value in that that is how we build the
best software
is that we really focus on it we get rid
of the distractions
we think through it we implement it all
sort of in the same
breath as it were so that it's all fresh
to us because if you write some code and
you come back six months later it's
going to be a little challenging it's
not going to be the same
so that is a Sprint and the value of one
we're going hard for a short period of
time we've got a small group of tasks
and the benefit is that we get to really
focus on those we get to really worry
just about that smaller bite-sized chunk
instead of having to think about the big
picture it goes back to the old saying
of you know how do you eat an elephant
you eat an elephant elephant a bite at a
time you can't just like take it in one
big bite it's the same thing with our
software projects it's better off if we
take those
essentially small bites chew them digest
them move on to the next one and it does
sort of fall into that slow and steady
wins the race but it is
a series of very fast Paces steady that
win the race we go hard rest recover go
hard rest recover and we do that until
we get the end of this larger race that
we want to get to
thank you
foreign
Transcript Segments
10.58

thank you

18.88

[Music]

27.119

welcome back to building better

29.22

developers today we are going to talk

31.8

about one of these sort of foundational

33.78

kinds of things but it's also something

35.76

that a lot of people have questions

37.8

about

38.94

what is a Sprint where is the value in a

42.42

Sprint

43.32

these are common questions particularly

46.739

what is a Sprint how does it work I

49.079

think a lot of people have an idea these

51

days developers have gotten into that

54.44

agile approach to software development

58.079

but

59.76

I don't know that you've maybe stepped

61.8

back and said what's the value of a

63.899

Sprint why are why would we do that

66.84

now first let's step into the definition

69

a bit about the what is a Sprint

71.1

the shortest way or a very

72.659

straightforward way to define it is that

75.24

a Sprint is a predefined period to get

77.58

something accomplished so yeah it may be

80.88

a day a week a month a year but you

84.9

could essentially say that you know and

86.82

it yes there are different time frames

89.64

are going to sort of a different meaning

91.4

specifically because a Sprint is usually

93.78

going to be a shorter period so maybe

95.88

weeks if it's a year that's probably a

98.82

marathon or something like that thinking

101.22

to the physical real world race

104.28

application of a Sprint

106.74

a Sprint is going to be a short High

110.159

Energy race you are running a Sprint is

113.759

actually most people attribute that to

116.759

running as fast as they can for a short

119.64

period of time

121.079

the software development concept of that

123.299

is very similar to it we're going to run

126.54

hard

127.439

and get to our destination

131.28

now one of the things that a Sprint

133.5

helps us with

134.94

is that we're doing bite-sized pieces

136.98

think about that race concept a little

139.14

bit we are going for a short period of

141.84

time which means we're not going to be

143.28

able to do a lot during that

145.68

you're not going to be doing

147.78

you know a front end and a back end a

150.18

middle tier and

151.98

hundreds of hundreds of pages and things

154.14

like that

155.52

this is where we're saying okay we're

157.14

going to focus on

158.7

a feature or a group a small grouping of

161.7

features

162.84

this allows us to really do it right

166.56

essentially we're not going to have to

167.879

worry about Switching gears and what are

170.16

we working on here this thing's only

171.66

partially done things like that

174.12

another thing we get from Sprints is we

176.7

get regular wins we get to the end of

179.16

that Sprint and we are done we have

182.099

accomplished something

184.099

obviously you know if you don't get

185.879

anything done during the Sprint then

187.08

it's a regular loss but typically what

189.36

it is is that we build a Sprint or plan

192.3

a Sprint so that we are making progress

196.5

and we have a marker of the Sprint

198.84

completed and we made the progress to

202.26

whatever that point was

204.599

and with this because it's bite-sized

206.879

pieces and things like that we can

209.159

easily make adjustments to where we want

211.56

to go

212.7

think of a big software application

214.56

that's got a lot of different features

216.72

and lots of forms and reports and pages

219.06

and things like that

220.799

within the Sprints you may only tackle

223.62

you know a report or two or a page or

225.54

two or one or two features

227.76

and you can really get those done but in

231.18

the meantime there may be other things

233.28

going on in the background the industry

235.68

may change things like that that we now

238.56

have not invested in all of these other

240.9

pieces we've only invested in these

243.239

little pieces at a time which means that

245.819

we can easily make adjustments think

248.099

about running a race like a a marathon

251.879

where you are heads down you're just

254.04

your head down driving forward to your

256.5

goal

257.699

the best way the most efficient way to

261

do so to complete that marathon is to go

263.699

heads down and go you know you're going

265.68

from point A to point B

268.5

and just go get on the road and go

272.22

if you don't necessarily know where B is

274.8

where point B where your destination is

277.08

you're going to have to look up

278.4

periodically you're gonna have to pick

279.96

your head up slow down a little bit

281.22

assess where you're at and then decide

282.84

where you're going to go

284.16

that does take time but does allow you

286.68

to more easily adjust so if you don't

289.259

know where B is if you don't know where

290.94

your destination is

292.5

then you want to regularly pick your

294.419

head up assess where you're at and make

297.12

some adjustments

300.12

another thing and really this is the I

302.639

think the best value of a Sprint when

305.759

we're thinking about that race again

306.9

you're running hard you are driving

310.44

towards your destination when you

313.56

complete the Sprint

315.84

you get to recover you think about if

318.06

you can picture in your mind Racers

319.979

running a Sprint remember or think about

322.56

them

323.52

running really hard and they're just all

326.52

out trying to get to that finish line

328.02

and then

329.94

cross the finish line they slow down a

332.82

little bit maybe they walk around take a

334.8

deep breath and they recover

337.08

and depending on where they're at and

338.46

what they're doing

339.78

that allows them to you know recover get

342.24

a drink of water whatever it is and then

344.1

maybe 30 minutes later hour later

345.6

whatever it is

346.74

come back and do another Sprint

349.8

so now you are making progress you know

352.919

you're winning that race or you're

354.479

racing that race anyways you're racing

356.699

that Sprint and then you get to recover

358.919

and go right into the next one

361.259

so you are steadily making progress

365.039

at very High pace for a while and then

369.84

you adjust you rest you can make some

371.82

adjustments and then you go do it again

373.8

and so you are able to get the benefits

377.22

of focus

379.139

of being able to really get into

382.44

whatever that challenge is that feature

384.84

is that software that you're building

387.68

that specific piece of it and really

390.419

understand it really do it well not have

392.4

distractions get it done and then move

395.1

on to the next one

396.72

it's a you know so you get it done put

398.52

it on the shelf or whatever it is deploy

400.38

it

401.22

and then you move on to the next thing

402.9

and this allows you to have that that

406.08

benefit of what Focus gives you so

409.56

you're not spending time Switching gears

411.24

you're not spending time trying to

413.4

adjust to another feature or another

415.86

section of code you're in the code

417.479

you're that is what you're doing and I

420.3

think all of us realize that there is

422.699

value in that that is how we build the

426.06

best software

427.319

is that we really focus on it we get rid

429.9

of the distractions

431.52

we think through it we implement it all

434.52

sort of in the same

436.199

breath as it were so that it's all fresh

439.8

to us because if you write some code and

442.38

you come back six months later it's

444.18

going to be a little challenging it's

445.68

not going to be the same

447.66

so that is a Sprint and the value of one

452.88

we're going hard for a short period of

455.34

time we've got a small group of tasks

457.74

and the benefit is that we get to really

459.72

focus on those we get to really worry

461.52

just about that smaller bite-sized chunk

464.88

instead of having to think about the big

467.22

picture it goes back to the old saying

470.099

of you know how do you eat an elephant

471.66

you eat an elephant elephant a bite at a

473.819

time you can't just like take it in one

475.319

big bite it's the same thing with our

477.36

software projects it's better off if we

479.34

take those

480.539

essentially small bites chew them digest

483.3

them move on to the next one and it does

486.06

sort of fall into that slow and steady

487.8

wins the race but it is

490.86

a series of very fast Paces steady that

496.38

win the race we go hard rest recover go

499.74

hard rest recover and we do that until

501.419

we get the end of this larger race that

504.12

we want to get to

514.86

thank you

516.899

foreign