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
Search - "pm po"
-
PM in daily: your turn. what have you done yesterday?
me: so i finished my PR for feature x and now i'm only waiting for review feedback there, so i can close this ticket today if no major rework is required-
PM: this is not what i asked, i don't want to know what you did, i want to know what was done.
me: uhh... okay, also i started working on task x
[note: task x, a task per definition involving a large amount of research, was very coarsly defined and it wasn't even clear to the PM what he exactly expects from me, and we agreed that the scope needs to be refined in the process],
so as a first step, i started doing some general investigations to get an overview of the topic and learn about concepts a and b-
PM: again, i don't want to know what you did, i want to know what was done.
me: okay well, i have DONE basic research on topic xy and collected information-
PM: this still does not answer my question, what's the deliverable?
me: ...so uhhh.... i read papers? i researched info online and collected and prepared information and links in a presentation which i'm also planning to present to the team-
PM: okay, can you please split your jira task in subtasks so everyone knows exactly what you're working on? otherwise we have no idea what you're doing.
for fuck's sake, shut up. just shut up22 -
it finally happened, PM/PO/SM is now also dev シ
each standup he now also gives update about his work in progress, with his diligently designed subtasks, perfectly sticking to the daily script, like a good well-behaved employee boi. it's weirdly cute
devs can't await to review his first PR. feeling the strong urge to spank his ass for each minor coding style issue or poorly-named variable...12 -
so management decided that the PM/PO/SM role has to be split and that SM shall be done by someone else.
PM in retro: so i will give away this role because i cannot fulfill all roles adequately, not because of missing skills, but because of missing time. this is also why i couldn't finish my development task for this sprint. so, someone of you guys has to do the job. i expect the future SM to be always available for me in the morning and the afternoon, so due to timezone shift this has to be someone from the German colleagues. I will have to explain to that person what exactly I as a PO expect from the SM and the SM will have to follow this guideline. also, being SM is no excuse for not delivering your stories, it just takes very little time.
...i don't need to comment on this at all, he already makes a perfect clown of himself 🤡7 -
I just experienced near death because of high blood. Super strong blood pressure. Avoid coffee, playing games, and sleeping very late at night. This is my advice as a survivor developer. I want to share this to help you. For fast deadlines or hard user stories, always negotiate reasonably with your SM or PM or PO or client.
Thank God he have me a 2nd chance at life. Take care of your health. Don't worry about deadlines. Health is more important. Always pray. I deleted all of my games especially my beloved call of duty mobile and clash of clans. I'll forget all games that I know because those contributed to my high blood pressure.
When you have a headache or head pressure or eye twitching . Stop what you are currently doing and relax, measure your blood pressure and contact your family asap. Take it seriously. My wife saved me.10 -
daily.
PM/PO/SM/dev(new!): so i've continued working on feature X, i did this and that (shows screenshot of UI in Jira) and for today i'm planning to do XYZ. anyquestionsnothennextoneplease.
me: sorry, i have a question. did you persist your changes in our repo?
PM: no, not yet.
me: okay, please do this, you've spent several days of work on this. i mean, it's fine if build servers don't build it yet, that's what our feature branches are for.
PM: you're absolutely right, and i will definitely do it at some point.
me: at some point?
PM: yes. dev x, your update please.9 -
I fucking hate morning people like the one in the story below!
Before we begin story time I want to acknowledge some things.
This is largely a case of a person having a lack of awareness and giving in to their base instincts (which are wrong).
People all tend to think that everyone else is like them (most children below a certain age cannot make this distinction and many adults never learn it either).
To take it a step further, anyone who isn't just like them is Lazy/Bad/An Asshole/etc.
FUCK THOSE PEOPLE
Now it's story time...
---------
I worked for a startup. We used a modified SCRUM, and we had standups every day @ 10 AM, the other team had then at 11:30 AM.
We get a new product owner. He is a morning person. But basically, he is a day-trader so he wakes up at 5 AM to trade and is in the office by 8 AM every day.
The problem is, he uses this as a reason to leave every day at 3 PM when EVERY other member of the team is there until at least 5 PM.
So he says one day (when I am not there) that we are moving our standups to 8:30 AM...
"Because he wants to make more use of the time and wants to get more done!"
So the next day a bunch of us miss this standup, the second day I was there in time but instead of going to the standup I sent them a picture of myself sitting in a coffee shop across the street with a message saying...
"I will be holding a meeting today at 10 AM, I expect EVERYONE to be there. If anyone on our team is absent then we will sit there and that absent person will be responsible for the time we waste waiting for them."
10 AM rolls around and the Product Owner is nowhere to be seen. The team starts complaining about the early standup and I tell them that this meeting is for me to take care of it. I tell them to sit silently and let me handle it.
We all message the PO saying the same thing...
"Come to the meeting, You are wasting our time!!!"
So he shows up at 10:20 AM and it begins.
(Now I'm going to do this as a conversation)
PO: "So I assume this is about the standup?..."
ME: "Feel free to ramble on as long as you want, you have already wasted 20 minutes of our time so we will sit here quietly and wait for you to decide you are ready to stop wasting our time with your ramblings. That's fine."
<PO then shuts up in disbelief>
ME: "So are you finished?"
PO: ...
ME: "I'm expecting an answer PO!"
PO: Yes, for now.
ME: I am moving our standups to 5 PM, end of discussion.
PO: Becuase your too lazy to be here by 8 AM?
<I expected this>
ME: No because I'm an asshole who expect everyone to conform to my schedule.
PO: ..., Well, I am not here at 5 PM.
ME: Sounds like your too "lazy" be here at 5 PM, eh?
PO: I have other things I do then.
ME: Ah, now the truth comes out. You care more about your life than our business. That's unacceptable! I personally don't care what you want to do. The fact is that we are working here and every day we end up having PO questions that need to and can't be answered because you are not here.
PO: <To the team> The standup is still at 8:30 AM.
ME: <To the team> The standup is at 5 PM. End of story. And from now on whenever we have questions before 5 for PO and he is not here we will be recording it and putting it in his report.
Then I walk away.
That day we held a standup at 5 PM. He wasn't there. He held a standup at 8:30 AM and he didn't even show up. He stayed home a video in. He then arrived in the office and said...
PO: Since no one was in the standup today we will be moving it back to 10 AM.
ME: Since PO has seen the selfishness of his ways, We will be moving the standup from 5 PM back to 10 AM.
FUCK THOSE PEOPLE6 -
Sometimes human stupidity still surprises me.
Today I was able to stop the release of a ticket at the last moment that intended to put urls WITH A SECURITY TOKEN TO ACCESS USER DATA through a link shortener.
Some PM assumed that it would be a reasonable course of action to map an url secured via jwt through to a 4 character, countable, base64 string so that we don't have to send multiple sms if they contain this url. I can accept that the implications might slip through one person but the fact that this was put into a ticket by a pm, prioritized by PO, estimated by an entire team, implemented by a professional developer, reviewed by a senior and then scheduled for release without anyone asking themselves if there might be a reason for a security token to be long, that one shocks me.8 -
Okay, one after another. They like to piss me off, apparently.
Coleague knows something isn't possible with current state of some api and pushes phone to me so I can maybe figure out what to reply to client. I dry-typed in "Its not possible" gave him phone and said "boom done, you know it aint possible"
Okay, TL;DR she got pissed that I am pissed that this BS is thrown at me and I dont want to participate in promissing something I know is undeliverable.
So she told me to go to PM/PO *kind of guy but not rly* with that problem. He aint technical by any mean. We are small company and for some reason this guy has more bearoucratic approach than I thought is possible to fit in one human.
Anyway. Well, apparently we will have meeting what are our options.
It all beginned that one guy promissed other guy undeliverable feature....
And becouse someone couldn't use his fucking brain it's pushed onto me, or I need to figure out how to do it. You cant without introducing safety flaw, period, it's that fuckin' simple.
But nooo, we will have god-knows-how-long meeting, that will bring exacly 0 value, as fking allways, and all I want now is just fucking focus on my fucking code becouse, ya know, I have timeline to follow, I dont have time to all that BS.
And to give you context, while keeping the stuff I cant share secret, imagine you have an API, that is just 'facade' of backend API, and layer of security. And they want to add authoritative endpoint to the facade API. Kind of endpoint "yes, you got paid".
Bravo, big brain, it will not work without like huge-as-fuck vunrability...
IDIOTS
How to not get pissed? Any protips?1 -
Am I the only dev being in the universe who hates dealing with non technical PMs and POs?
Every time I interact with them I just want to kill myself.
PS: I still think their roles are important. Just hire people that know what they are doing.8 -
currently thinking about asking my boss if I can make a training / qualification for scrum master.
when PM is trying so hard to shove *his* scrum down our throats and at the same time tries to block any scrum-related criticism of team members that question his behavior as SM AND PO, then maybe convincing my boss to become the new SM and shoving ALL the scrum down the PMs throat is the only chance to have a (bit more) bearable working environment in this project.
in my opinion, he has too much power.
whatcha think? any SMs here, and do you like what you are doing?8 -
Our current project...
First three sprints... going fine and slow get used to each other.
Later sprints get more of a clear scope. With a deadline a couple of months later. The team raises some red flags with problems.
Seems like the PO/PM doesn't get it or ignores it.
More sprints later with more confrontations. PO/PM still doesn't get it.
Team introduces a new theme song
https://m.youtube.com/watch/...
Hopes she gets it now . . . -
PO: Sure, use any tool to get the job done. You recon within 2 weeks to have a working demo?
Me: You bet ya
****1.9 weeks later****
PM: PO says to use another tool for this project.
Me: 🤬🤬🤬🤬🤬🤬🤬🤬🤬🤬🤬🤬4 -
I figured it all out, where all the bad code comes from, I know it now!
I think good developers need two things, an ego that makes them wanting to be competent and perceived as such and (very important) a problem with authority!
All the bad code is written by people who wanted to be liked by their teachers. The PM and PO are their teachers now and they make everything possible for them. Technical debt and human costs are swept aside when the authorities want a stupid feature now - because they have to like you and you need to be a nice pet to whip! -
PO writes a story. We groom it. Point it. Do the work. Finish the work. Dev test it. Push it to test. Tester find a weird edge case. Talks to me. I agree it’s weird. I talk to PO and the PM in the standup. PO realizes the whole business flow doesn’t make any sense. Changes the AC. Asks us to change/redo shit. 2 days until the end of the sprint.
I guess I’m working this weekend. Not that I have to go anywhere 🤷🏽♂️4