Core Platform Team/PET Work Processes/PET Task Criteria

Description
Tasks should have clear concise description that should be comprehendible by another Engineer with domain knowledge but who did not create the task. They should describe a single unit of work.

Acceptance Criteria
The task should contain a clear set of criteria that identify the state requirements to consider the tasks completed.

Testing Criteria
The task should contain a clear set of criteria that explain how it can be tested to ensure that it meets the acceptance criteria.

Prioritisation
Tasks should have a clear priority to ensure that the work that has the greatest impact on progressing our goals or meeting deliverables. Priority determines the ordering by which tasks will be completed.

Priority is determined collaboratively but is owned and directed primarily by the Product Manager.

Sizing/Estimation
Tasks are estimated based on the Fibonacci Estimation Scale. The goal is to divide tasks into clear buckets that reflect their complexity.

Complexity is a combination of difficulty in completing the task, dependencies on other teams or work, amount of work required and technical complexity.

Tasks that have very high scores in complexity should be considered for conversion to epics and decomposed into appropriate subtasks of more manageable size.

Sizing should be done by Engineers in collaboration with EM/PM.