Building a Sprint Backlog with the Work Breakdown Structure (WBS Beta)

In Accolade Projects, the WBS Beta tab provides a clear roadmap for the project, enabling team members to visualize the interdependencies between backlogs, sprints, and stories. Moreover, the WBS facilitates resource allocation and scheduling, allowing project managers to assign tasks appropriately and optimize resource utilization.

This topic describes the WBS Beta tab. The original WBS tab remains available, and the WBS Beta page will eventually replace it. The original page will be removed in a future release. For the procedures that apply to that tab, refer to Building a Sprint Backlog with the Work Breakdown Structure (WBS).

The following Scrum items can be created in the WBS:

  • Backlog:

    • Product Backlog: A prioritized list of all desired work for the product, including features, enhancements, and fixes. It is managed by the Product Owner and evolves as requirements change.

    • Sprint Backlog: A subset of the Product Backlog that the team commits to completing during a specific Sprint. It includes tasks and user stories that the team plans to address in that Sprint.

  • Sprint: A time-boxed iteration (typically 2-4 weeks) during which a Scrum team works to complete a set of Product Backlog items. At the end of the Sprint, the team delivers a potentially shippable product increment.

  • Release: The deployment of a product increment or set of increments to the production environment. Releases can be planned or done as part of the Scrum process, often at the end of Sprints or based on the readiness of the product.

  • Epic: A large, high-level user story or feature that can be broken down into smaller, more manageable user stories or tasks. Epics represent broad objectives and are often divided into multiple Sprints.

  • User Story: A brief, informal description of a feature or functionality from the end-user’s perspective. User stories are used to capture requirements and define what needs to be built, often following the format "As a [user], I want [goal] so that [benefit]."

  • QA Task: Quality Assurance (QA) tasks are specific activities related to testing and ensuring the quality of the product. These tasks are part of the Sprint Backlog and focus on validating that the product increment meets the defined acceptance criteria.

  • Defect: An issue or bug in the product that causes it to behave incorrectly or fail to meet the specified requirements. Defects are typically identified during testing and must be resolved before the product can be considered complete or ready for release.

  • Task: A task is a specific, actionable piece of work needed to complete a user story or backlog item. Tasks are detailed activities assigned to team members to track progress and ensure that user stories are fully implemented during a sprint.

To create the Work Breakdown Structure:

This procedure requires a PMO or Project Manager user role.

  1. Log in to Accolade Projects.
  2. To locate the project, do either of the following:
    • Search via the Quick Search Bar on the top right of the screen.

    • For a project currently being worked on, select Workspace, located on the navigation bar at the top of the page, and click on the My Projects tab.

    • If the project has not started yet, select Plan, located on the navigation bar at the top of the page, and click on Proposed Projects.

    • If the project is in-flight, select Manage, located on the navigation bar at the top of the page, and click on Projects (Brief) or Projects (Detailed).

  3. To access the project’s Online Project Editor, click on located to the left of the respective project. Click on the WBS Beta tab.

  4. To begin building the WBS, click New and select Add Task, Add Release, or Add Sprint.

  5. Enter a name for the backlog or task.

    • Creating a User Story also creates its Dev and QA child tasks.

  6. To add a further item relative to an existing one, right-click the item and select the type to add, then choose a placement. Before and After place the new item at the same level as the selected item, immediately above or below it. To places it one level down, inside the selected item.

  7. Continue creating items in the WBS as needed.

    • To rearrange items, drag any row to its new position. Dragging a row into a parent item re-parents it, and the WBS numbers of the affected items update automatically.

  8. Click Save.

    • To discard changes before saving, click Undo, or press Ctrl+Z.

Additional Notes on the Work Breakdown Structure

  • Items that qualify for publishing are published automatically when the grid is saved.

  • To view phases and tasks that need attention, click on Items Needing Attention.

  • To view all phases and tasks within the WBS, click on All Items.

  • To switch task dependencies from Strict to Loose temporarily, click Enforce Loose Dependencies. After loose dependencies are enforced, the start and end dates for tasks can be revised based on the dependencies originally set up.

  • To export the WBS, click the download icon and select Grid to Excel, Grid to PDF, or WBS Data Report. When the Status Details column is shown, Grid to Excel lists the selected indicators that need attention for each item, or All OK when every selected indicator is in good standing.

  • The Filter by Name/ID field searches for any item within the WBS.

  • To filter the WBS by item state, click the filter icon beside the Filter by Name/ID field and select the states to show. The states are Draft, Pending/Inflight, Completed/Deployed, Cancelled, On-Hold, and Not Required.

    Note:  By default, canceled items are not listed within the WBS.

  • To order the grid by WBS sequence, click the WBS column heading. Clicking again reverses the direction. The hierarchy is preserved, so child items stay beneath their parent. No other column can be used to sort the grid.

  • To filter a column, change which columns are shown, or move a column, click the menu icon on the column heading and select one of the following:

    • Filter to filter the grid by values in that column. The operators offered depend on the column type.

    • Columns to add or remove columns.

    • Hide column to remove the selected column from the grid.

    • Move to left section to move the column into the fixed left section of the grid.

  • To see which status indicators need attention on each item, add the Status Details column from Columns. To choose the indicators the column reports, click the selector below the column heading and select from Configuration, Resource, Alerts, Finance, Schedule, and Health. The selection is kept when returning to the project. When every selected indicator is in good standing, the cell shows a single check icon. When any selected indicator is at risk or in trouble, the cell shows only the icons for those indicators, in the color of their severity. Hover over an icon to view its description.

  • To reposition a column, drag its heading to the required position.

  • Right-click a saved item to open its actions menu. The following actions are available:
    • To view or edit the item, select Backlog Details, Epic Details, User Story Details, or Task Details, according to the item type.

    • To set the item's planned dates, select Scheduling.

    • To add an item inside or beside this one, select the type to add, then choose a placement option. The types offered depend on the item right-clicked.

    • To copy the item, select Clone Epic, Clone User Story, or Clone Task.

    • To cancel the item, select Cancel User Story or Cancel Task.

    • To remove the item, select Delete User Story or Delete Task.

    • Select Publish Eligible Tasks to publish the eligible tasks the item contains.

    • On a published task, select Send a Message to message the assignee, Add to My Watchlist to follow the task, or Unpublish Task to return the task to its unpublished state. Unpublish Task is available only while no time has been logged against the task.

    • The actions on offer depend on the state of the item, so a menu may hold fewer entries than this list.

  • To change a task's assignments, click its Assignments cell. The Edit Assignments for [task name] dialog lists the project's team members. To assign a team member, select the Assign check box in that member's row.

    • Each assigned row has its own Planned Start, Planned End Date, and Planned Hours fields, which can be edited in that row. The duration recalculates from the row's dates.

    • To give a team member more than one assignment on the same task, right-click the member's row and select Duplicate Row. The new row copies the Planned Start, Planned End Date, and Planned Hours values of the original row. Either row can then be changed without affecting the other.

    • Before the assignments are saved, a duplicated row can be removed: right-click it and select Remove Duplicate Row.

    • If the assignees' Planned Hours do not add up to the task's Planned Hours, a warning appears when OK is selected. Select Save Anyway to keep the hours as entered.

    • Select OK to return the assignments to the grid, where they remain unsaved until the grid is saved. Select Cancel to discard them.