New Internal Discovery Process

[cassie]

Hi @team

Following the finalisation of the Open edX community product review process, we’re revisiting and refining our internal discovery process. This work aims to improve collaboration between business, design, and development.

Please could everyone review the following pages:

• Project Workflow page
• Client Product Proposal page
  (This will replace the Discovery phase from the Epic management page. We’re aligning our terminology, i.e. Discovery, to the Open edX Platform terminology, i.e. Product Proposal).

Once reviewed by the entire team, I’ll add the new pages to the OpenCraft handbook.

I’ve read and acknowledged the processes outlined on the:

• Project Workflow Page
• Client Product Proposal Page

I’ve created a sub-task for everyone under this issue, bar Xavier, Ali and Tim, as they have already reviewed. Please try and complete this by the end of next sprint

[cassie]

Just a friendly ping to review this new process please @braden @jordan @Agrendalath @paulo @maxim @kshitij @kaustav @tecoholic @mtyaka @gabor

[kshitij (Kshitij Sobti)]

I understand the process changes but I wonder if thre is any advantage in now calling this the “product proposal process” instead of the “discovery process”, what do we get by changing the name? It will involve rewriting a lot of documentation, code, ideally renaming discovery duty etc. I understand that it is a term used by Open edX but needn’t be tied to that. We technically are open to working on other platforms so keeping out own distinct terminology seems okay to me.