Working with Visual Studio 2010 - Part 4

 

0:00

hi my name is Julio casal and in this

0:02

video I will show you how to plan your

0:05

iteration or sprint using visual studio

0:07

2010 now remember we are using beta 2 of

0:11

both visual studio 2010 and this is to

0:14

the team foundation server 2010 so so

0:17

far we have created our team project for

0:20

our bookstore project and we have to

0:24

find some user stories some initial

0:26

tasks to do and we have also set up or

0:29

our team ok this team is built of one

0:34

project manager a one designer one

0:37

developer and a one tester ok so what we

0:42

want to do now is to plan the sprint and

0:45

what I mean by planning the Sprint is to

0:49

specify which will be the length of the

0:54

entire sprint or iteration and who will

0:58

be participating in this print how much

1:01

time does he has available and for the

1:04

Sprint and make sure we are not

1:06

allocating a more time that is available

1:09

in each sprint ok so remember that in

1:14

this chrome you must always plan fi your

1:16

your activities in sprints usually the

1:19

Sprint's are made of the same amount of

1:22

time ok so how do we do this let's open

1:27

visual studio ok and for this a video I

1:36

will be taking the role of the product

1:38

manager which in this case is scott

1:42

brown ok so now what I want to do is to

1:52

choose a very very useful very very nice

1:56

workbook that you will find in the

1:59

document samples and templates sorry in

2:03

the shared documents a document library

2:06

and you can see you have a folder for

2:10

each of your iterations so in this case

2:12

I will open what we

2:13

the hydration one back lock okay let's

2:18

enter credentials okay so this work is

2:33

very useful because it lets lets you see

2:36

a boat your user stories and and inside

2:41

is each user story you can see each of

2:45

the tasks that are linked or our child

2:48

of each user story okay now let's edit

2:53

this workbook because we will be saving

2:55

the changes in the end and what we want

2:58

to do right now is to specify how much

3:01

time in hours is allowed for each of

3:04

these tasks so let me quickly specify

3:07

the time for these tasks okay let's say

3:13

16 hours for those tasks related to sell

3:17

a book and for the book list screen

3:20

let's say it is the and there is his

3:22

desk so let's specify 10 hour for each

3:25

of this and for the appt book screen

3:28

let's say will be 14 hours for this and

3:32

for the design as it is very small let's

3:34

just specify 12 you see aspect i specify

3:37

16 hours for this one because it's like

3:39

a transactional screen so it may involve

3:42

some validations some transactions and

3:44

some stuff okay so now that we have do

3:48

this we have done this we must certify

3:51

who will be in charge of each of these

3:53

tasks so let's say that for these tasks

4:00

we will specify Joe okay Joe will not be

4:05

testing but Rachel okay in this order

4:09

one testing again Rachel who you will be

4:13

building and job will be designing and

4:18

again julio builds rachel tests and Joe

4:24

will be designing

4:26

okay now that we did that what we have

4:30

to do is to switch to the next to the

4:35

next we can eat and we have to

4:38

specify details about the iteration like

4:42

which is this iteration and the length

4:44

of the iteration so as we know this will

4:47

be iteration 1 and let's say this that

4:51

this will be a very very short sprint

4:54

like one week okay just a quick note

4:58

here and i am using not real not very

5:01

real values for scrum process i mean i

5:04

will specify a one-week iteration and i

5:07

already specified very long tasks like

5:10

16 our tasks which is too much but i am

5:14

just using those values for this example

5:15

okay so let's say that this will be one

5:18

week and we will start in november very

5:22

2009 and the end will be on december for

5:28

2009 that that gives me five days for

5:33

this iteration ok in the interruption

5:35

staff which we will not be using for

5:37

this video you can specify any kind of

5:39

interruption in in your sprint so if any

5:42

team member can be in each of the in any

5:46

of the days of the sprint because i know

5:48

maybe he's sick or well not sick but

5:50

maybe he has to do some kind of training

5:53

or some extra project stuff you can

5:55

specify it here or in any holidays can

5:58

be safe I here if you modify this

6:00

adding any specific date here the

6:03

available dates for the Sprint will be

6:05

also modified ok so let's switch to the

6:09

capacity tab which is the very

6:11

interesting one here you can see how

6:14

much a remaining work is for for this

6:18

sprint how much a capacity is remaining

6:22

how much is utilized how much is

6:25

overused which is I as I guys we have

6:28

not still assignment any work everything

6:31

is over or reduce in this in this sprint

6:34

so let's specify the team members here

6:37

so we do have Rachel Green

6:39

we have joe black and which have we have

6:43

who Lucas oh ok so as you can see this

6:50

sheet is already telling me very

6:52

interesting stuff you can see that we ok

7:00

we have we are not using a two hours of

7:06

the old available hours in this sprint

7:09

and we can also see that Joe Black is

7:13

overused by 14 hours poor Joe his he has

7:17

too much work and who look a cell has a

7:20

16 hours free so okay so that's not

7:25

possible this is not very a very well

7:28

balanced sprint so what we can do here

7:31

is just to check back our iteration

7:34

backlog okay you could change the hours

7:38

allocated for any possible tasks but in

7:41

this case let's take a look as at this

7:44

first user story I want to sell a book

7:46

and we can see that there's some mistake

7:48

here okay Joe is the designer so he's

7:51

not supposed to be built in the screen

7:52

so maybe the developer should do that

7:55

which is coolio okay then as as soon as

7:59

we change that let's go back to capacity

8:01

and you can see that the values have

8:03

already changed it and this is letting

8:06

us know that nobody is overused in here

8:09

and Joey even has two hours free which

8:13

is good it's good to have some spare

8:17

time for the Sprint and we have a very

8:20

healthy very good a planification for

8:22

this spring now so I think that that's

8:26

pretty much it for for this video okay

8:30

so remember to always use this this

8:33

worksheet before starting toward your

8:36

actual project to have a very good idea

8:38

of how you are planning find your the

8:41

alteration and no