Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Search - "product owner"
Scrum Master: Let's estimate the task. Chose your estimations individually, then we will reveal at the same time and discuss
- variety of votes, ranging from 1 to 8
Product Owner: I don't agree, this should be a 1 or 2.
Dev Team Lead: Agreed, this is why I chose 2. Let's vote again.
- All votes now are 1s or 2s
Good fucking job 🤨11
Back when I was an wee lad I interviewed for an startup, not knowing that startups are not real companies. The scumbag interviewer, who was also the owner of the outfit, asked me what I was looking in a company. I said "fair wages, a non-antagonic environment and projects with real roadmaps".
He asked me to elaborate. I said, "You know, if today your product is a sales platform, I do not want to come into work next week and discover it is now an air travel tickets marketplace, or come back the very next day and discover it is now an automated pizza factory, or in the next day and it is now a crypto exchange..."
The scumbag looked PISSED. "Sorry, but we are looking for someone who likes the challenges of a dynamic environment (read: we do not have a business model and we hate the very idea of trying to make money out of our company), and you do not fit the profile"
Startups are not real companies, i.e. they do not systematically charge money in exchange for goods or services in amounts that exceed the cost of providing said goods or services. Most startups are just tax fronts for money laundering schemes. The rest are just playthings for rich assholes who can't get a real output-producing job. Those two categories are not mutually exclusive.
Take Facebook, for example. The poster child of startups. The Zucker that owns it just announced they are setting impossible performance targets on purpose, not even attempting to hide the fact that it is just a way to lay off large quantities of employees without using the words "massive lay offs". Companies, real thin-margin, lots-of-regulation profit-driven companies do not do that. They are not some sort of "capitalist woke", real CEOs just know that if their companies largely miss performance targets on their tenure, purposely or not, next it will be their neck on the chopping block. Because they can be fired if the KPI charts say they suck. But the Zucker cannot be fired, not even after commanding their beanbag and tap beer offices to be heated exclusively by burning hundred dollar bills.
So the Zucker is not interested in performance. Not even in lay offs as expense cutting measures - investors are an infinite source of free money for startups. The Zucker just wants to project power, especially now that engineers are not so confident in the stability of they high-paying jobs.
So are irrelevant 500-souls-or-less self-aggrandizing startups. Their owners are there because it is in vogue to have a startup or ten. And will have that startup pivot to whatever sounds fancy that season. After all, only poor people care about things like EBITDA and profit margins repeatability - A.K.A. "getting more money".
We work remotely, the only way I can collaborate with other Devs, team lead, product owner is slack. Respond to my f***ing messages people!3
I am mentally burned out from web development.
Physically I'm fine, but it's getting more difficult each day to open my laptop and write code, documentation or do code reviews.
Web development just seems so meaningless, where my day to day job has me trudging through one web form after another. I'm sick of implementing business logic on the backend and tired of listening to the product owner bitch about users who are demanding.
My productivity has fallen to the level where I'm feeling guilty for spending my time on nothing!
Don't give me advice, I know I need a change of scenery.
I just need to find the motivation to work on another hiring test which has nothing to do with the actual job.8
Jesus. Got elected by the product owner last minute to give a presentation to a bunch of stakeholders. What the fuck is the point of your job if all you do is delegate your responsibilites to other people.4
I have an interview with a CEO and product owner next week for the position of principal developer. The job ad which got me here stated 'Any additional skills you have will be viewed favorably'.
I've had my ass burned by that crap at least once before. When they ask about private projects, I'm just going to say "I love my job so much, I do it in my free time too!"3
So a few weeks ago, our PO really scolded my team for not letting him in on our release planning meeting. His rant went on for about 30 minutes, just one long monologue about why he should be invited in the future.
Apparently he wanted to know details since there were some important fixes in the release, which I suppose is fair (though the rant is really not necessary).
Fastforward 2 weeks, we invite him again. He accepts, but never shows up. We decide to start the planning anyway, since we don't want the release branch blocked because someone didn't show up.
Immediately after the meeting, we write him with the new release plan. And he starts ranting again about "planning without him" -.- ..
1) Stop yelling at the team you're supposed to work with. Talk with the team about it - I'm sure they'll listen.
2) If you demand being in meetings, show up - or at least decline in advance.
3) You have no right to rant about "not being part of the planning" when you were literally invited for a planning meeting 2 weeks in advance. No meetings were overlapping, so there's literally no excuse..1
Joined a new team at work 6 months ago. Immediately set upon by a useless PO who was somehow set in her ways while still being around 30 years old. Absolutely refused to change the broken team dynamic or processes in any way whatsoever. Made terrible tickets, never did refinement on tickets so they were always missing stuff and constantly blocked. Generally unlikeable and difficult to work with, incompetent at her job and resolutely refused to change literally anything to make the team function better.
She finally leaves after 6 months and the team dynamic changes immediately. Suddenly we are improving our processes, getting stakeholder input, refining tickets, taking reasonable amounts of work in a sprint. We have discussions without her butting in and getting frustrated when you bring up legitimate concerns. No longer do you have to tiptoe around and appease her ego if you want to point out the obvious flaws in the work she drew up or even just examine it from a technical perspective.
It's insane how much things can improve once you shed the dead weight of people that are just determined to be difficult and won't budge an inch to change their ways. Good riddance.2
Product owner (who is also the application administrator): please build feature to allow administrators to create automatic alerts to be sent to application users
Feature gets built, tested and deployed to production
Two months later:
PO: I've noticed in our monitoring tool that there haven't been any alerts sent out to users. What's going on??
Me: well have you created any automatic alerts?
PO: umm, no. How do we do that?
Me (inside): 🤦2
Go assign a super simple ticket to your "product owner" or "manager" or whoever the hell claims they "work so hard" and "have the vision" or whatever blah blah blah when in reality YOU'RE the one working 12 hour days, completing the features used by THOUSANDS.
Just try it. They'll never complete it. I guarantee it. Here I am looking at one that is three weeks old asking to update the f&*(@#$ credit card credentials for a simple log service to be reactivated.
So sick of this backward world where us devs never get any credit.
Who wants to start a software union with me?2
I once resigned the ui of our banking application on my own initiative without consulting with any clients. I then left that job before our next release. Apparently the product owner got flak because a client measured the header with a ruler pressed to their monitor and found the new header was sightly bigger.6
Old old organization makes me feel like I'm stuck in my career. I'm hanging out with boomer programmers when I'm not even 30.
I wouldn't call myself an exceptional programmer. But the way the organization does it's software development makes me cringe sometimes.
1. They use a ready made solution for the main system, which was coded in PL/SQL. The system isn't mobile friendly, looks like crap and cannot be updated via vendor (that you need to pay for anyway) because of so many code customizations being done to it over the years. The only way to update it is to code it yourself, making the paid solutions useless
2. Adding CloudFlare in the middle of everything without knowing how to use it. Resulting in some countries/networks not being able to access systems that are otherwise fine
3. When devs are asked to separate frontend and backend for in house systems, they have no clue about what are those and why should we do it (most are used to PHP spaghetti where everything is in php&html)
4. Too dependent on RDBMS that slows down development time due to having to design ERD and relationships that are often changed when users ask for process revisions anyway
5. Users directly contact programmers, including their personal whatsapp to ask for help/report errors that aren't even errors. They didn't read user guides
6. I have to become programmer-sysadm-helpdesk-product owner kind of thing. And blamed directly when theres one thing wrong (excuse me for getting one thing wrong, I have to do 4 kind of works at one time)
7. Overtime is sort of expected. It is in the culture
If you asked me if these were normal 4 years ago I would say no. But I'm so used to it to the point where this becomes kinda normal. Jack of all trades, master of none, just a young programmer acting like I was born in the era of PASCAL and COBOL9
Does anyone else find it strange that the stupidest people in the company are making all the decisions.
In order to be able to engineer software you have to understand everything that the product owner knows, the business analyst knows, the product manager knows + how to actually make the system both work in a reasonable time frame and be maintainable long-term.
But we're not the one making the decisions. The irony of it is something that I can't get beyond.
And when I do go out on a limb to point out a logical inconsistency to UX or product... They don't thank me for it they hate me for it and then 3 days later figure out that they should be doing it and quietly follow my suggestions.
Seriously is the goal here to create good software or to avoid stepping on everyone else's toes in the company who is overwhelmed by the complexity of the project.
I think companies based on a hierarchy of non-technical people controlling technical people, in the creation of software products are a dying breed.
When it comes to creating software products everyone in the hierarchy should be technically minded.
I've seriously been trying to come up with an alternative perspective here.
The executives of the company are completely out of touch and the only thing which looks like progress to them in a sprint review is something visual on the front end.
The technical architect, the product owner and the product manager all seem to be engaged in keeping the executives happy and managing their expectations. By means of obscuring the truth.
Imagine how much more cost-effective building a software product would be if the executives were engineers themselves.
I'm keen to do an experiment and build a company comprised of engineers only.
Obviously they need to have insight into the other roles. But none of these other roles are as complex as implementation itself.
So why exactly are we the slaves of these well-meaning under thinkers?7
Two weeks before the release of a major new version of an application I'm working on, the testers finally got round to testing the new functionality (a set of a few features and a new page). They didn't agree with the requirements and got the requirements to change with the product owner.
The product owner now says that these changes "are easy to implement" and "the new requirements are clear" even though the other devs and I all don't understand the change. How would a product owner even know it is easy to implement?
Currently having very funny project lead, who gives on the spot estimates for 9 years old very pathetic quality code having Android app in security domain. Memory leaks, bad practices, typos, CVEs etc. you name it we have it in our source of the app.
Since 5-6 sprints of our project, almost 50% of user stories were incomplete due to under estimations.
Basically everyone in management were almost sleeping since last 7-8 years about code quality & now suddenly when new Dev & QA team is here they wanted us to fix everything ASAP.
Most humourous thing is product owner is aware about importance of unit test cases, but don't want to allocate user stories for that at the time of sprint planning as code is almost freezed according to him for current release.
Actually, since last release he had done the same thing for each sprint, around 18 months were passed still he hadn't spared single day for unit testing.
Recently app crash issue was found in version upgrade scenario as QAs were much tired by testing hundreds of basic trivial test cases manually & server side testing too, so they can't do actual needful testing & which is tougher to automate for Dev.
Recently when team's old Macbook Pros got expired higher management has allocated Intel Mac minis by saying that few people of organization are misusing Macbooks. So for just few people everyone has to suffer now as there is no flexibility in frequent changing between WFH & WFO. 1 out of those Mac minis faced overheating & in repair since 6 months.
Out of 4 Devs & 3 QAs, all 3 QAs & 2 Devs had left gradually.
I think it's time to say goodbye 😔4
Question: How to deal with an idiot product owner?
Doesn't understand the job description. Thinks he's the manager. Controlling. Loud. Annoying.
Started freelancing via agency as android dev for this client. The product is a kyc mobile sdk with a flow of around 20 steps for identification. My job is to maintain the sdk/fix bugs/add features and so on.
Communication seems to be so fucking terrible.
For example the product owner is not technical and sucks at defining issues.
QA sucks at testing and providing feedback. Backend sucks at documentation and seems to live in a parallel universe, swagger docs are outdated. Previous android dev whom I replaced gave me 2 hours of his time during his last month in the company, answered some questions and then left today (which was release day) with around 6 bugs hanging. Now because we are behind schedule the PO is grilling my ass so I would provide hourly estimates, while I dont even know the codebase yet since I spent maybe 30 hours on it in the last month.
What a clusterfuck. I feel like Im in a kindergaden where people are either lazy or incompetent. It seems that sweet gig of 40 hours a month will become much more hours or my output will be low :)2
1 - Correct me if I’m wrong, but in true Agile, a product owner ought to be able to interact directly with the dev team, and vice versa, in the card/conversation/confirmation process of creating, estimating, and executing the user stories, correct?
2 - If Company “A” contracts with Consultant “A” to have software developed, and then Consultant “A” then contracts with Company “B” who then contracts with Consultant “B” to do the development, who would you define as the Product Owner?
3 - If Company “B” is barring Consultant “B” from talking with Company “A” and Consultant “B”, is Agile even possible?7
#Suphle Rant 2: Michael's obduration
For the uninitiated, Suphle is a PHP framework I built. This is the 2nd installment in my rants on here about it.
Some backstory: A friend and I go back ~5 years. Let's call him Michael. He was CTO of the company we worked at. After his emigration, they seem to have taught him some new stack and he needed somewhere to practise it on. That stack was Spring Boot and Angular. He and his pals convinced product owner at our workplace to rebuild the project (after 2+ years of active development) from scratch using these new techs. One thing led to the other, and I left the place after some months.
Fast forward a year later, dude hits me up to broach an incoming gig he wants us to collab on. Asks where I'm at now, and I reply I took the time off to build Suphle. Told him it's done already and it contains features from Spring, Rust, Nest and Rails; basically, I fixed everything they claimed makes PHP nonviable for enterprise software, added features from those frameworks that would attract a neutral party. Dude didn't even give me audience. I only asked him to look at the repo's readme to see what it does. That's faster than reading the tests (since the docs are still in progress). He stopped responding.
He's only the second person who has contacted me for a gig since I left. Both former colleagues. Both think lowly of PHP, ended up losing my best shot at earning a nickel while away from employed labour. It definitely feels like shooting myself in the foot.
I should take up his offer, get some extra money to stay afloat until Suphle's release. But he's adamant I use Spring. Even though Laravel is the ghetto, I would grudgingly return to it than spend another part of my life fighting to get the most basic functionality up and running without a migraine in Spring. This is a framework without an official documentation. You either have to rely on baeldung or mushroom blogs. Then I have to put up with mongodb (or nosql, in short).
I want to build a project I'm confident and proud about delivering, one certified by automated tests for it, something with an architecture I've studied extensively before arriving at. Somewhere to apply all the research that was brainstormed before this iteration of Suphle was built.
I want autonomy, not to argue over things I'm sure about. He denied me this when we worked together. I may not mind swallowing them for the money, but a return to amateur mode in Spring is something I hope I never get to experience soon
So, I'm wondering: if his reaction reflects the general impression PHP has among developers globally, it means I've built a castle on a sinking ship. If someone who can vouch for me as a professional would prefer not to have anything to do with PHP despite my reassurance it'll be difficult to convince others within and beyond that there could be a more equipped alternative to their staple tool. Reminds me of the time the orchestra played to their deaths while the titanic sank16