Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
It seems wrong but it's there for good reason. If you work in a place where your PO (or their boss lol) is out of control this allows the Scrum Master to say "no" to slipping in new stories during an active sprint. It's about longterm sanity for the entire team, avoiding burnout, etcetera. But it's not necessarily a steadfast rule depending where you work.
I would consider this a learning opportunity more than anything. Maybe next planning session you need to mention that they should stack in more stories for team members with certain skillsets to increase velocity. My 2 cents.
I'm at this magnificent company, working scrum, doing continuous integration which is really very cool. But although the features we develop are really nice it is sooooooo boring.
One of our team members emphasized that we should not pick up new stories if we haven't finished previous stories yet. I agree to some extent but think it is ok to pick up new stories if you have nothing to do. But we may not.
So, here I am now. Literally waiting for the day to pass. This sucks sooooo much!
I'm a hard worker and perform at my best under pressure with many things to do. Now, I just deployed one tiny little story today. I can do much much more. I feel so useless and cannot believe that my client pays so much just for me being at the office. And occasionally clicking a button and writing a line of code. This is so fucked up.
undefined