:clipboard: Guidelines & Workflow for people contributing to our project(s) on GitHub. Please :star: to confirm you've read & understood! :white_check_mark:
At the end of a project, there are a number of actions that need to be carried out to ensure the project is complete. These are not tracked anywhere as has recently been brought to my attention π±π
As part of https://github.com/dwyl/hq/issues/434, these need to be added to this repository to ensure we know that the project is complete and the correct information has been captured.
[ ] Definition of done for the project has been achieved and confirmed by the Product Owner (+ all agreed scope is in the 'Done' column of the Github Project)
[ ] The project's goal has been achieved
[ ] Has this/can this be captured in any way in the project documentation? e.g. results from user testing & OMTM reviewed
[ ] Understand whether the metrics are being reviewed and point POs to additional resources on how to better utilise these
[ ] Capture these in a systematic way via documentation
[ ] Automated follow up to understand if decisions have been made based on data and user testing since project phase's conclusion
[ ] Send end-of-project questionnaire to PO (we need a better way of capturing/communicating the results of this than we have currently)
[ ] SLA to be discussed and agreed one way or the other
At the end of a project, there are a number of actions that need to be carried out to ensure the project is complete. These are not tracked anywhere as has recently been brought to my attention π±π
As part of https://github.com/dwyl/hq/issues/434, these need to be added to this repository to ensure we know that the project is complete and the correct information has been captured.