ProjectTRACKER Help - Scrum

The ProjectTRACKER implements the Agile methodology Scrum. A Scrum project consists of a Program, which is decomposed into Epics, User Stories and Tasks which implement the User Story. A task might be broken down into smaller Activities, but due to the typical detailed “tasking out” of a user story this might be superfluous. For sure a program can contain also normal Tasks. To differentiate Scrum Tasks from normal tasks ProjectTRACKER uses 'S' as Top Level Group indicator. A typical User Story / Task view looks like:

Notes:

  • Only users with admin, team admin or project leader and “Scrum” access rights can see and use this functionality!
  • “Normal” tasks should not use 'S' as Top Level Group indicator!
  • Scrum tasks are also visible in the Tasks, Estimates and Schedule page, but it is not recommended to change any task fields there (e.g. the end time), as this could lead to strange effects in the Scrum page then!

Search User Story / Task

Task User Story / Task name filter.
Program Program name filter.
Task ID User Story / Task ID filter.
Task Group User Story / Task group filter.
Task Prio User Story / Task prio filter. Prio must be given in format: 1,2,3 …
Task Owner User Story / Task Owner filter.
Task Status Task Status filter.
Scrum Cycle / Year Scrum Cycle week / Year filter. Notes: Only tasks within the correct scrum cycle year are shown. The default year must be set, otherwise nothing is shown!
Grooming Status User Story / Task Grooming Status filter.
Show Inactive When set also all inactive, and normally hidden user stories / tasks are shown.
excel3.jpg Export to MS Excel sheet.
Opens the Reports page showing all reports including 8 in the report view.

User Story / Tasks Inline Report

The user story / tasks inline report with the name _Scrum Page Report is shown right to the Search User Story / Task form when defined by a user with “Report” rights.

User Story / Tasks Input Grid

ID1) Internal program ID. Clicking on the task ID will select only this user story / task.
Trend of the last change to task Effort or Story Points. Clicking on the icon will open the Task History / Trending.
Group2) Group name of the user story / task. See Group Format.
Prio3) Prio of the user story / task.
Program4) Name of the program associated to the user story / task. Note: The program name will be only shown in case no default program is selected.
Task Name5) Name of the epic / user story / task.
Clicking on the note icon will open the User Story / Task Description page. A blue icon indicates that there is a description available. A tool tip with the content of the description is shown as soon the mouse cursor will be moved over this field.
Scrum Cycle6)7) Scrum cycle week. Note: All tasks belonging to the user story Summary Group will be automatically assigned to the same scrum cycle week.
Effort(h)8) Planned effort for this task - see also Tasks.
Task Owner9) User Story / Task owner - if defined, users with “Own Task” right can change the user story / task content, even when not the record owner or in the group of the record owner.
Task Status10) User story / task status11). Note: For User Stories / Summary Tasks the task status shows the lowest status of all tasks belonging to the summary group.
Story Points12) Story points estimated for User Story. Note: Story Points can be defined only for User Stories (means lowest level summary task) where the corresponding tasks correctly belong to the User Story task group level - means all task groups are one level lower.
US Done13) User Story “done” indicator. Note: US Done checkbox is visible based on the “task done” condition14) of the associated User Story tasks. The US Done checkbox is also only visible if the corresponding tasks correctly belong to the User Story task group level - means all task groups are one level lower.
SP Done Shows Story Points “done” based on US Done checkbox.
Effort Done Shows the effort done from Efforts.
Effort Rem. Shows the remaining effort from Efforts. In case the task is done (remaining effort is 0) the Effort Rem. is shown in green color.
Active15) Set task to active / inactive. An inactive user story / task is not visible in other ProjectTRACKER pages, e.g. task selection lists. Inactive user story / tasks are also excluded from all effort calculations.
Copy Users with “Create” rights can copy or insert user stories / tasks depending on the User Story / Tasks Copy Options.
D/W Delete / Write indication. In case a check box is available you can delete the user story / task. When you move the mouse cursor over the field a tool tip shows the owner and creation date of this record.
Indicates the record is write protected. To still write to your own records choose another filter criteria to reduce the list to entries you are allowed to write.

Note: Clicking on the checkbox will set or reset the values in all lines. To overtake the settings you have to press the Update button!

User Story / Tasks Copy Options

Copy Tasks Copy User Story / task.
Copy Tasks+Alloc. Copy selected User Story / task and task allocations.
Copy Tasks+Alloc.+Year Copy selected User Story / task and task allocations. Task allocations will be moved to the current year setting. Note: The copy function exactly copies all fields of task. You have to modify the task dates and dependencies manually!
User Story / Task Templates List of User Story / task templates, which can be inserted below the current selected Copy task group level. Details see Task Templates.

Note: Only the Plan allocation values will be copied not the Curr. values.

User Story / Tasks Input Buttons

Update Store task entries.
Cancel Reload page without storing.

User Story / Task Description

Clicking on the icon will open the User Story / task description editor. As editor the FCK Editor is used. Press the help icon to get infos on how to use the FCK editor.

Here two examples for a user story and a task description:

User Story / Task Description Input

Task Owner User Story / Task owner - if defined, users with “Own Task” right can change the user story / task content, even when not the record owner or in the group of the record owner.
Grooming Status Grooming status.
Task Status User Story / Task status.
Default Activities This field shows “auto” activities assigned in the task description (see also Default Activities). Note: In case activities do not match activities belonging to the program or task activity group of this task, or the sum of activities is not 100% a warning in red is given.
Effort Best Case16) Best case effort estimation see “Software Estimation”17) page 106ff.
Effort Planned18) Most likely effort estimation see “Software Estimation”19) page 108ff.
Effort Worst Case20) Worst case effort estimation see “Software Estimation”21) page 106ff.
Expec. Case22) Is calculated according to Expected Case := (Effort Best Case + 4.0 * Effort Planned + Effort Worst Case) / 6.0 see “Software Estimation”23) page 109.

The values beside the Effort Best Case, Effort Planned and Effort Worst Case fields are extracted from the task description and can be copied to the effort fields via the Copy button. The Effort Deviation24) field is also extracted from the task description. The deviation value can be used in the Efforts page to correct the remaining efforts input. For details see Task Description Free Text Input.

Notes:

  • In case the Effort Planned is out of the range of Effort Best Case or Effort Worst Case a warning is given in the Expec. Case field.
  • The extracted Effort Best Case, Effort Planned and Effort Worst Case values are green in case they are identical to the saved effort values - otherwise they are red.

User Story / Task Description Input Buttons

Update Store description and efforts.
Copy Copy the efforts described in the text to the task effort fields. Note: Newly entered free text must be first saved via the Update button. The Copy button is only visible in case the task is not a summary task and task efforts are defined in the text!
Close Close description editor without saving.

References

25)Software Estimation - Demystifying the Black Art, Steve McConnell, Microsoft Press 2006

1) , 2) , 3) , 4) , 5) , 6) , 8) , 9) , 10) , 12) , 13) , 15) Clicking on the headline will also sort the column
7) Editable only for User Stories = Lowest Level Summary task
11) , 14) Configurable by the ProjectTRACKER PHP administrator
16) , 18) , 20) , 22) , 24) Not visible in case of a summary task
17) , 19) , 21) , 23) , 25) Ref Software Estimation
 
tracker/scrum.txt · Last modified: 2012/09/23 16:57 (external edit)
 
Except where otherwise noted, content on this wiki is licensed under the following license:(C) 2012 ProjectTRACKER - A. Welz. All rights reserved.
Recent changes RSS feed Donate Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki