Quote:
Originally Posted by Biggle10
I think they missed the 'people over process' message too.
The “people over process” concept means that a team or department forms processes based on the workers, rather than forcing the workers to accommodate a pre-designed process.
What problem are they trying to solve? Do tickets stagnate for a long time because only 1 person is working on them?
thanks this is a good response. they really like things like this. its not enough to just express why you think its a bad idea, you need a catchy buzzword/phrase and all that.
and no tickets dont stagnate. the only time a ticket takes too long is when we have dependencies outside of the program. our Scrum Master said that if we have such blockers then we should have everyone available work to overcome them. to me, this is obv idiocy. bc now instead of one person stuck, we now make the whole team stuck while we wait for the block to get resolved.
I think a lot of this process stuff is done for 2 reasons. 1) bc the managers want it to appear as if they are doing something. 2) the devs want to impeded their tasks as much as possible bc they are either lazy or suck at programming.
I am just gonna go with the flow and smile and nod and regurgitate the proper buzz words. just makes it easier.