My first impression was OMFG TOO COMPLICATED, but then I sat down and evaluated each step. To be frank, it just looks terrible on paper, it's very close to the workflow we have (we try to have) currently. I wouldn't be worried, most if not all of the tedious tasks would be done by the pms anyway.
I talked to Robert about this a lot, he even added an Agile choice based on my recommendation, so for projects that are a better fit for agile we have something to start with.
I need to copy over another comment of mine here:
"We totally have to make sure not to put too much overhead on work, as that might cripple progress. At the same time, we have to make sure to have some kind of planning/coordination/reporting/progress tracking, otherwise this project won't be able to scale. Trying to explain this is something we usually have a VERY hard time with. And that's totally understandable, as most people here are freelancers / enterpreneurs, and are used to the mentality of "execution is king". And they are right, but after a given team size, which is 4-5 max, there needs to be another layer. If we'd like to step up from here, we'll need to come up with a good solution in between the two extremes - if not, we'll remain at the level of a hobby project for 5-10 people."
So while we understand where the people who oppose any PM activity are coming from, based on our experience we simply cannot let zero coordination happen
It's really dificult to find the sweet spot, so please stay patient guys, and provide feedback as much as possible. We'll get there.
