The Project Management Framework supports the structure and principles of the Scrum methodology to create and manage your projects.

Scrum projects are composed of multiple building blocks. The following diagram illustrates the work units that comprise a project and their relationships.

• • Product - the product associated with the project; contains one or more backlogs, one of which is associated with the project
  • Backlog - a prioritized list of user stories waiting to be worked in a sprint
  • Project - contains one or more sprints; is associated with a product backlog
  • Sprint - an iterative unit of development usually lasting from 2-4 weeks; contains one or more user stories and can be associated with bugs/issues related to the sprint
  • User Story - a requirement written in business or everyday user language
  • Task - a unit of work assigned to a project resource needed to implement a user story
  • Bug - a unit of work that describes a feature or function that does not work as intended; can be part of a project, sprint, user story, or backlog
  • Issue - a unit of work that describes a problem, risk, impediment, or concern that can impact the outcome of a project; can be associated with a project, sprint, user story or backlog
  • Epic - a collection of user stories related to a single product capability

This article includes the following backlog topics:

• Viewing Scrum Projects from the Dashboard
• Creating a Scrum Project
• Displaying a Scrum Project
• Completing and Withdrawing Projects
• Other Scrum Project Articles

Viewing Scrum Projects from the Dashboard

You can select a display filter to determine which projects show on your Dashboard view.

• All Open Projects - all open Scrum and SmartBPM projects
• Open Scrum Projects -- all open Scrum projects
• All Resolved Projects - resolved Scrum and SmartBPM projects
• All Projects - open and resolved Scrum and SmartBPM projects

Filters can be selected:

• • From the Dashboard Limit Project Status by list. This selection overrides your default view.

• • From your preferences Default Dashboard View list.

Creating a Scrum Project

From the Actions menu, select.

Scrum projects reside at the highest level of the Project framework structure. Projects can be associated with:

• a product
• a release
• a backlog
• start and end dates
• milestones and themes
• sprints, user stories, tasks, bugs and issues
• target dates and work estimates
• a change history

* indicates a required field

1. 1. Enter the project detail.

NOTE: It is unlikely you will have all of the project detail available to you at the time you create the project. PMF lets you to add, update, and withdraw project elements and detail at any time during the life of the project.

• Select the Scrum methodology
• Enter the project name.
• Enter a description of the project.
• Select the product and release associated with the project.
• Select a product backlog. On this list are the backlogs for the product you selected.
• Enter the target start and end dates.
• Add project milestones and themes.
  • Milestone dates can be starting or ending dates depending on your organization's interpretation
  • Use the icons to add, insert, and delete rows

• Click Create to create the project and assign it a unique ID. The project displays in your workspace where you can begin to the build out the project tree with sprints, user stories, and tasks.

Displaying a Scrum Project

The project display is the operational workspace for a project where you can review, drill down into, and perform updates to detail and work elements of the project stored in tabs.

Display a project by:

• Searching for the Project ID or Name via the Search gadget.
• Selecting the project from the Dashboard view
• Clicking the project link in the breadcrumb trail of sprints, user stories, tasks, bugs and issues

Tree Tab

The Tree tab displays a tree grid of the sprints, user stories and tasks in the project. When you create a project, this is where you begin to add and structure project sprints. As you build out the sprints, icons identify whether a tree branch represents a sprint, user story, or a taskon the tree.

• Select the View Bugs? checkbox if you want to include bug items in the tree display.
• Click Open Backlog to display the product backlog associated with the project. If you do not have a backlog associated with the project, this button does not appear on the display. You can associate a backlog with the project using the Update Details project action.
• Click Export to export the tree to a Microsoft Project 2003 or 2007 compatible XML file.
• Click Bulk Process to display a list of open user stories that can be processed or exported to Microsoft Excel. Select one or more stories to perform these actions:
  • Add Note
  • Move Item
  • Reassign
  • Update Epic
  • Withdrawn Item
• Click Refresh to reload the tree after updates.
• Double-click a row to open a modal pop-up where can you update the details of a sprint, user story or task.
• Drag and drop rows to reorder and rank them.
• Right-click a row to display a menu of actions you can perform on a sprint, user story or task. Menu selections are based on the type of item you select.

  

Details Tab

The Details tab displays a high level view of the project's backlog, velocity, status, start and end dates, effort comparisons, milestones and themes.

Expand and contract the sections to view the project detail.

• Backlog - links to the backlog and summarizes the count and totals of stories and points associated with your current project; click the link to display the backlog in a separate tab
• Velocity - tabulates the planned and actual velocity of the project sprints; column filters allow you to sort the sprint list
• Assigned To - defaults to the next scheduled action; right click to display and select an action
• Details - describes the project
• Dates & Efforts - a high level roll up of dates and hours for the work linked to the project; click View Change History to display an audit trail of project changes
• Status - key status indicators that are also included on the Dashboard tab; click View Status History to display an audit trail of project status changes
• Milestones and Themes - lists the project milestones and themes; click a link to display work associated with the milestone or theme that you can optionally export to Microsoft Excel

Reports Tab

The Reports tab contains a selection of project reports including a Remaining Effort Burndown chart that tracks the amount of remaining effort by day throughout the project lifecycle.

The Additional Reports section links to other reports that display in a pop-up window when selected.

• Rule Updates by Resource and Task/Bugs – reports the actions taken on rules in the development environment to complete project tasks and bug fixes
• Late Tasks – lists tasks with a target end dates in the past
• Work Pending Verification – lists work that is currently in a Pending-Verification status
• User Stories by Epic- lists by epic the user stories in the project
• Open Bugs by Severity – pie chart of open bugs in the project by severity
• Weekly Bug Throughput – trend chart showing the rate of new vs. resolved bugs for the past 6 weeks
• Daily Bug Trend with Severity – trend chart showing the number and severity of bugs over the life of the project

Bugs/Issues Tab

The Bugs/Issues tab lists the open bugs and issues linked to the project.

From each list you can:

• Select a row to review and/or update it
• Add, remove, and sort the content of the list columns
• Click Export to Excel to export the list to a Microsoft Excel spreadsheet
• Click All Bugs to display a list of open and resolved bugs associated with the project
• Click Bulk Process Bugs or Bulk Process Issues to perform bulk actions on open project bugs and issues
• Click Refresh to update the list

Team Tab

The Team tab lists the members of the project team including stakeholders, their role, phone, email address. It displays the number of items assigned to each member and the remaining effort in hours for those items.

• Click the number of Assigned Items to display a list of the open items assigned a team member.
• Click the team member's name to display operator detail in a pop-up window and display additional project and organizational information.
  • Click Reporting Structure to drill down into the member's organization
  • Click View Worklist to display the member's work list.
  • Click View Project List to see the member's project list.

Notes Tab

The Notes tab displays notes, questions and responses to questions added to the project.

• Click a row to display a note or question.
• From an Actions list, select the Add Note or Add Question action to add notes and questions.

The Attachments Tab

The Attachments tab displays a list of attachments added to the project. The tab indicates the number of attachments.

• Click a row to display an attachment.
• Click to delete an attachment.
• Click New to add a new attachment.

Completing and Withdrawing Projects

Projects are complete when all items linked to them are resolved. Alternatively, they can be withdrawn prior to completion. Withdrawing a project also withdraws all open items linked to the project.

Note: User stories, and bugs in the backlog remain with the product backlog when you complete or withdraw a project.

Complete and Withdraw Project options are selected from the list of actions displayed during a project update.

• To complete a project:
  1. Resolve the sprints, stories, tasks, issues, and bugs linked to the project. If they are not resolved, the system prevents completion of the project.
  2. Select the Complete action.
  3. Enter a resolution note and optionally update the actual date and effort values.
  4. Click Submit.
• To withdraw a project:
  1. Select the Withdraw Project action. A list of open items - including sprints, stories, tasks, bug items, and issues - linked to the project are listed.
  2. Enter the reason for withdrawal and optionally update the actual date and effort values.
  3. Click Submit.

This article links to following articles about working with scrum projects in the PMF 6.1.1 release.

Adding Scrum Sprints and User Stories

Working with Scrum Backlogs

Best Practices for Managing Scrum Projects

Return to About the Project Management Framework to access all PMF articles.