Project planning and meeting ceremonies

Story Task Decomposition

Perform the following actions for each front and back-end sections of the feature:

1. Read the user story and acceptance criteria
   1. Identify any missing details that were not identified in clarification.
   2. Identify Project
2. Identify what code will be impacted
   1. Minimum: Identify feature entry point (controller and or endpoint)
   2. Maximum: Method (or class)
3. Identify test scenarios
   1. Identify the amount of data should be mocked (this can be a time consuming endeavour and should be considered carefully for time estimates)
4. Evaluate that all acceptance criteria has been covered.
   1. Adjust for any missed requirements.
5. Identify any actions required after deployment.

Ongoing for all tasks: Throughout the process ensure that any requirements that are not possible/practical are raised, this may lead to the requirements being too large and deserves its own story or it not feasible due to some identified constraint. This should be raised with the Product Owner through a conversation in the discussion of the story. It is essential that the developers performing the decomposition perform the due diligence to qualify their findings and propose any available solutions that could fulfil some or all of the requiement.