Basic Work Item Fields – description.

As I promised in the previous post, below you can find the description of all fields that come to TFS Work Item from our local system RRP. Let’s call TFS Work Item that comes from RRP in one word – Task.

  • Title – short name of the work item.
  • RRP Number – internal number of the task from RRP system.
  • RRP Created By, RRP Created Date, Close Date – who and when has created the task and when it was closed.
  • Request Type – we use the following (in TFS they are different Work Items, but as in RRP the type of the task can be changed we decided to unite them also in one Work Item):
    • CR – Change Request: that is change of the existence functionality.
    • DE – Date Edit: direct change of data in database.
    • FS – Functional Support: some researches for business, some data upload – usually requests with this type, does not affect code or data.
    • HD – Bug. No additional comments )))
    • IR – Internal Requests: internal IT activities that does not directly touch business activities. E.g. optimization activities, planning, code review etc.
  • Approver/FAM – CR and DE must be approved by Business Process Owners (BPO), so this field contains name of the approver.
  • Assigned to – the developer of the work item.
  • Priority – we use four priorities: Low – 1, Medium – 2, High – 3, Critical – 4.
  • State – we use the following states:
    • Registered not analyzed – the ticket was just created.
    • New RFC, not yet accepted – for CR and DE this status means that it was send to the BPO for approve.
    • RFC Accepted, not analyzed – the task was accepted by BPO, but not analyzed by IT manager.
    • Rough Analysis Finished – the task was fully analyzed and hours planned  were filled for it.
    • Started – the developer is working on the request
    • Finished – the task is finished and waiting code review or is already sent to business for test.
    • Tested – the task was tested by business and is prepared for deployment.
    • Deployed (Closed) – the task was successfully implemented into production.
    • Pending – work is on hold.
    • Cancelled – clear state, I hope )))
  • Planned date (is Finished date in TFS) – date when the work item must be finished.
  • Hours Planned, Hours Left, Hours Done – are Baseline work, Remaining Work and Completed Work in TFS.
  • Area Path – as we have several applications developed in one Team Project we use this field to identify to which application Work Item is referred.
  • Iteration Path – we use it as it must be in TFS: to mark different iteration cycles of active projects.
  • BU/RU/Projects – business unit of task requester.
  • Pending Type – we use the following types:
    • Approver – some of steps of the task must be additionally approved.
    • Expert – developer does not understand how to do the task.
    • Maintenance – developer is busy solving other tasks, or is out, or server is down )))
    • User – waiting for reply from the task requester.
    • RootCauseAnalysis – additional work on IT side is required (e.g. writing of technical design).
    • FrozenByBusiness – business stops work on the task.
    • Deadline – this date is set in RRP by business and shows till what date business wants this task to be finished.

Добавить комментарий

Ваш адрес email не будет опубликован.