Screenshots

Product Views

The Product Backlog

ProductBacklog.JPG

This is the main Product Backlog view for, as it happens the Scrumpy application itself. This Portfolio containing the latest Scrumpy Product Backlog is shipped with the application. From this view a number of Stories can be selected, dragged and dropped on the table to alter their priority or onto Releases and Sprints in the Tree to assign them to a Release or schedule them as candidates for a Sprint. The application is Popup Menu driven with each Tree node having an appropriate menu of actions. Clicking on a Release, Team or Sprint will show you just the Stories for that entity in the Table view. Double clicking on a Story or a leaf node in the Tree will edit that entity. The outstanding Stories each have a Forecast date based on the Average Product Velocity from today thus answering the question "When is this story likely to be done?". In this example the Forecast Date is set to "30-Jun-09". Consequently the Done Date field of the outstanding stories is being coloured to indicate the likelyhood that each Story will be completed by the end of the month. So, if I achieve the Minimum Product Velocity I have ever managed then the dark green Story will be done by the end of the month. If I achieve the Average Product Velocity then the light green stories will be done by this date and the yellow stories if I achieve the Maximum Product Velocity. For any of the red Stories to be done I would have to achieve a Velocity greater than I have ever managed before. This feature helps us to answer the question "What is likely to be done by this date?". The Hide Done checkbox restricts the view to just the outstanding stories. If one selects a number of Stories thier Story Point total is shown in the bottom right corner.

The Product Chart

ProductChart.JPG

This Chart shows the 'trajectory' of the Product by illustrating the rate at which work is being Added and Done. The cumulative difference between the two is the amount of work Outstanding. It is showing that the rate at which work is being added i.e. discovered is slowing and that the rate at which I am doing the work is increasing. Consequently the work Outstanding has peaked and is starting to decline. The actual Min, Average and Max Product Velocity quantities are available on the Velocity Tab. This chart illustrates clearly how work is discovered as we proceed, a fundamental reality of software development.

Team Views

The Team Velocity Chart

TeamChart.JPG

A Chart showing the Team Velocity against time allowing you to measure the effect of changes in development practices. The Stats Tab provides the precise Velocity values, helping the Team decide how many candidate Stories they can pull into a Sprint and still have a good chance of completing them all. Active Sprints are highlighted in red. The Committed bar indicates the total Story Points that were committed at the start of the Sprint. Capturing and presenting this information against the actual Story Points Done in the Sprint helps the Team to see if they are consistently under or over estimating how much work they can pull from the Product Backlog in an iteration. I have only had this feature for the last couple of Sprints hence the limited Committed Story Point data.

Web Publication

The Product Backlog

WebBacklog.JPG

This screenshot shows the Product Backlog User Stories as published from Scrumpy and displayed in Internet Explorer. In this way the Product Backlog is always visible to any stakeholders that are interested and they can be printed out for face to face meetings.

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License