Differences

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

tracker:pm [2012/08/28 15:02]
awelde created
tracker:pm [2012/10/03 11:30] (current)
Line 1: Line 1:
-NEW - in work for version 2.0!+====== ProjectTRACKER Help - Project Management Best Practices / Curriculum ====== 
 + 
 +===== Software Project Management Techniques ===== 
 + 
 +ProjectTRACKER supports standard project planning and time / effort documentation techniques successfully used since more then 20 years of SW development. ProjectTRACKER also supports the Agile Scrum development methodology consisting of user stories and story point estimation techniques, and with this allows to close the gaps between Agile and Plan-driven concepts((Ref Balancing Agility and Discipline)). ProjectTRACKER in addition incorporates heuristic project scheduling and statistical estimation functions((Ref Software Estimation)) supporting Lean Six Sigma methodologies adapted to the Software development domain. 
 + 
 +A strong differentiator is that ProjectTRACKER does not force a special method or planning rigor, but allows to use different methods based on the program, project or business need((Ref Balancing Agility and Discipline)). 
 + 
 +The following table shows Software Project Management methods and planning rigor supported by the ProjectTRACKER: 
 + 
 +^ Method ^ Agile / Plan / Both ^  Planning\\ Effort / Rigor  ^ ProjectTRACKER Support ^ 
 +| Task / User Story Standardization / Templates |  Both  |  Low  | -> [[tracker:tasks|Tasks]]\\ -> [[tracker:scrum|Scrum]]\\ -> [[tracker:pm#task_templates|Task Templates]]\\ -> [[tracker:naming#group_name_notations|Group Name Notations]] | 
 +| Task planning / structuring |  Plan  |  Low  | -> [[tracker:tasks|Tasks]]\\ -> [[tracker:naming#group_name_notations|Group Name Notations]] | 
 +| Task time recording |  Both  |  Low  | -> [[tracker:efforts|Efforts]] | 
 +| Plan control / prediction |  Plan  |  Low  | -> [[tracker:tasks|Tasks]]\\ -> [[tracker:schedule|Schedule]]\\ -> [[tracker:reports-predefined|Reports]] | 
 +| Scope / Feature Creep, Task / User Story Trending |  Both  |  Low  | -> [[tracker:pm#task_history_trending|Task History / Trending]]\\ -> [[tracker:reports-predefined|Burn Down, Burn Up Charts]]  | 
 +| Team collaboration |  Both  |  Low  | -> [[tracker:efforts|Efforts]]\\ -> [[tracker:reports-predefined|Reports]]\\ -> [[tracker:reports-config|Wiki Update / Export]] | 
 +| Remaining task effort recording / calculation (TR_REMEFF_MANDATORY((Configurable by the ProjectTRACKER PHP administrator)) not set) |  Both  |  Low  | -> [[tracker:efforts|Efforts]] | 
 +| Epic / User Story / Story Point planning / structuring |  Agile  |  Low  | -> [[tracker:scrum|Scrum]]\\ -> [[tracker:naming#group_name_notations|Group Name Notations]] | 
 +| User Story Done tracking |  Agile  |  Low  | -> [[tracker:scrum|Scrum]]\\ -> [[tracker:reports-predefined|Burn Up Charts]] | 
 +| Best Case, Most Likely, Worst Case Effort Estimation((Ref Software Estimation)) |  Plan  |  Medium  | -> [[tracker:estimates|Estimates]] | 
 +| Resource planning |  Plan  |  Medium  | -> [[tracker:plan|Plan]] | 
 +| Activity recording |  Plan  |  High  | -> [[tracker:efforts|Efforts]]\\ -> [[tracker:programs#program_activities|Program Activities]]\\ -> [[tracker:pm#default_activities_via_task_description|Default Activities]] | 
 +| Remaining task effort recording (TR_REMEFF_MANDATORY((Configurable by the ProjectTRACKER PHP administrator)) set) |  Both  |  High  | -> [[tracker:efforts|Efforts]] | 
 +| Detailed Task planning |  Both  |  High  | -> [[tracker:tasks|Tasks]]\\ -> [[tracker:scrum|Scrum]]\\ -> [[tracker:pm#detailed_planning_via_task_description_free_text_input|Task Description Free Text Input]] | 
 + 
 +===== Task Import / Other Tools ===== 
 + 
 +There are very good "classical" Project Management, Time Accounting and Collaboration Tools available ProjectTRACKER is not competing against, but supports e.g. the initial planning via [[http://sourceforge.net/projects/openproj|OpenProj]] and allows then importing the results to ProjectTRACKER. The following import / exchange formats are supported: 
 + 
 +^ Supported Tool Types ^ Exchange format ^ ProjectTRACKER Support ^ Exchange Direction ^ 
 +| Spreadsheet | CSV | [[tracker:reports|Reports]] | ProjectTRACKER -> Tool | 
 +| Spreadsheet | CSV | [[tracker:auto#import_tasks_from_csv_list|Import CSV]] | Tool -> ProjectTRACKER | 
 +| Spreadsheet | CSV | {{:tracker:excel3.jpg}} MS Excel((All third party trademarks are the property of their respective owners)) Grid Export | ProjectTRACKER -> Tool | 
 +| Microsoft Project((All third party trademarks are the property of their respective owners)) | MS Project 2003 XML export format | [[tracker:auto#import_tasks_from_msproject_openproj|Import MS Project]] | Tool -> ProjectTRACKER | 
 +| OpenProj((All third party trademarks are the property of their respective owners)) | MS Project 2003 XML export format | [[tracker:auto#import_tasks_from_msproject_openproj|Import OpenProj]] | Tool -> ProjectTRACKER | 
 + 
 +===== Task History / Trending ===== 
 + 
 +The ProjectTRACKER supports a full change history on all effort and date changes to tasks with a daily granularity via retaining a so called **Task History**. Clicking on the task trend symbols {{:tracker:trend-down2.png}}{{:tracker:trend-stable2.png}}{{:tracker:trend-up2.png}} opens the Task History page, e.g.: 
 + 
 +{{:tracker:tracker-tasks-history.png?600}} 
 + 
 +The example above shows that the admin user has changed the Story Point effort on 18th Jan. Old value was //8// SPs. In the line above you see the new value //10// SPs (ProjectTRACKER stores always the old, non-zero value before the field is changed to the new value - this would be visible also in the current SP value in the User Story). On 27th of Jan the User Story was set to //"Done"// by the admin user. 
 + 
 +With the Task History, changes in the Task or User Story effort baseline can be simply detected and analysed via the ProjectTRACKER [[tracker:reports-predefined|Burn Down, Burn Up Charts]], like this one: 
 + 
 +{{:tracker:tracker-reports-burnup-sp.png?500}}   
 + 
 +In the example above Story Points have increased around mid of January (details could be derived by the Task History above) with the effect that most probably the target date is not feasible anymore as the average velocity is not hitting the red, dotted Planned Effort line at the Plan Date. 
 + 
 +The trend symbols {{:tracker:trend-down2.png}}{{:tracker:trend-stable2.png}}{{:tracker:trend-up2.png}} are shown in the grid displays of the [[tracker:tasks|Tasks]], [[tracker:scrum|Scrum]], [[tracker:estimates|Estimates]] and [[tracker:schedule|Schedule]] pages. The trend symbol gives a quick indication of the effort trend: 
 + 
 +|{{:tracker:trend-down2.png}}|Effort has decreased after the last update.| 
 +|{{:tracker:trend-stable2.png}}|Effort has not changed.| 
 +|{{:tracker:trend-up2.png}}|Effort has increased after the last update.| 
 + 
 +//**Notes:**// 
 + 
 +  * The Task History / Trending must be activated via the TR_TASK_TRENDING((Configurable by the ProjectTRACKER PHP administrator)) flag! 
 +  * The behaviour of changes to the Task or User Story effort baseline are defined via the TR_TASK_PLAN_VALIDITY((Configurable by the ProjectTRACKER PHP administrator)) flag! 
 + 
 +===== Detailed Planning via Task Description Free Text Input ===== 
 + 
 +To allow a very detailed, free text task definition in combination with the effort rationales, the ProjectTRACKER extracts / parses effort estimations from the [[tracker:tasks#task_description|Task]] description text. It is recommended to describe the detailed efforts in a tabular form e.g. via the [[http://ckeditor.com|FCK Editor]] table function: 
 + 
 +^  **Task A**  ^^^^^^^^^ 
 +| **Description** | Bla Bla Bla ||||||||| 
 +| **Risks** | Bla Bla Bla ||||||||| 
 +| **Constraints** | Bla Bla Bla ||||||||| 
 +| **...** | ... ||||||||| 
 +| **Task Steps to do** | **Description** | **Responsible** | **Planned Effort** | **Min. Effort** | **Max. Effort** | **Risks/Issues identified** | **Effort Deviations** | ... | 
 +| Task A Step 1 | Bla Bla Bla | Mr. X |  10 PD |  8- PD |  12+ PD | Risk UVW |  +10! PH | ... | 
 +| Task A Step 2 | Bla Bla Bla | Mr. Y |  33 PH |  22- PH |  44+ PH | Risk XYZ | | ... | 
 +| Task A Step 3 | Bla Bla Bla | Mr. X |  11.5 PD |  10- PD |  15.5+ PD | Risk ABC |  -2.5! PD | ... | 
 +| Task A Step 4 | Bla Bla Bla | Mr. X |  0:30 PH |  0:10- PH |  0:40+ PH | Risk 987 |  +0:30! PH | ... | 
 + 
 +Efforts are collected from all numbers in the format //123 PD// (in Person Days, with 8 hours a day) or //123 PH// (in Person Hours). Hours can be also entered in the format //12:34//. A '-' after the number indicates a **Best Case Effort**, a '+' indicates a **Worst Case Effort** and a '!' indicates a [[tracker:efforts#remaining_effort_in_combination_with_task_description|Effort Deviation]]. 
 + 
 +//**Note:**// Be aware that small typos in the task descriptions (e.g. //8 -PD//) will make the extracted efforts incorrect - so better double check! 
 + 
 +===== Default Activities via Task Description ===== 
 + 
 +To reduce the efforts for the ProjectTRACKER user to record [[tracker:programs#program_activities|Program Activities]], matching activities could be set by default in the [[tracker:tasks#task_description|Task]] description text, e.g. 100% verification via the text //##150 Verification Testing<nowiki>%%</nowiki>100##//. This is very usefull when the Tasks strucuture reflects already activities, e.g. Scrum "tasking out"s are typically a good match to activity sctructures (see also the examples in [[tracker:pm#example_template_tasks|Task Templates]]). 
 + 
 +===== Task Templates ===== 
 + 
 +Task Templates are tasks with the [[tracker:naming#group_format|Top Level Group]] letter 'T'((Configurable by the ProjectTRACKER PHP administrator)). They can be inserted at any position via the [[tracker:tasks#tasks_copy_options|Task Copy Option]]. Template tasks can be freely defined by everyone who can create and edit new tasks. The ProjectTRACKER example (see [[tracker:admin#projecttracker_quick_demo_setup|ProjectTRACKER Quick Demo Setup]]) contains e.g. the following templates: 
 + 
 + 
 + 
 +==== Example Template Tasks ====  
 + 
 +^**ID**^**Grp**^**Task**^**Description**|| 
 +|881|T01#|Task Template|<html><table cellspacing="1" cellpadding="1" border="1"> <tbody> <tr> <td bgcolor="#cccccc"><strong>Task Title</strong></td> <td colspan="8"> </td> </tr> <tr> <td bgcolor="#cccccc"><strong>Description</strong></td> <td colspan="8"> </td> </tr> <tr> <td bgcolor="#cccccc"><strong>Risks / Issues</strong></td> <td colspan="8"> </td> </tr> <tr> <td bgcolor="#cccccc"><strong>Constraints</strong></td> <td colspan="8"> </td> </tr> <tr> <td bgcolor="#cccccc"><strong>Default Activities</strong></td> <td colspan="8"> e.g. ##123 XYZ%%100##</td> </tr> <tr> <td bgcolor="#cccccc"><strong>Sub-Tasks</strong></td> <td bgcolor="#cccccc"><strong>Description</strong></td> <td bgcolor="#cccccc"><strong>Subtask Responsible</strong></td> <td bgcolor="#cccccc"><strong>Planned Effort</strong></td> <td bgcolor="#cccccc"><strong>Min. Effort</strong></td> <td bgcolor="#cccccc"><strong>Max. Effort</strong></td> <td bgcolor="#cccccc"><strong>Effort Deviation</strong></td> <td bgcolor="#cccccc"><strong>Subtask Status</strong></td> <td bgcolor="#cccccc"><strong>Comments</strong></td> </tr> <tr> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> e.g. OPEN, WIP, DONE</td> <td> </td> </tr> <tr> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> </tr> <tr> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> </tr> <tr> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> </tr> <tr> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> </tr> <tr> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> </tr> <tr> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> </tr> </tbody> </table> <p><em>Note: Task Efforts, Owner, Status see relevant ProjectTRACKER Task fields</em></p></html>| 
 +|896|T02##|User Story Template|<html><table cellspacing="1" cellpadding="1" border="1"> <tbody> <tr> <td bgcolor="#cccccc"><strong>User Story Name</strong></td> <td> </td> </tr> <tr> <td bgcolor="#cccccc"><strong>User Story Definition</strong></td> <td>As &lt;type of user&gt; I want &lt;what&gt; so that &lt;why&gt;</td> </tr> <tr> <td bgcolor="#cccccc"><strong>Risks / Issues</strong></td> <td>e.g. Risks / Issues discussed in Grooming session</td> </tr> <tr> <td bgcolor="#cccccc"><strong>User Story Type</strong></td> <td>e.g. Epic, Spike, Verification, Validation, Defect, &lt;functional area&gt;</td> </tr> <tr> <td bgcolor="#cccccc"><strong>Pre-conditions</strong></td> <td>e.g. Conditions necessary to start working on the user story</td> </tr> <tr> <td bgcolor="#cccccc"><strong>Predecessors</strong></td> <td>e.g. User Stories needed before staring user story</td> </tr> <tr> <td bgcolor="#cccccc"><strong>Successors</strong></td> <td>e.g. User Stories needed after implementing the user story</td> </tr> </tbody> </table> <p><em>Notes: </em></p> <ul> <li><em>User Story Grooming Status, Completion Status, Story point effort, Owner see relevant ProjectTRACKER Task fields</em></li> <li><em>User Stories should be checked for <strong>I</strong>: Independent, <strong>N:</strong> Negotiable, <strong>V</strong>: Valuable, <strong>E</strong>: Estimable, <strong>S</strong>: Small, <strong>T</strong>:Testable</em></li> </ul></html>| 
 +|915|T03##|Sprint Task Template|<html><table cellspacing="1" cellpadding="1" border="1"> <tbody> <tr> <td bgcolor="#cccccc"><strong>Description</strong></td> <td colspan="8">e.g. Document SW Design requirements</td> </tr> <tr> <td bgcolor="#cccccc"><strong>Risks / Issues</strong></td> <td colspan="8">e.g. Issues / Risks identified during the task out / planning sessions</td> </tr> <tr> <td bgcolor="#cccccc"><strong>Default Activities</strong></td> <td colspan="8">e.g. ##123 XYZ%%100##</td> </tr> </tbody> </table> <p><em>Note: Task Efforts, Owner, Status see relevant ProjectTRACKER Task fields</em></p></html>| 
 +|908|T04##.|.User Story + Task Out Template|<html><table cellspacing="1" cellpadding="1" border="1"> <tbody> <tr> <td bgcolor="#cccccc"><strong>User Story Name</strong></td> <td> </td> </tr> <tr> <td bgcolor="#cccccc"><strong>User Story Definition</strong></td> <td>As &lt;type of user&gt; I want &lt;what&gt; so that &lt;why&gt;</td> </tr> <tr> <td bgcolor="#cccccc"><strong>Risks / Issues</strong></td> <td>e.g. Risks / Issues discussed in Grooming session</td> </tr> <tr> <td bgcolor="#cccccc"><strong>User Story Type</strong></td> <td>e.g. Epic, Spike, Verification, Validation, Defect, &lt;functional area&gt;</td> </tr> <tr> <td bgcolor="#cccccc"><strong>Pre-conditions</strong></td> <td>e.g. Conditions necessary to start working on the user story</td> </tr> <tr> <td bgcolor="#cccccc"><strong>Predecessors</strong></td> <td>e.g. User Stories needed before staring user story</td> </tr> <tr> <td bgcolor="#cccccc"><strong>Successors</strong></td> <td>e.g. User Stories needed after implementing the user story</td> </tr> </tbody> </table> <p><em>Notes: </em></p> <ul> <li><em>User Story Grooming Status, Completion Status, Story point effort, Owner see relevant ProjectTRACKER Task fields</em></li> <li><em>User Stories should be checked for <strong>I</strong>: Independent, <strong>N:</strong> Negotiable, <strong>V</strong>: Valuable, <strong>E</strong>: Estimable, <strong>S</strong>: Small, <strong>T</strong>:Testable</em></li> </ul></html>| 
 +|909|T04##1|User Requirements|<html><table cellspacing="1" cellpadding="1" border="1"> <tbody> <tr> <td bgcolor="#cccccc"><strong>Description</strong></td> <td colspan="8">e.g. Document user / customer requirements </td> </tr> <tr> <td bgcolor="#cccccc"><strong>Risks / Issues</strong></td> <td colspan="8">e.g. Issues / Risks identified during the task out / planning sessions</td> </tr> <tr> <td bgcolor="#cccccc"><strong>Default Activities</strong></td> <td colspan="8">##110 User Requirements%%100##</td> </tr> </tbody> </table> <p><em>Note: Task Efforts, Owner, Status see relevant ProjectTRACKER Task fields</em></p></html>| 
 +|910|T04##2|SW Requirements|<html><table cellspacing="1" cellpadding="1" border="1"> <tbody> <tr> <td bgcolor="#cccccc"><strong>Description</strong></td> <td colspan="8">e.g. Document SW requirements </td> </tr> <tr> <td bgcolor="#cccccc"><strong>Risks / Issues</strong></td> <td colspan="8">e.g. Issues / Risks identified during the task out / planning sessions</td> </tr> <tr> <td bgcolor="#cccccc"><strong>Default Activities</strong></td> <td colspan="8">##120 System / Software Requirements%%100##</td> </tr> </tbody> </table> <p><em>Note: Task Efforts, Owner, Status see relevant ProjectTRACKER Task fields</em></p></html>| 
 +|911|T04##3|Risk Assessment|<html><table cellspacing="1" cellpadding="1" border="1"> <tbody> <tr> <td bgcolor="#cccccc"><strong>Description</strong></td> <td colspan="8">e.g. Perform draft risk assessment</td> </tr> <tr> <td bgcolor="#cccccc"><strong>Risks / Issues</strong></td> <td colspan="8">e.g. Issues / Risks identified during the task out / planning sessions</td> </tr> <tr> <td bgcolor="#cccccc"><strong>Default Activities</strong></td> <td colspan="8">##210 Formalization%%100##</td> </tr> </tbody> </table> <p><em>Note: Task Efforts, Owner, Status see relevant ProjectTRACKER Task fields</em></p></html>| 
 +|912|T04##4|Technical Design Reviews|<html><table cellspacing="1" cellpadding="1" border="1"> <tbody> <tr> <td bgcolor="#cccccc"><strong>Description</strong></td> <td colspan="8">e.g. Perform draft technical design review</td> </tr> <tr> <td bgcolor="#cccccc"><strong>Risks / Issues</strong></td> <td colspan="8">e.g. Issues / Risks identified during the task out / planning sessions</td> </tr> <tr> <td bgcolor="#cccccc"><strong>Default Activities</strong></td> <td colspan="8">##130 Design%%100##</td> </tr> </tbody> </table> <p><em>Note: Task Efforts, Owner, Status see relevant ProjectTRACKER Task fields</em></p></html>| 
 +|914|T04##5|SW Design|<html><table cellspacing="1" cellpadding="1" border="1"> <tbody> <tr> <td bgcolor="#cccccc"><strong>Description</strong></td> <td colspan="8">e.g. Document SW Design requirements </td> </tr> <tr> <td bgcolor="#cccccc"><strong>Risks / Issues</strong></td> <td colspan="8">e.g. Issues / Risks identified during the task out / planning sessions</td> </tr> <tr> <td bgcolor="#cccccc"><strong>Default Activities</strong></td> <td colspan="8">##130 Design%%100##</td> </tr> </tbody> </table> <p><em>Note: Task Efforts, Owner, Status see relevant ProjectTRACKER Task fields</em></p></html>| 
 +|916|T04##6|Implement Code|<html><table cellspacing="1" cellpadding="1" border="1"> <tbody> <tr> <td bgcolor="#cccccc"><strong>Description</strong></td> <td colspan="8">e.g. Implement code</td> </tr> <tr> <td bgcolor="#cccccc"><strong>Risks / Issues</strong></td> <td colspan="8">e.g. Issues / Risks identified during the task out / planning sessions</td> </tr> <tr> <td bgcolor="#cccccc"><strong>Default Activities</strong></td> <td colspan="8">##140 Implementation%%100##</td> </tr> </tbody> </table> <p><em>Note: Task Efforts, Owner, Status see relevant ProjectTRACKER Task fields</em></p></html>| 
 +|917|T04##7|Unit Testing|<html><table cellspacing="1" cellpadding="1" border="1"> <tbody> <tr> <td bgcolor="#cccccc"><strong>Description</strong></td> <td colspan="8">e.g. Unit test + code review + static code analysis + check-in</td> </tr> <tr> <td bgcolor="#cccccc"><strong>Risks / Issues</strong></td> <td colspan="8">e.g. Issues / Risks identified during the task out / planning sessions</td> </tr> <tr> <td bgcolor="#cccccc"><strong>Default Activities</strong></td> <td colspan="8">##150 Verification Testing%%100##</td> </tr> </tbody> </table> <p><em>Note: Task Efforts, Owner, Status see relevant ProjectTRACKER Task fields</em></p></html>| 
 +|918|T04##8|Verification Testing|<html><table cellspacing="1" cellpadding="1" border="1"> <tbody> <tr> <td bgcolor="#cccccc"><strong>Description</strong></td> <td colspan="8">e.g.: Verification scope,  test cases cover SW and Detailed Design Requirements and test cases successfully executed</td> </tr> <tr> <td bgcolor="#cccccc"><strong>Risks / Issues</strong></td> <td colspan="8">e.g. Issues / Risks identified during the task out / planning sessions</td> </tr> <tr> <td bgcolor="#cccccc"><strong>Default Activities</strong></td> <td colspan="8">##150 Verification Testing%%100##</td> </tr> </tbody> </table> <p><em>Note: Task Efforts, Owner, Status see relevant ProjectTRACKER Task fields</em></p></html>| 
 +|922|T04##9|Validation Testing|<html><table cellspacing="1" cellpadding="1" border="1"> <tbody> <tr> <td bgcolor="#cccccc"><strong>Description</strong></td> <td colspan="8">e.g.: Validation scope,  test cases cover User / Customer Requirements and test cases successfully executed</td> </tr> <tr> <td bgcolor="#cccccc"><strong>Risks / Issues</strong></td> <td colspan="8">e.g. Issues / Risks identified during the task out / planning sessions</td> </tr> <tr> <td bgcolor="#cccccc"><strong>Default Activities</strong></td> <td colspan="8">##160 Validation Testing%%100##</td> </tr> </tbody> </table> <p><em>Note: Task Efforts, Owner, Status see relevant ProjectTRACKER Task fields</em></p></html>| 
 +|920|T04##A|Manuals / Instructions|<html><table cellspacing="1" cellpadding="1" border="1"> <tbody> <tr> <td bgcolor="#cccccc"><strong>Description</strong></td> <td colspan="8">e.g.: Update manual / install / readme / troubleshooting instructions</td> </tr> <tr> <td bgcolor="#cccccc"><strong>Risks / Issues</strong></td> <td colspan="8">e.g. Issues / Risks identified during the task out / planning sessions</td> </tr> <tr> <td bgcolor="#cccccc"><strong>Default Activities</strong></td> <td colspan="8">##190 Manuals / Localization%%100##</td> </tr> </tbody> </table> <p><em>Note: Task Efforts, Owner, Status see relevant ProjectTRACKER Task fields</em></p></html>| 
 +|919|T04##B|Customer feedback|<html><table cellspacing="1" cellpadding="1" border="1"> <tbody> <tr> <td bgcolor="#cccccc"><strong>Description</strong></td> <td colspan="8">e.g.: Customer feedback scheduled, customer feedback done</td> </tr> <tr> <td bgcolor="#cccccc"><strong>Risks / Issues</strong></td> <td colspan="8">e.g. Issues / Risks identified during the task out / planning sessions</td> </tr> <tr> <td bgcolor="#cccccc"><strong>Default Activities</strong></td> <td colspan="8">##230 Rollout Support%%100##</td> </tr> </tbody> </table> <p><em>Note: Task Efforts, Owner, Status see relevant ProjectTRACKER Task fields</em></p></html>| 
 + 
 +==== Task Templates Inheritance ==== 
 + 
 +When inserting task template via the [[tracker:tasks#tasks_copy_options|Task Copy Option]] the parameters "program ID", "task owner" and "task active" are inherited from the checked "copy" task. The parameters "task group", "task prio", "task name", "task effort planned", "task effort best case", "task effort worst case", "task story points", "task status 1", "task status 2", "task time box" and  "task description" are copied from the template task. This allows quick assignments of task owners to the inserted template tasks and also allows the use of generic estimation templates with efforts already included as a guideline for the estimation process, e.g.: 
 + 
 +  * T01 Small Size User Story ~ 1SP 
 +    * T011 Task 1 
 +    * ... 
 +  * T02 Medium Small Size User Story ~ 2SP 
 +    * T021 Task 1 
 +    * ... 
 +  * T03 Medium Size User Story ~ 5SP 
 +    * T031 Task 1 
 +    * ... 
 + 
 +===== References ===== 
 + 
 +  * ((Ref Software Estimation))**Software Estimation - Demystifying the Black Art**, Steve McConnell, Microsoft Press 2006 
 +  * ((Ref Balancing Agility and Discipline))**Balancing Agility and Discipline - A Guide for the Perplexed**, Barry Boehm, Richard Turner, Addison Wesley 2012 
 + 
 
tracker/pm.1346158920.txt.gz · Last modified: 2012/08/28 15:02 by awelde
 
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