Hacker News new | past | comments | ask | show | jobs | submit login

Re #3: this has been my experience almost my entire 10 year tenure as a software developer. You start out doing a few stories, hey this is easy. Then they get harder (ooo we're starting to pack those two weeks now! Hope I get a good bonus for this, it's exhausting), then eventually you're tracking down acceptance criteria for your own stories (what happened to the project manager?! I can do this though, I'm senior level, no problem), then you're getting support requests for other devs and more and more work, scope creep, debugging, etc...

And any request to "follow the rules" (what if we had AC before stories started? what if we defined who would do that and gave them time to do it? what if we didn't change or add stories mid-sprint? can we discuss why that overtime happened the last few times so it doesn't happen again? Sure, bring it up in the retro... but we won't be willing to change much, sorry) leads to you being increasingly shunned and disliked.

Does anyone have solutions to this? It seems like most people solve it by moving up the ladder, as ICs generally aren't treated well in most places, and when you can delegate you hopefully can get back to 40h/wk.




> then eventually you're tracking down acceptance criteria for your own stories (what happened to the project manager?!

Lol depending on the product owner I get anywhere from "some nice stories and design mockups" to "there isn't even a document describing the requirments and I have to write my own stories for bookkeeping purposes."




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: