This article contains detailed explanations of the Work Items entity available in PPO. This entity is used on the Agile PPO Instance.
Work items form the product back-log. These work items are prepared for sprinting and are later planned on a specific sprint based on priority and other considerations. Because the work items are associated with a project, this can be used to further break up the backlog e.g. operations, development, specific applications or epics.
Next, the fields on the work items entity will be discussed per category. First up is the Work Item Information and the Work Item Classification categories, as can be seen below:
Category: Work Item Information
1.1.1 Project – Each work item is associated with a project. The project that you choose will be dependent on how you want to structure your product backlog. Typically, a work item will be associated with the generic Operations project, an application project (e.g. Application ABC: Minor Changes) or an epic (e.g. Application ABC: Search Functionality).
1.1.2 Title – Capture a descriptive title for the work item. It is important that you get this right as it is used extensively in reporting.
1.1.3 Description – This is a more detailed description of the work item. Over time, as the work item is refined, this description should be updated.
1.1.4 Solution – this is a brief description of what the team thinks the solution for the specific work item is. Once again, this should be refined and updated over time.
Category: Work Item Classification
1.1.5 Type – this categorises the work items into the following types: Enhancement Request, Generic, Incident, Operational Issue, Other and Software Bug.
1.1.6 Priority – this prioritises the work items into either being: Critical, High, Medium or Low.
1.1.7 Code Change Risk – this is a subjective measure of the risk associated with a work item. The risk being that the change will break the application or have other undesirable side effects.
1.1.8 Impact – this categorises the work item according to the following impacts: User Facing, Technical and Other.
Category: Work Item Planning
1.1.9 Sprint Key – if you want to link a work item to a sprint, the sprint key field needs to be captured. If the field is 0, it means that the work item has not yet been linked to a sprint and forms part of the product backlog.
1.1.10 Sprint Status – this is a calculated field that shows the status of the sprint that the work item is linked to. If the status is blank like in the example above, the item is not linked to a sprint, as previously mentioned.
1.1.11 Responsibility – this shows the person responsible for the work item in the sprint. This is the person that will be doing the work.
1.1.12 Estimated Hours – this indicates the estimated hours for completing the work item. This is usually captured when the work item is added but may be changed as the work item is refined.
1.1.13 Estimate to Complete – this number is updated daily by the person working on the work item, and should become less as the development of the work item is progressing.
1.1.14 Product Backlog Status – This is a calculated field and shows the status of the work item, with regards to the product back-log. The statuses are the following: Ready, Preparing, New and Parked (see the table further below).
Category: Work Item Management
1.1.15 Sprint Backlog Status – this is a calculated field that indicates the sprint back-log status of the work item. The statuses are the following: Backlog, To Do, Doing and Done. These statuses are also used on the Kanban board on the Scrum - Sprint Backlog dashboard, to also show the status of the work items that are currently part of a sprint and currently in development (see the table further below).
1.1.16 Status – when the work item is captured the applicable status needs to be selected. The table below shows the relationship between the status of the work item, Product Backlog Status and the Sprint Backlog Status.
If the status of the work item is changed to “Ready for Sprint” then the Sprint Key needs to be updated to reflect the sprint that the work item will form part of.
1.1.17 Assigned To – this is usually the same as the Responsible person except when it is in a review or QA status, in which case it will be the person responsible for that activity.
1.1.18 Action / Response – every time that the work item is updated, the reason for the update is captured here and gives an indication of what is required for the item to progress. Please note that this field is auto-cleared each time the work item is updated.
1.1.19 Deployment Date – this field only needs to be populated once the status of the work item is changed to “Deployed”.
1.1.20 Deployment Steps –the development team usually follows their normal deployment process. This field is only used to record special steps they required during the deployment of the work item and is not always populated.
1.1.21 Time Entry Hours – this is a calculated field which shows the actual hours captured for the work item, on the time entries maintenance page.
1.1.22 Variance – this is a calculated field that shows the difference between the Estimated Hours for the work item and the Time Entry Hours + Estimated Hours to complete fields on the work item.