Valueflows' "value proposition" to developers
Created by: simontegg
What does valueflows offer developers?
This has been on my mind because Enspiral is planning to opensource and put some energy into "My.enspiral" - the software we use to create virtual accounts and transact money within a company while reducing overheads.
A year ago @bhaugen wrote a pretty good description of one of the main use cases here and its overlap with valueflows. The other week I started a design exploration thread targeted at my.enspiral. I've put my hand up to help with the design and development but I imagine work won't really get going until the new year. Since enspiral is a do-acracy and I will be doing some of the doing I hope to influence my.enspiral to align with valueflows but I don't have good understanding what that means.
I'm not sure yet but lets say that redevelopment means spitting the app in to an API and a frontend. It would be great if the API could handle syncing accounts and company level transactions with Xero and also with a third app for a specific collaborative funding use-case Cobudget.
Imagine you're a sceptical developer of my.enspiral. In the projects you've worked on you've seen the benefits of keeping a tight scope and minimising coordination costs by giving the lead dev autonomy over implementation details.
Why would you give up your hard earned autonomy over technical implementation to do things the "valueflows way"? How will this benefit the redevelopment, and ultimately users? What does "valueflows way" even mean in practice? Won't that blow out the scope of the project? Isn't software development about meeting and responding to user needs (agile), rather than conforming to abstract prefigured requirements (waterfall)? :)
Thinking about this case may help us get develop better comms in general