3 ms·
I'm surprised that a startup would even consider following one of these processes. They are responses to the organizational constraints of corporate software de
by gruseom 18y ago
I'm surprised that a startup would even consider following one of these processes. They are responses to the organizational constraints of corporate software development (and its symbiotic relationship with big-name consultants). A startup isn't, or shouldn't be, subject to those constraints in the first place. So a startup that feels the need for such a process seems likely to have more fundamental problems than a process can fix.
I don't mean to criticize anything that's genuinely working, and one can't tell much about a particular situation from a blog post. But all other things being equal, I'd say something is wrong.
Edit: I missed this from the original article and just read it in another comment:
The development team is run by a project manager. His role is to move the top priority user stories from product backlog to the sprint backlog and break them in atomic tasks that are distributed to your developers.
Is this a joke? This is not only ludicrous behavior for a startup, it's the very opposite of the process this startup has supposedly adopted. I take back "one can't tell much about a particular situation from a blog post". This says a great deal.