It has been raised a few times in maintainer calls and other calls that we don’t collectively as a software/product team (product, design, development and adopters) scope the cost in both time and effort terms as well as financially very well before undertaking a significant feature build.
This proposal is for a ‘tool’ (in the form of a collaborative spreadsheet) we can test and implement if we find it useful. This tool is a ‘feasibility review’ process within a spreadsheet template for the functions (product, design, development and adopters) to scope out complexity, time and costs associated with these build before we undertake the higher effort discovery tasks associated with Hypha feature builds.
Goal: To have a way to asynchronously cross communicate effort and cost of large scale feature builds in an open and clear way possibly leveraging a template that is open and replicable as well as being inclusive of adopters time and skills. There is an opportunity to have a video call synchronously to clarify or discuss any depth and detail that rises from the form.
Outcome: Feasibility reviews for each large scale feature build that can be open and iterative.
Please see a spreadsheet here: Feasibility Review Template - Google Sheets
(it’s open for editing and commenting but if you want to make direct feedback on the spreadsheet please use comments first. I do have a back up spreadsheet if anyone deletes anything by accident )
Do you have any critical concerns about adopting the proposal?
Are there any clarifying questions you all might have?
Any quick reactions to the proposal above (e.g. good, feels weird, I don’t understand etc.)