The ScrumWorks Pro Web Client is intended as a light-weight alternative to the ScrumWorks Pro Desktop Client. The Web Client provides team members access to sprint tasks through the "Sprints" and "My Tasks" views, while managers and product owners have access to backlog management features through the "Planning" view. The "Dashboard" view gives all users access to custom web reports from the convenience of the web client.
The Web Client has four top-level areas:
In the Web Client Login section, enter your login name and password as set in the User Manager or User Preference section of the ScrumWorks Pro Desktop Client. Users administration capabilities are available in the ScrumWorks Pro Desktop Client.
If you choose the option 'Remember me for two weeks', you will be automatically logged into the Web Client each time you access the page until you explicitly logout or two weeks has transpired. For security reasons, do not use this option on computers to which other people have access.
When navigating between the different Web Client views, the last view you selected will be saved. Each time you log into the Web Client, the last page you were viewing will be loaded as your default page.
The Planning view provides the ability to create and organize backlog items into releases and sprints.
The view contains three columns that can be configured to show a product release or a team's sprints. Backlog items can be dragged to re-prioritize them within the same column, or dragged between columns to modify release and sprint associations.
Once authenticated, the Planning view is always accessible by clicking the "Planning" navigation option in the page header.
All ScrumWorks Pro users can access this view; no special permissions are required.
To select a Product:
Once you have selected your product context, you can start populating the columns with data. The dropdown for each column contains all of your active (un-archived) releases, and all teams that are working on the product.
By default, the release appearing at the top of the backlog is loaded into the left column, and the first two teams are loaded into the center and right columns respectively. Once you make a selection, it is remembered for future sessions and will be restored whenever possible.
To change what data is displayed in a column, choose a release name or team name from that column's dropdown menu.
To create a backlog item, click the new backlog item button associated with the desired target release or sprint. Upon saving, the backlog item will be associated to that sprint or release. If you create a backlog item in a sprint column, you will still be required to select the release for the new backlog item.
The create backlog item dialog will appear and the backlog item's attributes can be populated including title, description, estimate, themes, comments, and business value data. Click save when finished and the backlog item will be created. The backlog item title is required.
To create a backlog item, you must have the Create Product Backlog Item permission.
From the planning view, you can edit a backlog item's title, description, and other attributes. To open the backlog item editor, click on the backlog item's title in the Planning view. Multiple editors can be open at the same time. If a backlog item is already open, it will be brought into focus; a single backlog item cannot be open in more than one editor.
Your role affects what you can see and edit in the backlog item editor. For instance, if you don't have permission to see business weight, you will not see any business weight information.
You can change the associated release by selecting a different release from the selector. The backlog item will be moved into that release ranked at the top of that release.
To mark the backlog item as done, so it contributes toward the team's velocity, chose a Done status in the status dropdown.
To change the Business Weight of a backlog item, open the business weight accordion and update the benefit and penalty estimates. The values entered here, in combination with the effort estimate, generate a number of calculations by which the backlog item may be compared relative to its release, product, and other backlog items. The business weight, ROI, and rBV values only update upon saving the backlog item and updates will reflect the next time the editor is opened.
For an explanation of business weight and the related fields please see the user documentation for Earned Business Value.
The themes associated with a backlog item can be changed in the Themes accordion on the backlog item editor.
To add a theme to the backlog item, select it from the "Available Themes" list and use the button controls to add it to the backlog item. To remove a theme from a backlog item, select it from the "Applied Themes" list and use the button control to remove it from the backlog item. You can also double-click on a theme in either list to move the theme to the the other list. Themes may be multi-selected using Shift or Ctrl keys.
To delete a backlog item, open the backlog item's editor by clicking on the title. The editor will show a "Delete" button on the bottom left hand side of the editor.
You will be prompted to keep or delete the historic backlog item data. Keeping the data will preserve estimate history used in release level reports. Deleting the historical data will remove the backlog item and its historical effort estimates will not factor into release level reports.
From the planning view, you can organize and prioritize backlog items. Moving them within a release or sprint, as well as between releases and sprints.
To move a backlog item, you can drag it vertically from the current position and drop it to a new desired position. Moving backlog items in this manner adjusts the "relative priority" of the item in contrast to other items in the backlog.
Notes:
The ScrumWorks Pro My Tasks view provides a user-centric view of ScrumWorks Pro data. It is a light and convenient interface primarily intended for team members working on multiple teams and sprints.
The view is comprised of a list of all undone tasks assigned to you in current sprints: those that are ongoing or whose begin or end dates are within the last five days. The tasks are displayed in priority order as listed in the ScrumWorks Pro Desktop application.
Intended for users working on multiple teams, products, or sprints, the My Tasks view offers users a consolidated view of all tasks for which the logged in user is the designated Point Person across all products and sprints.
Once authenticated, the My Tasks view is always accessible by clicking the "My Tasks" navigation option in the page header.
Required Permission: View Task, for each listed product.
You can update the Hours Spent Today, Hours Remaining and the Status of your tasks from the My Tasks view. Once you have made changes to your tasks, clicking on the Update Tasks button will submit those changes.
Required Permission: Create/Edit/Delete Task, for each listed product where changes are to be made.
If you decide that you have made a change in error, you can click the Cancel button to revert any unsaved changes.
The Sprints view is designed primarily for Scrum team members working toward Sprint goals. The Sprints view employs a "task board" paradigm, where tasks are arrayed into columns representing task status. All tasks currently defined in the selected Sprint will appear in the task board, including tasks with a designated point person and those without a point person designation (unspecified).
The Sprints view is comprised of two main elements:
Because ScrumWorks Pro is a multi-user system, there is a possibility that the data represented within the Web Client is out of synchronization with changes made by other users. To compensate for this, the Sprint View will automatically poll the ScrumWorks Pro server for any updates to visible content every 30 seconds. Users can manually trigger a polling event by clicking the "Update" icon on the upper right of the interface.
If an update is detected the Web Client will silently refresh the visible data on your screen. The exception is if the data being updated is at risk of conflict due to an ongoing edit. If you are editing a task that simultaneously receives an update, a conflict notification message will appear at the bottom of the editor. It is up to you to decide whether to ignore the message and continue editing or close and re-open the editor to obtain the latest updates. If you save your changes after receiving an update notification, your changes will over-write the previous changes that were made. ScrumWorks will not over-write data in an open editor automatically.
All actions taken by Web Client users are immediately saved to the ScrumWorks Pro Server.
The "Sprints" view of the Web Client is a sprint centric view; it shows information relating to a specific sprint as selected by the user. The first step to selecting a sprint, however, is selecting the Product to which the Sprint belongs. Note, the list will contain those products for which the user has access.
To select a Product:
The "Sprint" view of the ScrumWorks Pro Web Client is a team member centric view; it shows information relating to a specific Sprint as selected by the user.
Required Permission: View Task.
To select a sprint:
The "Sprints" view of the ScrumWorks Pro Web Client provides a "task board" interface for selected sprints. Task boards are used at the team level to track the progress of product backlog items and tasks in sprints. The task board arrays all defined sprint tasks into status columns, indicating the overall progress of the sprint spatially.
Each row of the task board represents a product backlog item that has been committed to the sprint. The product backlog items are displayed in the far left column. Tasks related to each product backlog item are displayed in the appropriate task status columns to the right.
Changing the status of a task is as easy as dragging it from one column to the next. Task order within each status column can also be maintained via drag and drop.
The task board is designed to be used as you would index cards laid out on a table or pinned up on a wall. Each row represents a product backlog item and its associated tasks. The product backlog item title and description are displayed in the far left-hand column. Each of the product backlog item's tasks are displayed as individual cards, ordered within the status column that applies to each task. The header of each column lists the status and the number of tasks in that column.
The task board may be customized in the following way:
New tasks may be added from the Web Client.
Required Permission: Create, Edit, Delete Task.
To add a new task:When saved, the new task appears in the respective status column that was selected by the user, and "Not Started" by default.
Note: When task estimates are used, the first estimate entered and saved is displayed in the Original Estimate field. This figure is used in the desktop client to populate the Task Estimates vs. Actuals report, which is available when the Timesheets feature is enabled in Product Properties.
Required Permission: Create, Edit, Delete Task.
Tasks may be edited from the Web Client:When saved, the task may change appearance or location in the task board to reflect the edit. For example, if the status was changed, the task will move to the respective status column.
If the point person was edited to the current user, then the task color may change to match the rest of the user's tasks depending on highlight preferences. While your changes are being saved, the task will will be grayed out, and cannot be moved or opened for edit. Once this operation has completed, the task will again be available for changes.Users can add new comments to tasks during an "Add" or "Edit" operation. Once comments are added, they are visible in the Comments section of the "Edit Task" dialog. By default, the "Comments" section of the "Edit Task" dialog is closed, but shows the total comment count in collapsed form.
Required Permission: Create, Edit, Delete Task.
To view or add new commentsIn the task board, tasks are displayed in columns according to the task status ("Not Started", "Impeded", "In Progress", or "Done"). For example, all tasks that have not yet been started are listed in the "Not Started" column.
Required Permission: Create, Edit, Delete Task.
There are two ways to change task status:
Drag-and-drop methodWhen any one column for a single product backlog item contains more than one task, those tasks can be individually ranked within that status column. This rank is independent of the rank in the Desktop Client. Ranking tasks within the status columns on the Web Client will be maintained within the Web Client only, it will not effect the ranking in the Desktop Client.
Required Permission: Create, Edit, Delete Task.
Tasks can be moved between product backlog items. To move a task from one product backlog item to another:
Required Permission: Create, Edit, Delete Task.
Team members can volunteer as point person on tasks in the Web Client. Being a member of the team corresponding to the selected Sprint is a requirement. When a Team Member decides that she would like to make herself the point person on unassigned tasks or tasks currently associated to another point person, there are two methods to achieve this goal through the Web Client:
Required Permission: Create, Edit, Delete Task.
Edit Task Method:Users can update the time spent on individual tasks through the Web Client using the Edit Task dialog.
Required Permission: Create, Edit, Delete Task.
Historical entries may only be edited using the Desktop Client's Timesheet screen.
Tasks may be deleted from the Web Client through the Edit Task dialog. To delete a Task:
Required Permission: Create, Edit, Delete Task.
The user must have the "Mark product backlog item as Done" permission.
Users can add new comments to backlog items during an "Add" or "Edit" operation. Once comments are added, they are visible in the Comments section of the backlog item dialog. By default, the "Comments" section of the dialog is closed, but shows the total comment count in collapsed form.
Comments are listed in reverse chronological order with the most recent comment at top. Each comment includes the user that entered the comment and the time the comment was created on the server.
To view or add new commentsThe sprint burndown chart indicates the overall progress of the sprint. A "thumbnail" version of the sprint burndown chart is located at the top of task board, under the page header. Clicking the thumbnail will overlay the full sprint burndown chart on the task board. Both the thumbnail and full version are dynamically generated, so updating tasks will update the chart immediately.
Required Permission: View Task.
Sharing the sprint burndown chartThe Dashboard view allows quick selection and viewing of your existing web reports for the selected product.
To select a Product:
To select a Report:
The full page item editor allows you to edit all of the fields of a backlog item at once with out having to switch accordions or tabs as you would with the web client and desktop client.
To open the full page editor:
Note: Editing fields in the full page item editor requires the appropriate permissions. However, any user with product access rights can view backlog items in this fashion.