Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
I look for another place. But next time he disagrees ask him to ellaborate on why he think that it is 3 hours.
was there once. the fucking stupid manager screwed the project and cost a client to the company and client fired their team and we guys left our company.
Yeah... during our first foray into "agile", this happened a bit. Thankfully, we made it known during the retrospective meeting that the practice is breaking productivity and that the team feels their manager should "get scarce" during planning for the next 3 sprints.
The productivity increase solidified the practice.
Seems strange that stories and tasks are being created in sprint planning. Stories should be created by the PM and then split up as necessary in grooming. Tasks should be created before sprint planning by the developers alone and then planning is just figuring out what will be done based on resource availability and sprint length.
Seems like the agile process your team is using is missing a few steps.
purged35433yScrum isn't perfect, but if you guys are doing retrospectives, that would be a good time to bring that up. Your team will most likely back you up.
If your manager doesn't like the criticism, or ignores it, it's time to go above his head with the issue, while looking for something else in case they let you go for it (they shouldn't, but let's face it: some people are assholes)
Side Tip: as a manager myself, nothing will put you in poor-graces with your manager faster than going above his head without FIRST bringing the problem to his/her attention and giving them the opportunity to address it.
manrock0073I've been doing agile wrong my entire life
abhi-inc7This story is 100% true. I got hired onto a team of construction workers to build a house. We set up a meetin...
bittersweet14"Let's do some pair programming! It will be fun!" ... Fuck no. Either I start coding and you open a beer, or...