Differences

This shows you the differences between two versions of the page.

Link to this comparison view

tracker:scrum [2012/08/28 15:02]
awelde created
tracker:scrum [2012/09/23 16:57] (current)
Line 1: Line 1:
-NEW - in work for version ​2.0!+====== ProjectTRACKER Help Scrum ====== 
 + 
 +The ProjectTRACKER implements the Agile methodology [[http://​en.wikipedia.org/​wiki/​Scrum_%28development%29|Scrum]]. A Scrum project consists of a [[tracker:​programs|Program]],​ which is decomposed into **Epics**, **User Stories** and **Tasks** which implement the User Story. A task might be broken down into smaller [[programs#​program_activities|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 [[tracker:​tasks|Tasks]]. To differentiate Scrum Tasks from normal tasks ProjectTRACKER uses '​S'​ as [[tracker:​naming#​group_name_notations|Top Level Group]] indicator. A typical User Story / Task view looks like: 
 + 
 +{{:​tracker:​tracker-scrum.png?​750}} 
 + 
 +//​**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 [[tracker:​naming#​group_name_notations|Top Level Group]] indicator! 
 +  * Scrum tasks are also visible ​in the [[tracker:​tasks|Tasks]],​ [[tracker:​estimates|Estimates]] and  [[tracker:​schedule|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. | 
 +^ {{:​tracker:​excel3.jpg}} | Export to MS Excel sheet. | 
 +^ {{:​tracker:​print-pdf.png|}} | Opens the [[tracker:​reports|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 ===== 
 + 
 +^ ID((Clicking on the headline will also sort the column)) | Internal program ID. Clicking on the task ID will select only this user story / task. | 
 +^ {{:​tracker:​trend-down2.png}}{{:​tracker:​trend-stable2.png}}{{:​tracker:​trend-up2.png}} | Trend of the last change to task **Effort** or **Story Points**. Clicking on the icon will open the [[tracker:​pm#​task_history_trending|Task History / Trending]]. | 
 +^ Group((Clicking on the headline will also sort the column)) | Group name of the user story / task. See [[naming#​group_format|Group Format]]. | 
 +^ Prio((Clicking on the headline will also sort the column)) | Prio of the user story / task. | 
 +^ Program((Clicking on the headline will also sort the column)) | 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 Name((Clicking on the headline will also sort the column)) | Name of the epic / user story / task. | 
 +^ {{tracker:​notes.png}}{{tracker:​notese.png}} | 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 Cycle((Clicking on the headline will also sort the column))((Editable only for User Stories = Lowest Level Summary task)) | Scrum cycle week. //​**Note:​**//​ All tasks belonging to the user story [[naming#​group_format|Summary Group]] will be automatically assigned to the same scrum cycle week. | 
 +^ Effort(h)((Clicking on the headline will also sort the column)) | Planned effort for this task - see also [[tracker:​tasks|Tasks]]. | 
 +^ Task Owner((Clicking on the headline will also sort the column)) | 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 Status((Clicking on the headline will also sort the column)) | User story / task status((Configurable by the ProjectTRACKER PHP administrator)). //​**Note:​**//​ For User Stories / Summary Tasks the task status shows the lowest status of all tasks belonging to the summary group. |  
 +^ Story Points((Clicking on the headline will also sort the column)) | 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 Done((Clicking on the headline will also sort the column)) | User Story "​done"​ indicator. //​**Note:​**//​ **US Done** checkbox is visible based on the "task done" condition((Configurable by the ProjectTRACKER PHP administrator)) 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 [[tracker:​efforts|Efforts]]. | 
 +^ Effort Rem. | Shows the remaining effort from [[tracker:​efforts|Efforts]]. In case the task is done (remaining effort is 0) the **Effort Rem.** is shown in green color. | 
 +^ Active((Clicking on the headline will also sort the column)) | 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. | 
 +^ {{:​tracker:​ronly2.png}} | 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 [[tracker:​pm#​task_templates|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 {{:​tracker:​notes.png}} icon will open the User Story / task description editor. As editor the [[http://​ckeditor.com|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:​ 
 + 
 +{{:​tracker:​tracker-scrum-descr-us.png?​500}} {{:​tracker:​tracker-scrum-descr.png?​500}} 
 + 
 +==== 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 [[tracker:​pm#​default_activities_via_task_description|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 Case((Not visible in case of a summary task))| Best case effort estimation see "​Software Estimation"​((Ref Software Estimation)) page 106ff. | 
 +^Effort Planned((Not visible in case of a summary task))| Most likely effort estimation see "​Software Estimation"​((Ref Software Estimation)) page 108ff. | 
 +^Effort Worst Case((Not visible in case of a summary task))| Worst case effort estimation see "​Software Estimation"​((Ref Software Estimation)) page 106ff. | 
 +^Expec. Case((Not visible in case of a summary task))| Is calculated according to //Expected Case// := (**Effort Best Case** + 4.0 * **Effort Planned** + **Effort Worst Case**) / 6.0 see "​Software Estimation"​((Ref Software Estimation)) 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 Deviation**((Not visible in case of a summary task)) field is also extracted from the task description. The deviation value can be used in the [[tracker:​efforts#​remaining_effort_in_combination_with_task_description|Efforts]] page to correct the remaining efforts input. For details see [[tracker:​pm#​detailed_planning_via_task_description_free_text_input|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 ===== 
 + 
 +((Ref Software Estimation))**Software Estimation - Demystifying the Black Art**, Steve McConnell, Microsoft Press 2006
  • tracker/scrum.1346158943.txt.gz
  • Last modified: 2012/08/28 15:02
  • by awelde