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.
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
0voters
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
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.
Where are we on this? I was looking for our latest Discovery document template for a task, then vaguely remembered that we had renamed and updated the process, but couldn’t find the new information in the Handbook.
@gabriel I had to defer this work due to the conference and client work. I asked if anyone wanted to pick up the tickets up, but I had no takers. It’s still on my radar but I have higher priorities unfortunately. I’d love to be able to get this finished!
Initially I wanted to roll this out incrementally but the new Project Workflow page has created a knock on effect, meaning we need all the content written before we make updates to the handbook.
To start, we need content collated from the current handbook and then restructured / rewritten. The two sections that need development attention are Development and Upstreaming. See this ticket description. If you’re interested I can create a task
