a. Creation

i. Who:

  • Project managers or account executives

ii. When:

  • As DBSs are created

iii. How:

  • If a DBS does not require much work create one WTI.  If it is a large area of work, split the work into WTIs.
  • A WTI should represent a distinct chunk of work.  A WTI cannot include work on more than one project or task type, but this should never arise as a DBS should not either.  But work might be split on the basis of:

    • being required at different times, or being of differing priorities (eg, top priority output, medium priority output, etc)
    • being estimated separately if this is how it has been done in the DBS
    • being likely to be completed in discrete steps, and so to be in testing or to be with the client for approval at different times

  • Conversely, remember that WTIs are used to a) invoice, so it is easier if work that will be invoiced all at once is on one WTI; and b) to provide management information on how long things take us, so it is easier if work that relates to one thing is all on WTI.  Similarly, if a software change job also involves some error fixing, it should still all be one WTI; and if a WTI is closed but corrections need to be done, re-open the WTI rather than starting a new one.

b. Details

Follow the following procedure:
  • Ask for a new WTI and this will generate the number for you when its saved.
  • Enter a title (for your purposes, but one that is appropriate for clients also) and any client reference number.
  • Select the project (should be set up already, before DBSs are written; these are client-specific, and based on timing or subject, but should not be set up separately for every Task).
  • Select the task type (functional area of the system not site specific), and DBS as appropriate.
  • Enter the date delivery is required (after all QA etc has been done).
  • Enter estimate details from the DTS, if there is one, or from the DBS.
  • Enter the type:  use Software Change if it involves any new development and Error & Software Change if there is bug-fixing as well; use Error if it is only a bug report; and use User Error if it is.  Type is just a classification, not an indicator of severity or when the work gets done.
  • Enter the priority:  this represents the severity of the problem and should range from Low to High at present; it does not indicate when work will be done (this is done with the Date field).
  • Enter the status:  this represents the processing stage or the department it is with.

> Top <