Working with Visual Studio 2010 - Part 2

 

0:00

hi in this

0:02

I will show you how to use user

0:05

stories to identify the main

0:07

requirements that will drive your

0:08

application remember that I am using the

0:11

beta to of Vis Studio 2010 client and

0:14

Vis Studio 2010 team Foundation server

0:17

okay so so far you have already created

0:20

your new team project in this case we

0:23

call it it bookstore and now you have to

0:26

State the requirements that will drive

0:28

your application for that we use what we

0:30

call user stories this is very uh

0:33

popular in the scrum process template

0:35

which is the one that we're using right

0:38

now so what what is user story it is no

0:41

more than a way to document your

0:44

requirements paying some particular

0:46

attention to the end user's point of

0:48

view so this will state the requirements

0:51

H the way that the end user expects to

0:54

the the application to

0:56

behave so where should we put this user

0:59

story

1:00

we use for this what we call the product

1:02

backlog which is no more than a list of

1:04

all the user stories that dve your

1:07

application where would can you find

1:09

that H product backlog you can go to

1:12

Team Explorer enter documents and share

1:16

documents okay which is actually a

1:19

document a library of your SharePoint

1:21

project portal you can see here this is

1:23

the product backlock or you can also go

1:27

to

1:28

the to your uh project

1:30

portal okay if you go to share documents

1:34

you can see here this is the product

1:36

backlog okay ER this could be a a good

1:41

way to to access the product backlog if

1:44

you don't have the visual studio

1:45

installing in your computer so let's

1:47

open the product

1:50

backlog and remember we are using h a

1:53

book story scenario so what we want is

1:56

to be able to somehow H manage

2:01

um a list of of books that could be able

2:05

to be sell in the bookstore okay so um

2:10

what we have to do is first state which

2:12

are these user stories so I just talked

2:15

about three possible user

2:17

stories we'll write right

2:19

now okay so first one will

2:22

be as a

2:24

customer I want to see a list of all

2:30

available books

2:33

okay another

2:35

one as a book

2:38

store

2:41

administrator I want to add a new

2:45

book so let's add a final one let's call

2:49

this as a

2:53

Salesman I want to sell a

2:57

book okay good we now have the three

3:02

user stories and what we should do uh

3:05

right now is to set some priorities to

3:08

these user stories okay this is a common

3:10

practice to that will help you to Al

3:13

always focus on the most important ER

3:17

user stories for your application so

3:20

from my point of view H the most

3:22

important thing here is that the user

3:24

can see the list of books and that the

3:26

salesman can actually sell a book so

3:29

let's put uh priority one for both these

3:32

user stories and let's just use priority

3:35

two for the last for the third one now H

3:39

now that you have priorities you should

3:41

have some um

3:43

estimation for the size of your res

3:47

stories you know this will help you um

3:50

on estimating um how much work can be

3:54

done in each uh product ER cycle which

3:58

we call Sprint in the scrum process so

4:01

you will usually have a Sprints of two

4:04

or at most three weeks when you have to

4:07

deliver a new version of your product so

4:10

how can you know how much work can be

4:12

done in each Sprint you will use what we

4:15

call story points and story points is a

4:18

measure of the amount of work or the

4:20

amount of complexity in each user story

4:24

so now having these three user stories I

4:27

will H estimate that

4:30

the first one the customer wants to see

4:32

the list of available books is not

4:34

really too much complicated so let's add

4:37

uh put two story points for that one the

4:40

next one I want to add a new book well

4:42

you have to do some insertions in the

4:44

database so let's give a little bit more

4:47

complexity to this one and the last one

4:49

the salesman H wants to sell a book

4:52

might include some other complexities so

4:55

let's say five for this user story okay

4:58

so h if this was like a big project you

5:02

might say okay I have time

5:05

for H five story points in each Sprint

5:09

so you might say okay let's develop uh

5:11

these two ones first and let's and then

5:14

this one in this next Sprint okay five

5:16

story points and five here okay or any

5:20

other way okay so um now that we have

5:23

this we should state in which iteration

5:27

or which Sprint we want to develop uh

5:30

this user

5:32

story so if we open this iteration pad

5:36

cell we can see that we already have ER

5:40

stated the three iterations for this

5:43

application okay this is the default you

5:45

can also add new more iterations from

5:48

the D Explorer so let's say we will H

5:50

create a develop all these requirements

5:54

in iteration

5:55

one okay and another uh important thing

5:59

we should should state which kind of

6:00

work item is this okay as we already

6:03

know these are user stories so let's

6:06

just put user story for each of them of

6:09

them so having this the only thing that

6:11

we should do right now is to publish

6:14

this new these three new user stories

6:16

which are work items to team Foundation

6:18

server so let's H you should go to the

6:21

team uh tab in your in Excel and then

6:25

click

6:26

publish what this will do is to publish

6:30

ER each each of the three items to team

6:32

Foundation server which already did and

6:35

if now you go back to Vis Studio you can

6:38

go to um okay let's close this let's go

6:42

to word items team queries and let's

6:45

open user

6:46

stories okay you see we now have the

6:49

three user stories ready to start uh

6:51

working from here so now

6:55

um once you have the user stories stated

6:58

you should H also create the developer

7:02

or the teams tasks that will give more

7:05

uh detail to what has to be done in

7:07

order to um build uh the the

7:11

specifications the the product to

7:14

accomplish with these user stories so in

7:16

order to do that we can for example

7:18

let's go for for the first one as a

7:20

customer I want to see a list of all

7:22

available books so in order to create

7:25

tasks for this user story we will right

7:27

click here and let's say new linked word

7:30

item we will create a child word item

7:33

the kind of a task word item and let's

7:37

say that in order to do this we will

7:39

have to build the book list screen okay

7:45

which is will be our first

7:48

task and let's go back and add another

7:52

one let's say that uh we will have to

7:56

test the book list screen okay the book

7:59

list screen will be a screen we will see

8:01

the list of all the these books okay

8:03

let's hit

8:05

okay and let's uh of course you can also

8:09

State several oral details on each of

8:12

these tasks okay um for now let's just

8:16

save all

8:18

them and we're done so right now you

8:23

have at least uh you have all the user

8:26

stories uh that uh involve are involved

8:29

in your system and the tasks so that

8:32

will be all for this uh video and

8:35

hopefully in the next video we can start

8:37

writing some code see you soon