Projects Status

The Project Status screen is a real-time heat map that gives users a complete view into the progress and health of all their projects. The goal of this screen is to show at a glance projects that might require attention.  This page is most useful to people who are responsible for managing multiple projects and multiple teams, such as development managers.



 enlarge screenshot



The Projects Status screen shows a list of all the current iterations in all the projects you are a member of or you have xView access to.  By default this list is sorted by the Late Items column and then by the Time Elapsed column.  This ends up showing the iterations with the greatest percentage of late items (stories, bugs, issues and risks based on their estimates) at the top of the list.  Sorting by  Time Elapsed is done so that iterations that are closer to the end are displayed above the ones that have more time remaining.


Each row in the list displays some metrics that communicate possible areas of concern.  For instance, if the current rate of work being completed indicates that some items will not be completed, some action may be required.  Similarly, if there are any blocking bugs, issues, or risks, something may need to be done to unblock them.  The metrics are intended to start discussion and to help those in a management role figure out where they are needed most.




The following section will explain what each column is used for and how to intepret the information provided within.


Project / Iteration

This column displays the name of the project and the current iteration and can be used for sorting.  It also contains an arrow icon which can be clicked to drill down and view more details about the iteration.


Blocking Bugs, Issues, and Risks

These columns display a count of the number of blocking bugs, issues, and risks in the current iteration.  If the count for any item is zero, the box is not displayed at all.  To see exactly which items are blocking, expand the row and see the Blocking Bugs, Blocking Issues, and Blocking Risks sections.  Clicking the links will open the items in the TeamPulse Silverlight client.

enlarge screenshot


Time Elapsed

This column displays a simple progress bar indicating how many days into the iteration you are.  It is not an indication of progress on the work that is part of the iteration, but rather a percentage of time elapsed.  You can sort on this column to see which iterations are nearer to completing.



enlarge screenshot 



This column has a chart that shows the rate that work is being completed this iteration.  There are three lines on the graph which show the actual work completed, the optimal trend, and the actual trend.  The actual trend is used to calculate the information shown in the Estimated Completion and Late Items columns.


The burndown is calculated using the burndown mode chosen for the project.  The default burndown mode is by task estimate but you can also use estimate (based on stories, bugs, issues and risks in the iteration), task count, and task work remaining.  You can change the default burndown mode used by a project from the tracking screens settings xView Settings page.


To get a larger view of the burndown chart, expand the row.  In the expanded view you can also use the Burndown by drop-down list to get a different view of the chart, estimated days late, and late items for this iteration.  Please note that if you change the burndown mode in this way, the setting is not remembered between page refreshes.


enlarge screenshot


Estimated Completion

The estimated completion column uses the burndown trend to estimate how many days it will take you to finish the remaining work in the iteration.  The number of days late or early is displayed as well as a percentage of the total number of days in the iteration.  The percentage value is used for sorting this column because in general, being a day late on a four week iteration shouldn't be as bad as being a day late on a one week iteration.


If the burndown trend is flat or going up, "Will Never Finish" is displayed because at the current rate, there is no way for the work in the current iteration to ever complete.

 enlarge screenshot


Late Items

This column uses the burndown trend to estimate both the number of stories, bugs, issues and risks that could be late as well how much of the total work, based on the estimates, the late items make up.  For example, if you have two stories in an iteration, one with an estimate of 1, and the other with an estimate of 2, if the latter will be late, the cell will show "1 item late (67% of total estimate)".


When determining which items will be late, the backlog priority is used.  The calculation assumes that higher priority items are worked on before lower priority items.  To see a list of which items might be late, expand the row and find the Late Items section.  To view the details of the story, bug, issue or risk, click the link to open it in TeamPulse.


It is also possible that you might be trending to finish your work early.  If this is the case, the cell will show an estimate of how many "units" of work are available.  The reason the term "units" is used is because this number is based on the burndown mode you are using and the estimation technique you use.  For instance, if you chose to burndown by estimate and you estimate using story points, the information in the cell can be used to help determine what size of story will fit in the iteration.  On the other hand, you might be using the task estimate burndown mode and estimating your tasks in hours.  In this case "units" can be taken to mean how many task hours worth of work you could still fit in.

    enlarge screenshot    enlarge screenshot


Unplanned Stories

This column shows the number of unplanned stories that are part of this iteration.  This column can be used to help identify a possible reason why some work didn't get finished or to flag an area of your process that could be improved.


A story is considered unplanned if it was added to an iteration a certain number of days after the iteration started.  For instance, if you use two week iterations and you add a story to it four days into the iteration, it will be considered unplanned.  This "grace period" is configurable and you can see the xView Settings section for more information about changing it.


To see a list of which stories are considered unplanned, expand the row and find the Unplanned Stories section. To view the details of the story, click the link to open it in TeamPulse.


enlarge screenshot


Tracking Screens Settings

Some of the metrics can be configured to better suit how your project is run.  The view and modify the settings, click the button at the end of the row.  For more information, see the xView Settings section.


 enlarge screenshot