Working with Visual Studio 2010 - Part 11

 

In the last part of the series I show how to track the progress of your team using the new SharePoint Dashboards and the SQL Server Reporting Services that are part of the Team Foundation Server 2010 installation.

0:00

hi my name is Julio gazelle and in this

0:02

video I will show you how to review your

0:05

team progress using the new SharePoint

0:07

dashboards and the sequel server

0:09

reporting services reports that come

0:12

with team foundation server 2010

0:14

remember we are using beta 2 of team

0:17

foundation server 2010 and visual studio

0:19

tonight on ok so at different stages of

0:24

your a software lifecycle and your

0:28

product development you will want to

0:30

know which is the current state of the

0:32

development you know how fast are we

0:35

doing the tasks how much task have we

0:37

closed ok how much bugs have been have

0:40

been found ok which will be very useful

0:44

information for future iterations in

0:46

your project so here we will like to to

0:50

see all these information using both

0:53

sharepoint and reporting services which

0:55

are an integral part of team foundation

0:58

server 2010 so let's see how how to do

1:00

that I will now enter this one studio

1:03

2010 which is not really necessary but

1:07

let's just do it for this time in order

1:11

to see a nice way to connect to the

1:14

break photo from visual studio now that

1:18

we are here I just logged in as as a

1:21

developer and I will right click in the

1:25

team project and click on show predict

1:27

portal ok this will ask me again for

1:31

credentials ok so right now i am just

1:38

logging in into a SharePoint portal that

1:41

was is installed along with the team

1:43

foundation server 2010 installation i am

1:47

using a microsoft office sharepoint

1:49

server twenty two thousand seven for

1:53

this integration so first thing that you

1:57

can see here let's just scroll a little

2:00

bit to the right side here you can see

2:03

the different project work items that

2:08

are

2:09

and have being worked recently into the

2:12

in the project so you can see that there

2:15

have been seven reported backs while

2:17

seven were closed ten tasks six text

2:22

test cases and three user stories okay

2:25

and here you can also see the status of

2:29

the reason builds you remember in the

2:31

last video we talked about making builds

2:33

work here you can see the status of

2:35

recent builds so if you have regular

2:37

builds anytime you enter here you can

2:40

quickly see the status of the latest

2:42

builds can see this one is screen

2:44

succeeded this one partially succeeded

2:46

this one failed and this one's so silly

2:48

the game over here you can see the

2:52

recent check-ins that the development

2:54

team has performed and the different

2:57

comments that they entered for each of

2:59

these check-ins okay in the in the

3:03

center of this screen we are seeing

3:06

several dash words that come with a team

3:11

foundation server 2010 and office

3:12

sharepoint server 2727 sorry 2007 so

3:17

here you can see for example the TAS

3:20

word burned down which is a very common

3:24

in that shirt in many a Jo methods which

3:29

shows the remaining work and the trend

3:32

of the work that is being done at the

3:35

moment so okay so just keep remember

3:39

that this is not a real project what I

3:42

am tracking in this desert right now

3:44

it's just the sum of different samples

3:46

that I have performed so maybe this is

3:49

not the best example but here you can

3:51

see the remaining work that it existed

3:55

the sum of the different the different

3:58

tasks that the team has still yet to

4:01

perform which you can see in the blue

4:03

area and if you would see that a green

4:06

area that will be the completed work and

4:08

in this black this black line is ideal

4:12

trend which means when would we ideally

4:16

finish the

4:18

completing the tasks okay over here you

4:23

can see the task progress the test

4:25

progress shows you how much tasks are

4:28

still a active which are the blue ones

4:30

and how much of of them are already

4:33

closed which is the green portion okay

4:36

over here you can see the user story

4:38

progress which means how much of the

4:41

user stories are still active in this

4:44

one you can see the seven issue trend

4:47

dates okay so this shows you the this is

4:53

related to box which means that for

4:55

example the blue the blue line is the

5:00

day the the some of the different box

5:04

that has arrived and when they arrived

5:07

when were they detected the yellow one

5:12

is the box that were resolved and the

5:15

green ones are the box that I have

5:18

already been closed by the testing team

5:20

over here if there were any issues in

5:23

the recorded in the project you would

5:25

see them over here okay now this is just

5:28

one of the possible dashboards that you

5:30

can access if you want to see more

5:32

dashboards and just go to the left side

5:34

left side of the other portal for

5:36

example let's split on quality you can

5:41

see these are there are more reports

5:43

loading here remember all this

5:45

information is coming from the sequel

5:47

server analysis services databases that

5:51

that are also installed with team

5:54

foundation server 2010 and that are all

5:56

the time tracking the progress of the

5:58

other team so for example in this one

6:02

you can see the build status okay of the

6:05

latest builds okay so for example you

6:08

can see this red or pink portion is

6:12

related to the failed builds in the

6:14

yesterday which would be 16 January

6:17

which was yesterday they bring one are

6:19

they built start that partially

6:21

succeeded and then this purple one is

6:24

the ones that actually succeeded okay

6:26

and same same you can see for the old

6:28

days

6:31

over here you can see the bug progress

6:33

where the blue one the blue area are the

6:36

active box the green area are the closet

6:39

box and if there was there was any jello

6:41

that will be the result box you can see

6:44

box activations over here which there's

6:46

no one at the moment code coverage if

6:49

you enable code coverage in visual

6:50

studio you can also see the code

6:52

coverage percentage over here you know

6:55

it's always good to have a very hike

6:57

code coverage in your code and over here

7:00

the code churn shows you how much lines

7:02

of code has been added in different days

7:06

of the project ok and this same way you

7:09

can keep checking the different

7:11

dashboards that are coming with team

7:14

foundation server 2010 ok you can see

7:16

this has the test one the box ones you

7:19

can see testing ok they're just loading

7:25

can take a little while sometimes you

7:30

can see the bills well there's a lot of

7:34

dashboards that you can see here another

7:36

way to take a look at the progress of

7:38

the project is going to the reports

7:41

section over here this is actually

7:43

redirecting us to the reporting services

7:46

sequel server reporting services a

7:47

portal that is also extracting

7:51

information from the analysis services

7:52

database so for example if we go to

7:56

project management you can see there are

7:58

several reports are ready prepared for

8:00

you to take a look let's go to burn down

8:03

and burn rate so the nice thing about

8:07

this other a reporting services portal

8:11

is that these reports are a configurable

8:13

which which means that you can enter

8:16

parameters like sample here you could

8:19

use you will be able to select the

8:21

iteration they were item type that you

8:23

want to see how we want to measure stuff

8:26

I duration and I mean interation started

8:29

ratio name the area the state of the of

8:34

the items and then the trend line that

8:37

you want to see and these reports are

8:39

usually a little bit more detailed you

8:43

know

8:44

you see a nice explanation here of what

8:46

are we looking at you can see here there

8:49

are similar report that we saw in the

8:51

dashboard but a little bit more big and

8:54

more explained here okay you can see

8:58

additional additional wraps over here

9:00

the pawn rate ok and the assignment of

9:05

work in the project so this is like a

9:08

little bit more detailed let's take a

9:10

look for example remaining work ok and

9:18

well this way you can always keep track

9:21

of of your project so remember you have

9:23

all this information all the time just

9:26

keep any every work item update