Professional Documents
Culture Documents
Contents
Introduction .......................................................................................................................................... 2 1.1 1.2 1.3 Summary ....................................................................................................................................... 2 Scenarios ....................................................................................................................................... 2 Not Implemented Scenarios ......................................................................................................... 2
Usage Guidelines................................................................................................................................... 4 2.1 2.2 2.3 2.4 2.5 Installing Scrum Solution Starter .................................................................................................. 4 Getting Started.............................................................................................................................. 4 Tracking Progress .......................................................................................................................... 5 Views ............................................................................................................................................. 8 BurnDown chart ............................................................................................................................ 8
1 INTRODUCTION
1.1 SUMMARY
Scrum is an iterative, incremental methodology for project management often seen in agile software development. Although Scrum was intended for management of software development projects, it can be used to run software maintenance teams, or as a general project/program management approach. There are 3 main items in Scum: - Product backlog: A product backlog is dynamicItems may be deleted or added at any time during the project. It is prioritizedItems with the highest priority are completed first. It is progressively refinedLower priority items are intentionally course-grained. - Sprint backlog: A sprint backlog is a negotiated set of items from the product backlog that a team commits to complete during the time box of a sprint. Items in the sprint backlog are broken into detailed tasks for the team members to complete. The team works collaboratively to complete the items in the sprint backlog, meeting each day (during a daily scrum) to share struggles and progress and update the sprint backlog and burn down chart accordingly. - Burn down: The sprint burn down chart is a publicly displayed chart showing remaining work in the sprint backlog. Updated every day, it gives a simple view of the sprint progress. It also provides quick visualizations for reference.
This solution starter focuses on the Project 2010 desktop client, and on the individual Scrum team experience.
1.2 SCENARIOS
A Scrum Master wants to use Project for the basics of running a sprint, including: Collecting and tracking status Managing the product backlog Managing the sprint backlog (and initial iteration planning) Viewing a burn down chart Easily exporting Scrum data to email/other apps
Higher level scenarios like integrating Scrum with EPM, or using Project to manage Scrums of Scrums (or Scrums of Scrums of Scrums)
2 USAGE GUIDELINES
2.1 INSTALLING SCRUM SOLUTION STARTER
Unzip package and run setup.exe. Follow the simple wizard steps to complete the installation.
The new scrum project will be created and Scrum ribbon tab will become available.
Once project is created, you need to populate the Product Backlog. Click the Product Backlog button on the Scrum tab and populate the task list with product backlog items. The next thing to do is create sprints. To do this, click the Add new Sprint button and fill in the following form:
The new sprint records will appear in Key Dates View and will automatically be added to the Timeline View. After that you can add tasks to appropriate Sprint by changing sprint number in Sprint column in Product Backlog View. To view items in appropriate sprint you need click the Sprint Backlog button on the Scrum tab and choice sprint in the Sprint Number drop down box. The next step is to assign resource to tasks. To do this, open Sprint or Product backlog, click the View tab, check the Details checkbox and choice the Task Form.
The task detail form will be opened. Project 2010 Scrum Solution Starter p. 5 of 9
By default this form shows the tasks start date in the Date field, remaining work of selected task and assigned resource. First of all you need choice Date to the date the work was completed and then decrement remaining work and click the Ok button, so it is reflected accurately. There are few limitations related to the form: You cant track more than 8hrs. per day You cant track time on weekend. This form is available only if the task has only one resource assigned to it.
2.4 VIEWS
The Product Backlog view is a long-term prioritized list of features, with estimates in dimensionless units (entered in the Size column. The Sprint Backlog is a list of the development tasks targeted for the current iteration (or sprint). The Key Dates view allows user to track non-work item dates, and visualize them using the timeline view, like shown in figure below: