Carl-Erik Kopseng
Sep 4, 2018 · 1 min read

This is exactly how I have suggested keeping effectiveness when increasing the size of the dev organization. Glad to hear someone testing it out with success! Since it’s been a year since you wrote, maybe you can explain a bit on how the process at EVRY is actually implemented?

I assume that a “task” is like a sub-project of its own, where you follow your own Kanban-board or SCRUM process, splitting it up in sub-tasks, without affecting others.

At least, that’s what I would assume, since having 20 developers all in the same scrum meeting, largely irrelevant for most, would not be effective use of time. I am also assuming a feature is of some non-trivial size (like a man-month or more)

    Carl-Erik Kopseng

    Written by

    Senior Front-End developer at Making Waves. #ENTP