:clipboard: Guidelines & Workflow for people contributing to our project(s) on GitHub. Please :star: to confirm you've read & understood! :white_check_mark:
86
stars
9
forks
source link
Required agreements with/information from PO *before* a project starts #107
We don't have these captured anywhere and are often quick to rush into projects (because decisions on moving ahead are usually made pretty last minute) without ensuring that all of the work that the Product Owner (PO) needs to do ahead of the start of a project has had adequate (if any) thought go into it.
As such, the POs are somewhat surprised when we ask them for 'all this information' once the project has begun. They need to be captured and importantly systematised.
What metrics do we need to capture in order to determine success for each of these content types and users? https://github.com/club-soda/club-soda-guide/issues/97 The key is to know at every step that we are building something people want and this is the only way to be sure of that
We don't have these captured anywhere and are often quick to rush into projects (because decisions on moving ahead are usually made pretty last minute) without ensuring that all of the work that the Product Owner (PO) needs to do ahead of the start of a project has had adequate (if any) thought go into it.
As such, the POs are somewhat surprised when we ask them for 'all this information' once the project has begun. They need to be captured and importantly systematised.
definition of donefor the project?successlook like for the project?successfor each of these content types and users? https://github.com/club-soda/club-soda-guide/issues/97 The key is to know at every step that we are building something people want and this is the only way to be sure of that