Differences between revisions 1 and 30 (spanning 29 versions)
⇤ ← Revision 1 as of 2008-12-17 11:03:26 →
Size: 37
Editor: EldZierau
Comment:
← Revision 30 as of 2010-08-16 10:24:09 → ⇥
Size: 4732
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
== Evaluation of a Tracker Issue == ## page was renamed from Process/Evaluate Tracker Issue
~-<<Action(edit)>>-~

The Evaluation of a Tracker Issue process contains [[#EvaluateTIDescription|Description]], [[#EvaluateTIPurpose|Purpose]], [[#EvaluateTIResponsible|Responsible]], [[#EvaluateTIMethod|Method]], [[#EvaluateTITime|Time]], [[#EvaluateTIInput|Input]] and [[#EvaluateTIOutput|Output]].

<<Anchor(EvaluateTIDescription)>>
'''~+Description+~'''<<BR>>
To have new tracker issues evaluated adn possibly fixed as quick as possible
When a tracker issue is created and assigned a module, it must be evaluated and possibly handled by the [[Process Role/Module Owner| Module Owner]]. Further more tracker issue that needs additional information must be followed up.

<<Anchor(EvaluateTIPurpose)>>
'''~+Purpose+~'''<<BR>>
To have new tracker issues evaluated adn possibly fixed as quick as possible

<<Anchor(EvaluateTIPurpose)>>
'''~+Responsible+~'''<<BR>>
[[Process Role/Module Owner| Module Owner]]. Please refer to [[Development#Staffing| Staffing]] for overview of modules, owners and backups.

<<Anchor(EvaluateTIMethod)>>
'''~+Method+~'''<<BR>>
Overview of tracker issue fields can be found on [[BugInfGuide/Fields| Tracker Issue Field Description]]
 1. Find tracker issues for module via the [[https://gforge.statsbiblioteket.dk/tracker/?group_id=7|trackers in GForge]]
 1. Check if the tracker issue is assigned to the right module.
 1. If the tracker issue shoud be assigned to another known module do following
    1. Change the 'Module' field to what seems the right module
    1. Change the 'Assigned To' field to the owner of this module.
    1. If appropriate make a comment on the reason of the change in the 'OR Attach A Comment' field.
 1. If the tracker issue shoud be assigned to another NOT known module do following
    1. Change the 'Module' field to "None"
    1. Change the 'Assigned To' field to the name of the [[Process Role/QA Coordinator| QA Coordinator]].
    1. If appropriate make a comment on the reason of the change in the 'OR Attach A Comment' field.

'''''Only proceed with issues for actual module'''''
 1. Set priority according to how important the tracker issue seem to be.
 1. If the priority is set to the highest priority (5) then contact [[Process Role/QA Coordinator| QA Coordinator]] who will take action according to the [[Process/Prioritization|Prioritization]] process.

'''''Only proceed with issues with priority is less than 5'''''
 1. If we currently do NOT have a code freeze at evaluation time
   1. If there is an easy solution to fix the tracker issue (guideline maximum 1 md.):
     1. Set the 'Status' field to "In Progress"
     1. Follow the [[Process/Implementation|Implementation]] process
   1. If there are a need for additional information before evaluation can be completed:
     1. Sent request for nedded information
     1. Set the 'Status' field to "Need Info"
     1. Write information about request of information in the 'OR Attach A Comment' field
   1. If there is a little more complex solution to fix the tracker issue:
     1. Make a description of how the tracker issue should be fixed in the 'OR Attach A Comment' field
     1. Write and estimate (with uncertaincy description if appropriate) of the fix in the 'OR Attach A Comment' field
   1. If the solution is complex:
     1. Make a description of creation of an assignement in the 'OR Attach A Comment' field
     1. Write and estimate (with uncertaincy description if appropriate) of the creation of such an assignment in the 'OR Attach A Comment' field
   1. Set the 'Status' field to "Evaluated"
 1. If we currently DO have a code freeze at evaluation time
   1. Evaluate if the tracker issue should be fixed before release.
   1. If it should be fixed before release then
     1. Contact [[Process Role/QA Coordinator| QA Coordinator]] and [[Process Role/Test Coordinator| Test Coordinator]].
   1. If it should NOT be fixed before release then
     1. Evaluate the tracker issue after codefreeze

<<Anchor(EvaluateTITime)>>
'''~+Time+~'''<<BR>>
Every time a new tracker issue is created.

The reaction time on evaluation of a tracker issue should be no more than a week.

All tracker issues must be evaluated or fixed before [[Process/Code Freeze|Code Freeze]].

<<Anchor(EvaluateTIInput)>>
'''~+Input+~'''<<BR>>
Tracker issue
 * that has been assigned to a specific module (set by creater of issue or in the [[Process/Monitoring_Trackers|Monitoring Trackers]] process)
 * that awaits additional information before evaluation can be completed

<<Anchor(EvaluateTIOutput)>>
'''~+Output+~'''<<BR>>
Evaluated or fix in progress of tracker issue

edit

The Evaluation of a Tracker Issue process contains Description, Purpose, Responsible, Method, Time, Input and Output.

Description
To have new tracker issues evaluated adn possibly fixed as quick as possible When a tracker issue is created and assigned a module, it must be evaluated and possibly handled by the Module Owner. Further more tracker issue that needs additional information must be followed up.

Purpose
To have new tracker issues evaluated adn possibly fixed as quick as possible

Responsible
Module Owner. Please refer to Staffing for overview of modules, owners and backups.

Method
Overview of tracker issue fields can be found on Tracker Issue Field Description

  1. Find tracker issues for module via the trackers in GForge

  2. Check if the tracker issue is assigned to the right module.
  3. If the tracker issue shoud be assigned to another known module do following
    1. Change the 'Module' field to what seems the right module
    2. Change the 'Assigned To' field to the owner of this module.
    3. If appropriate make a comment on the reason of the change in the 'OR Attach A Comment' field.
  4. If the tracker issue shoud be assigned to another NOT known module do following
    1. Change the 'Module' field to "None"

    2. Change the 'Assigned To' field to the name of the QA Coordinator.

    3. If appropriate make a comment on the reason of the change in the 'OR Attach A Comment' field.

Only proceed with issues for actual module

  1. Set priority according to how important the tracker issue seem to be.

  2. If the priority is set to the highest priority (5) then contact QA Coordinator who will take action according to the Prioritization process.

Only proceed with issues with priority is less than 5

  1. If we currently do NOT have a code freeze at evaluation time
    1. If there is an easy solution to fix the tracker issue (guideline maximum 1 md.):
      1. Set the 'Status' field to "In Progress"

      2. Follow the Implementation process

    2. If there are a need for additional information before evaluation can be completed:
      1. Sent request for nedded information
      2. Set the 'Status' field to "Need Info"
      3. Write information about request of information in the 'OR Attach A Comment' field
    3. If there is a little more complex solution to fix the tracker issue:
      1. Make a description of how the tracker issue should be fixed in the 'OR Attach A Comment' field
      2. Write and estimate (with uncertaincy description if appropriate) of the fix in the 'OR Attach A Comment' field
    4. If the solution is complex:
      1. Make a description of creation of an assignement in the 'OR Attach A Comment' field
      2. Write and estimate (with uncertaincy description if appropriate) of the creation of such an assignment in the 'OR Attach A Comment' field
    5. Set the 'Status' field to "Evaluated"
  2. If we currently DO have a code freeze at evaluation time
    1. Evaluate if the tracker issue should be fixed before release.
    2. If it should be fixed before release then

      1. Contact QA Coordinator and Test Coordinator.

    3. If it should NOT be fixed before release then
      1. Evaluate the tracker issue after codefreeze

Time
Every time a new tracker issue is created.

The reaction time on evaluation of a tracker issue should be no more than a week.

All tracker issues must be evaluated or fixed before Code Freeze.

Input
Tracker issue

  • that has been assigned to a specific module (set by creater of issue or in the Monitoring Trackers process)

  • that awaits additional information before evaluation can be completed

Output
Evaluated or fix in progress of tracker issue

Process/Evaluate Tracker Issue WithoutTitle (last edited 2010-08-16 10:24:09 by localhost)