Ranter
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
Comments
-
- Add in more reporting, ofc don't just use the Jira status view, then complain why people aren't working on the actual tasks.
- When the deadline approaches, increase the reporting frequency, at least twice per day. More reporting surely makes the project finish earlier. -
@soull00t Just comment that the ticket should be clarified by stakeholders, and summon endless meetings with scum and SO.
meetings about work ==> actual work.
keep hammring "action item"/"velocity"/"delierables"/"DOD"/"customer value" in the meetings - until you are promoted or find a better job. -
Sorry, I have no time.
Later: Why did you not talk to me and coordinate the priorities?
Related Rants
-
soull00t22PM in daily: your turn. what have you done yesterday? me: so i finished my PR for feature x and now i'm only ...
-
soull00t4hey there, long time no rant. remember that manipulative, sociopathic angry manchild turdface PM, the kind tha...
-
soull00t2PM was on vacation the whole sprint. this sprint was so much more... convenient. i really liked what i was wor...
how to become a true scum master:
- formulate jira tasks for your inferiors as vague as possible, best they don't make any sense
- before sprint start, ask the subhuman being to estimate storypoints, and if they say they can't really tell with this description and choose the highest estimate, say "okay, let's estimate it to one sprint length", so they can actually work on it within one sprint (which makes total sense)
- if the scum dares to question the content of the ticket and begs for more details, be like teflon and give no useful answer at all. if they continue asking for a meeting to discuss the ticket, tell them to have a meeting with a coworker about it (who also has no clue). don't be available for them because you have more important stuff to do.
- bully them during daily standups that they didn't create clear subtasks from this task and criticize them because you have no idea what they are doing. tell them they are having performance issues and suspect them to sit on their lazy asses all day.
- criticize the team in general for bad performance, bad item tracking and never say something nice, to make sure everybody loses even the last bit of intrinsic motivation for the project.
stay tuned to learn how to make yourself a skull throne out of those filthy dev smartasses ^.^
rant
daily scum