Ticket to log time: SE-4874
When I mentioned fluid cells, I was thinking in terms of how I’ve seen other consulting shops (IBM, Accenture, etc) do it. Roughly speaking, you don’t join cells - you join projects. And for the duration of the project, that’s all you focus on. (In those companies it’s horrible projects like SAP customization, but you get the picture.) The overhead is only as big as that particular project itself.
What happens when the project is over? You sign up for (or are transferred to) another one.
To try and translate this into OpenCraft terminology, this would mean that instead of joining cells, we’d join epics. Total, 100% focus on one client and/or project. No firefighting things you have little context in. No distractions, a lot less context switching. And if the project ends and there’s no new one available immediately? No sweat: join one of the accelerated epics.
The thing is… this would work well for large(ish) epics, probably not so much for small ones. We’d likely have to ditch small customers altogether - which may or may not be financially feasible. (That it works for IBM does not mean it’s possible for us.) We’d also have to ditch sustainability per cell - likely the cell concept altogether.
Anyway, just a thought.