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 - "scrum"
-
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 up21 -
Manager: How come the push to prod didn’t happen?
Dev: We told you at the scrum yesterday. To reiterate, our dev environment was crashing so it’s not safe to push to prod until that is fixed.
Manager: Ok well lets set a goal to fix that and push to prod happens today so that it guaranteed happens.
Dev: That was our goal yesterday and it definitely didn’t happen.
Manager: I AM AWARE OF THAT. The corrective action is that this time compliance with the goal is 100% ABSOLUTELY MANDATORY!!
Dev: We’ll do our best, can’t guarantee anything until we figure out what the nature of what is occurring on dev though.
Manager: NO. I AM THE BOSS. YOU WILL 100% ABSOLUTELY COMPLY WITH THIS. THAT IS AN ORDER. YOU WILL SUCCESSFULLY GET THIS UPDATE OUT TO PROD TODAY. ANYTHING LESS THAN THAT SHALL BE CONSIDERED INSUBORDINATION. I WANT STATUS UPDATES EVERY 15 MINUTES ON WHERE WE ARE AT WITH THIS.
Dev: …
Dev: Can I get you to send me that request in an email?
*Manager leaves the meeting*
// *****************************
Job search is ticking along. It’s tough going though because I currently make ~120k and the best offers I’ve received so far are all ~70k because “You only have 2 years experience so you couldn’t possibly have the skills to be worth 120k. You are are junior level developer and 70K is already overpaying for you. We can pay you more later™. No we will not give you that in writing”. Ah well, the hunt continues.17 -
Its so weird working in this company. No onboarding, no micromanaging, noone to track your progress or performance. U can basically do what u want and ask what u want and requests will be fulfilled.
Initially was assigned to a random team and started fixing stuff. I hated the scope so after 2 months in requested to switch teams, request approved.
3 months in realized I lowballed myself during the interview and actually am doing better than half of the team, so I asked for a 43% bump, request approved.
4 months in I realized that I did atleast 100hrs overtime in a month during crunchtime, burned out. Asked for a paid week off to recover, request approved.
5 months in realized that we have many MR's piling up in the team and I could help with approving some of them, but they grant MR approval rights only when u work here for a year or are a decent dev from the get go. Requested for MR approval rights, request approved.
Again it feels so weird working on a big product with 6-7 scrum teams. Its like there is no bullshit, just ask what you need you will get what you asked so you can continue working.
On the other hand its kinda weird to keep asking everything, in other companies a good teamlead/manager shows more initiative takes care of stuff like this without even asking.8 -
Didn't finish morning run in time for morning scrum call. Looks like I'm answering the call from here.8
-
The next big trend will be in the area of project management:
The Waterfall™
Agile has been abused to the point where The Waterfall™ is way more agile! Think about it: It's straight down. No loops, no unnecessary hourly, daily, weekly meetings. No micromanaging. Just one flow. It starts at the top and it's all downhill from there.
Pure efficiency!
Edit: Wake up developers! The management doesn't want you to know this simple efficiency trick!9 -
Appretnly for 5 devs + 1QA we need now :
A project manager
A scrum master
A VP of engeneering
Another person I don't remember title.
yep 2023 will be "productive"9 -
Me, complaining about being single: It would just be nice to have someone who cares how my day went every day
Scrum master: Hey...
Me: No6 -
I work for healthcare client project in a start up, worked two years straight without a break.
Client is very inconsiderate about developers work-life balance, he always wants to release every features yesterday.
Never had a reasonable deadline, worked late nights most of the time. No one had backbone to control this client from our side.
Its only developers team, no project management, scrum masters or anything, everything has to be taken care by Dev's.
I decided to take a week break from work.
The first day of my leave he pinged me 3 times to change an "from email" address for notification email which no one give a damn about.
I never replied or did anything. But the part of myself is dying of guilt.
Now I can't relax myself completely.
Re-thinking of my life choices atm.
I loved programming since high school, I can work on computers 24/7 without tired. That's how much I love it. Now I'm just tired of it.
If anyone who read this till here. Thank you.18 -
!rant
This might be the most ambitious project I've ever started up till now, teaching my girlfriend everything college isn't.
As some of you may know my uni isn't the greatest and lacks in professor quality, my girlfriend (who's taking the same bachelor) knows this and when she knew I was starting a new little side project she wanted in.
At first I was skeptical, this could be just an excuse to spend more time with me, so I told her:
"if you really want to then I'm all for it, it'll be done my way and the first few weeks will be tough, however I promise by the end of it you will know 10x what you do now"
She agreed and so our journey began 3 weeks ago, my goal: make a kick ass project, do it in record time and teach her enough to cope with a IRL job.
I've setup the project so by the end of it she is well versed in the following: scrum, Django, MVC, python, HTML + CSS3, git, GitHub, PostgreSQL and Docker. In about 4 to 6 months.
We are into our third sprint this week, she had two small breakdowns because she couldn't believe how much she was missing out and felt she lacked talent, this is our third week and I'm glad to see that she's actually enjoying herself.2 -
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 -
sprint retros with PM are a fucking farce, it cannot possibly get any more grotesque.
they are held like this:
- in the meeting, PM asks each team member directly what they found good and bad
- only half of the team gives real negative feedback directed towards the PM or the process, because they are intimidated or just not that confrontative
- when they state a bad point, he explains them that their opinion is just wrong or they just need to learn more about the scrum process, in any case he didn't do anything wrong and he is always right
- when people stand up against this behavior, he bullshits his way out, e.g. using platitudes like "it's a learning process for the whole team", switching the topic, or solely repeating what he had just said, acting like everybody agreed on this topic, and then continue talking
- he writes down everything invisible for the team
- after the meeting he mostly remembers sending a mail to the team which "summarizes" the retro. it contains funny points like "good: living the agile approach" (something he must have obviously hallucinated during the meeting)
- for each bad point from team members, he adds a long explanation why this is wrong and he is doing everything right and it's the team's fault
- after that happens the second part of the retro, where colleagues from the team start arguing with him via mail that they don't feel understood or strongly disagree with his summary. of course he can parry all their criticism again, with his perfectly valid arguments, causing even longer debates
- repeated criticism of colleagues about poor retro quality and that we might want to use a retro tool, are also parried by him using arguments such as "obviously you still have to learn a lot about the scrum process, the agile manifesto states 'individuals and interactions over processes and tools', so using a tool won't improve our sprint retros" and "having anonymous feedback violates the principles of scrum"
- when people continue arguing with him, he writes them privately that they are not allowed to criticize or confront him.
i must say, there is one thing that i really like about PM's retro approach:
you get an excellent papertrail about our poor retro quality and how PM tries to enforce his idiocratic PM dictatorship on the team with his manipulative bullshit.
independently from each other, me and my colleague decided to send this papertrail to our boss, and he is veeeery interested.
so shit is hitting the fan, and the fan accelerates. stay tuned シ16 -
Manager: we should arrange regular catchups, I have several Monday morning, how about 10:30, that'd be 9:30 your time?
Me inside: dude, we both know I struggle to be up in time for the scrum at 10, do you really think I'm going to be any better at 9:30?
Me outside: How about 10:30 after scrum?
Manager: OK, that works, I have half an hour between meetings
Me: Thank fuck.4 -
I manage a team of engineers.
Toxic Culture Post #2:
Manager: Everybody on your team needs their own swimlane in Jira. Each person's work should be their own lane. When I have a ticket for <Project A> I want to make sure that <Bob> always gets it, all tickets for <Project B> must go to <James>. You'll need to figure out which team member will handle <New Project C> and create their personal swim lane.
Me: That's not really how SCRUM works. Actually, that's not how teamwork works. You're creating silos and we all need to learn how to do these tasks. We're a cross-functional team, and each team member brings their own unique talents to the whole process.
Manager: So you'll create the swimlanes?
Me: No
Manager (to Bob): You'll be devoted to <Project A> from now own. It's the only work I expect you to do. All work for that project will be yours.
Likewise, my manager also reached out to each team member and assigned them specific tasks, furthering the silos.6 -
Send help..
The project we're currently working on:
- an angular codebase that's broken beyond recognition - nothing's working as it should
- user stories are estimated in hours, but estimations are treated as hard facts. Since the app is so broken, everything takes longer than usual and it's almost impossible to consider every potential hardship during refinements, therefore, we constantly need more time than we have estimated
- retrospectives (intentional plural here, since one time isn't enough) are used to discuss why we cannot manage to finish tickets within the estimations
- the design was made beforehand and is extremely inconsistent and inaccessible
- if you open a new ticket, you need to add a reason for why this ticket is needed - in addition to the ticket description..
- The moment you move a ticket to QA, the "Scrum Master" breathes down your neck, shoving new tickets in your face. Despite having to finish up the other two you're still working on
- multiple teams are working on the application, but - of course - communication is overrated.
I could go on, but I'm too tired..
We were supposed to help the client for a couple of months - we're close to a year now and still nowhere near done.5 -
Why does Scrum feel like micromanagement?
I seriously hate daily standup, ours go on for half an hour, sometimes longer and I have to listen to completely unrelated shit I don't know anything about. I cannot explain how disconnected I feel. I'm the only dev working on their website. Some days I don't even need to check in, I have nothing to say.24 -
For the first time I am feeling like.... I hate my job.
Agile and Scrum can be fucked, but at least there is a work methodology. I was hired by a company being run the old school way.
These guys never heard of git??
- Fuck you. We never used git and neither should you.
Client company does not want to give me push/pull access to their gitlab instance??
- Fuck you, you can use our RDP server for that.
Project planning features be damned, they've got email, Teams and videocalls!
Can I develop in peace? Fuck no, I have to give IT support to the guy who hired me.
Our timeline is defined IN A FUCKING WORD DOCUMENT FOR FUCKS SAKE. I can't connect Issues to milestones in a Word doc
Oh, and the customer is running everything on prem. If there is a need to scale up, FUCK ME. I should have specified 20 machines from the get go or gtfo. We're using 2 machines to run 8 different services that are going to be ingesting and computing data.
They want state of the art on a cheapskate.
And I have nothing else lined up at the moment. Although I am soon to renew the contract... This contract binds me with professional responsibility for a project being ran by people who do not give a single fuck about optimizing the work process.3 -
That slow realization that you're hitting burnout due to the toxicity of those in non-technical roles above you is wild. Also, Jira, Scrum, Sprints and all the extra bullshit can fuck right off as well.3
-
RETARD MASTER: So how did you feel about this sprint DEV?
*nothing is planned, new tickets added each day and old ones removed - inconsistent sprint*
DEV: Well, it’s a bit chaotic, but it’s understandable. I’m used to it. Nothing’s to blame here. Client can’t produce their end of the bargain on time.
*3 week later*
DEV MANAGER: So RETARD MASTER gave a feedback. He told me you insulted him.
DEV: Can I please die now? Not funny.12 -
Once upon a time we were normal remote professionals and our sprint meetings were characteristically professional, no more, no less.
Until.
one of our juniors, a Southern sports-bro type, suddenly started saying "SIR" to the scrum master in literally every sentence.
"Good morning sir". "Yes sir." "Thank you sir." "I can do that sir."
SOMEHOW this plague caught on to half of the male members of our team like we're in the military or something. We have ONE veteran and ZERO Indians and I can't think of a logical explanation for why we're suddenly sir-ing each other and people who aren't even high level executives.9 -
Im getting tired of this fucking scrum team.
First of all let me introduce our backend team which takes 3 weeks to add one fucking column to database and in the end turns out they fucked up RabbitMQ RPC implementation so the column is not syncing with our app at all so now we have to wait 2 extra weeks until that will be working. Best part is that backend fucker who fucked up doesnt even feel like hes blocking a feature and would rather sit for extra few days and do nothing until he gets reassigned his pile of shit back to him than clean up his own shit.
Then we have business analytic who doesnt know how to define tasks properly so I have to record each grooming meeting so I would know what to fucking implement because he doesnt even bother to take proper notes. Which results in not fully defined tasks, which results in unexpected behaviours and MR's stuck in limbo for weeks.
Also lets not forget QA guy who doesnt even bother writing scenarios, I as an app dev have to write them myself just to be sure that fucker will test everything thoroughly.
Then we have fucking devs from consultancy agency who apparently have 6 years of experience (I have barely 2) and these fuckers are spamming me daily with the most basic questions. After each grooming they rush to assign themselves tasks which are not even defined properly yet and not even in this sprint, but fuckers are lazy so thy want to reserve easier tasks for themselves. Pathetic.
At least I have a decent senior on my team, but sometimes he patronizes me so much that I start asking me what I am doing in this team.
Fuck this shit, I asked for a 43% raise and if Im not getting it in 2-3 weeks im outta here. Fuckers.5 -
When your team wants to do daily scrum but there's only four of you and you work for different clients.1
-
Had a conference call and one of the guys said something along the lines of "I can handle the load (ticket load)" didn't even thought about it my mouth instinctively reacted with "that's what she said".
A couple of guys laughed but the other few just "wooooow"ed like if I had thrown a 9/11 joke.
This is not a rant perse, just a reminder that if I ever launch my own startup I shall look to hire "joke sensitive" people to make my scrum meetings as awkward as possible.4 -
Scrum master asks how I'm doing and how I'm finding the project I'm working with.
I complain about the lack of documentation and that it kills me (well, kills my brain with increased migraines) due to my Asperger's as I need CLEAR instructions and not ~something~ I need to piece together from asking from 5-10 different people who all know some minor part of the final answer.
"*You* could do the documentation, lankku, while you're figuring it out!"
Just...FML.
And the reason I was trying to find out this one thing related to a completely different repo I have never worked on was because I was trying to write documentation for something totally different that just needs a login redirect from this different repo. <.<6 -
the amount of micromanagement enforced in our scrum routine is getting ridiculous... but the PM seems to be happy with this14
-
I dream of a chat bot that would read my Kanban/scrum boards and answer status queries for me.
Instead of spending 1h13mins (I measured) on average EACH AND EVERY DAY just telling people whatever is written on the story cards, the robot could tell them for me.
Maybe someone will suggest on the comments that people should just read by themselves on the story cards. Yeah, people will ask you where the toilet is while you are peeing on it. That is why we need robot nannies for professional adults.1 -
When scrum master/agile coach sais "I know, I used to be a developer myself." ....
Do they think it makes me trust them and drop my point?
Honestly all I think is "well, plenty of bad devs out there, and there's a reason you'r not doing it anymore"3 -
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?9 -
Long story short I joined this company as a junior after 1.5 years of a break from development. Before that I worked for almost 3 years in the required stack. We agreed that if I do well after 3 months probation period I can ask for a raise.
It turned out that Im doing better than half of my team so 1 week before probation was about to end, I put in my raise request. Got nothing but strong feedback, even managed to burn myself out a couple times.
Now since the request 11 weeks passed. Our HQ which has the final say about the raise is overseas. Im getting excuses about summer: allegedly because of summer some people in the appproval chain have vacations so this process is taking a long time. This is the excuse they are giving to me.
Right now Im getting really pissed off and resentful because this drag is becoming unnacceptable. Also being in a new scrum team filled with total juniors complicates everything a lot. Im not having the best time here. But at the same time I dont have any savings actually am in debts and currenty barely am able to survive paycheck to paycheck to I cant just quit on the spot.
Had I known that they will drag this out that much, I would have applied to other places and presented them a counter offer. Or at least bluffed from the start in order to speed the raise proccess up.
Should I give ultimatum to my manager?
Im hesitant to do that because up until now we had a decent relationship and he seems like a nice guy so I dont want to rock the boat.
Or should I bluff about having a counter offer, so he would speed things up? But what happens if he asks me to forward him evidence of my received offer?7 -
I'm getting tired of coding. Not really the coding part, the dealing with people who tell me what to code and why part. Sort of considering making a move into a scrum master or PM role just so I can get fired when I say "No, we're not changing everything they've been working on in the middle of the sprint" or maybe "Yeah, no we're not going to put in a bunch of tickets to change the UI/UX without first talking to the designers, because that's what they do. Yes, I realize we aren't Facebook, but do you realize we "compete" with them because a huge number of people will compare our usability to theirs? (even if just subconsciously)"2
-
I was in a company (if you can call it that) for 3 months but I didn't exactly have a good selection process and I was even afraid to get paid for the first month. They made me install Hubstaff (or new slavery), I was in a project that mixed too many technologies, we were not clear who was making the decisions and finally they fired me this week, you don't know how happy I am.2
-
Most of the mockery and derisive talk at lunch was directed towards: middle management. - even if they were present at the table.
I too, have struggles with our PO: he was developer but is totally out of our development, what he kinda accepts and lets us do our stuff... BUT from time to time he wants to meddle with our architecture even though he is not even capable of writing more than a sentence into our ticket description, and his only "vision" is the KISS principle. Totally triggers me.
On the other hand I am also part time working as a scrum master and thus get to know the shit show from the other side: sitting between all parties with their particular, contradicting interests - all that shitty "politics" you don't have have to care about if you just code.2 -
Oh my fucking god, we're doing SCRUM, why does every task get stuck in review limbo and take a sprint and a half minimum because of it.
-
Seriously guys, how do you deal when remotely collaborating with lets say not the most motivated and competent devs?
Our scrum team got formed about 6 months ago from leftover devs of other teams, choosing a couple competent devs at the core and other devs who were kinda gotten rid of by their old teams, and after 6 months of working together I can see why.
Situation is that we are 7 devs in our team and 4 of devs are not pulling their weight. They are seniors on paper, but in reality not really.
They rarely take something complex to work on and even if they do, they make sure they take as much time as possible. Two of them are contractors who I imagine decided to treat the job as a paycheck and nothing more. There is no initiative, no push to make things better and in general attitude is to do bare minimum: only what is being asked and then delaying the hell out of tasks.
Im not exaggareting: Im talking about every possible way of dragging out the tasks: delaying communication, sitting around for a few days while not asking for new tasks to work on if they are blocked, also avoiding standups. Working for days on very basic comments in their MR's. Getting "sick" for a couple days on deadline when things get tough, so that someone else would come in, refactor and save the day. Once or twice it could be a coincidence, but nowadays I can already guess ahead of time what kind of trick they will pull now.
Our project is an android app where we have to support few different tablets, so the most recent new trick that I witnessed is devs avoiding hardware delivers, sometimes for months. Idea seems to be if you dont ping your team that you dont have hardware, then you can avoid working on related tasks with that hardware.
Worst part is that they get away with it. Our teamlead is a senior dev who is first time teamlead, doesnt code anymore and doesnt want to rock the boat. He is the type of teamlead who sets arbitrary deadlines, makes it sound that they are urgent and takes a few days off in the middle of chaos just before deadline. Restrospectives don't help at all and if I try to bring up stuff directly to him he tells me to bring it up during retrospectives. We discuss issues, rant a bit ant then continue carying on like nothing happened and nothing changes.
So little by little in the past 6 months we came to this point where 2-3 devs are carrying the weight of the team and are in a constant crunch mode, while others are allowed to slack. Its becoming ridiculous.
Problem is that this is starting to affect our morale. Only way that is left to keep my sanity right now is to pull away sometimes and also slack. Then I come back at full capacity, give my best for a couple weeks until I have to go and fix some basic leftover task that has been purposefully dragged out for 2 months and left unfinished, then I just want to scream and I know that its time to disconnect again.7 -
This is more of an advice seeking rant. I've recently been promoted to Team Leader of my team but mostly because of circumstances. The previous team leader left for a start-up and I've been somehow the acting Scrum Master of the team for the past months (although our company sucks at Scrum generally speaking) and also having the most time in the company. However I'm still the youngest I'm my team so managing the actual team feels a bit weird and also I do not consider myself experienced enough to be a Technical lead but we don't have a different position for that.
Below actions happen in the course of 2-3 months.
With all the things above considered I find myself in a dire situation, a couple of months ago there were several Blocker bugs opened from the Clients side / production env related to one feature, however after spending about a month or so on trying to investigate the issues we've come to the conclusion that it needs to be refactorised as it's way too bad and it can't be solved (as a side note this issue has also been raised by a former dev who left the company). Although it was not part of the initial upcoming version release it was "forcefully" introduced in the plan and we took out of the scope other things but was still flagged as a potential risk. But wait..there's more, this feature was part of a Java microservice (the whole microservice basically) and our team is mostly made of JS, just one guy who actually works as a Java dev (I've only done one Java course during uni but never felt attracted to it). I've not been involved in the initial planning of this EPIC, my former TL was an the Java guy. Now during this the company decides that me and my TL were needed for a side project, so both of us got "pulled out" of the team and move there but we've also had to "manage" the team at the same time. In the end it's decided that since my TL will leave and I will take leadership of the team, I get "released" from the side project to manage the team. I'm left with about 3 weeks to slam dunk the feature.. but, I'm not a great leader for my team nor do I have the knowledge to help me teammate into fixing this Java MS, I do go about the normal schedule about asking him in the daily what is he working on and if he needs any help, but I don't really get into much details as I'm neither too much in sync with the feature nor with the technical part of Java. And here we are now in the last week, I've had several calls with PSO from the clients trying to push me into giving them a deadline on when will it be fixed that it's very important for the client to get this working in the next release and so on, however I do not hold an answer to that. I've been trying to explain to them that this was flagged as a risk and I can't guarantee them anything but that didn't seem to make them any happier. On the other side I feel like this team member has been slacking it a lot, his work this week would barely sum up a couple of hours from my point of view as I've asked him to push the branch he's been working on and checked his code changes. I'm a bit anxious to confront him however as I feel I haven't been on top of his situation either, not saying I was uninvolved but I definetly could have been a better manager for him and go into more details about his daily work and so on.
All in all there has been mistakes on all levels(maybe not on PSO as they can't really be held accountable for R&D inability to deliver stuff, but they should be a little more understandable at the very least) and it got us into a shitty situation which stresses me out and makes me feel like I've started my new position with a wrong step.
I'm just wondering if anyone has been in similar situations and has any tips or words of wisdom to share. Or how do you guys feel about the whole situation, am I just over stressing it? Did I get a good analysis, was there anything I could have done better? I'm open for any kind of feedback.2 -
Recently, our COO left the company and we got a new one. He is, for some reason, a freelancer which I find very odd as a C-level employee.
Anyway, fast forward 3 months and we the scrum master (or project manager), 60% of our dev team, one tech guy responsible for installations and our intern IT support department all got fired.
Now they gave me the decision for a raise, extra training (that they pay) but I have to find/figure out or an e-bike. Does anyone have some advice?6 -
Help. We're starting to feel the effects of unnecessary micromanagement.
We're a small startup. The kind with less than 10 devs spread across different domains. We've been fine with a Kanban approach as the velocity/flow of deliverables don't necessarily warrant a Scrum approach yet.
Our boss has been wanting to adopt Scrum-style sprints, even shoved and assumed that were doing these sprints and demanding Scrum-style reports (and meetings!!!) when they are, in reality,
1) unnecessary
2) a waste of time
Absolutely none of the team members want this. But our boss insists on having it. We like our boss, but lately things are getting out of control
What can we do to mitigate and prevent this?3 -
How to handle a company in which I work as a junior android dev for the past 7 weeks where there is zero mentoring?
I have 2.5 year experience in android dev and then I had a 1.5 year gap. I was looking for a company where I can get back on track, fill my knowledge gaps and get back in shape. So I accepted lower starting salary because of this gap that I had. Me and manager agreed that I will get a 'buddy' assigned and will get some mentoring but nope..
70% of my scrum team with teamlead are overseas in USA and I have just 2 senior colleagues from my scrumteam that visit office only once a week. Ofcourse there are other scrum teams visiting office daily but I personally dread even going to office.
Nobody is waiting for me in there. What's the point if when I need to ask something I have to always call someone? I can do it from home, no need to go to the office.
My manager dropped the ball and basically disappeared after first 2 days of helping me setting up, we had just two biweekly half-assed 1on1’s where he basically rants about some stuff but doesn’t track my progress at all. I bet he doesn’t even know what I’m working on. Everything he seems to be concerned about is that I come to work into office atleast 3 days a week and then I can work remaining 2 days from home.
I feel like they are treating me as a mid level dev where I have to figure out everything by myself and actual feedback is given only in code reviews. I have no idea what is the expectation of me and wether Im doing good or well. Only my team business analyst praised me once saying that I had a strong onboarding start and I am moving baldly forward… What onboarding? It was just me and documentation and calling everybody asking questions…
My teammates didn't even bother accepting me into a team or giving me a basic code overview, we interact mainly in fucking code review comments or when I awkwardly call them when I already wasted days on something and feel like I'm missing some knowledge and I am to the point where I don't cere if they are awkward, I just ask what I need to know.
Seriously when my probation is done (after 6 weeks) I'm thinking of asking for a 43% raise because I am even sacrificing weekends to catch up with this fucked up broken phone communication style where I have to figure out everything by myself. I will have MR's to prove that I was able to contribute from week 1 so my ass is covered.
I even heard that a fresh uni graduate with 0 android experience was hired just for 15% les salary then me. I compared our output, I am doing much better so I definetly feel that Im worthy of a raise. Also I am getting a hang of codebase and expected codestyle, so either these fuckers will pay for it or I will go somewhere else to work for even less salary as long as I get some decent mentoring and have a decent team with decent culture. A place where I could close my laptop and go home instead of wasting time catching up and always feel behind. I want to see people around me who have some emotional intelligene, not some robots who care only about their own work and never interact.6 -
So my team started creating an in-house wiki for all information about our products, methods, scrum, documentation etc. From the beginning we had settled on doing everything in English instead of native language just in case we get a foreign student intern or simply a foreign employee... And now it looks to me that nobody but my team leader and I care about it: half of the documents are either fully native (especially from other part of the team who work on a different project, they have probably never gotten the memo of language choice to start with) or the documents are in some weird-ass combination of English-native which is even worse imo.
I really don't understand why my own team doesn't adhere to the decision though: we're all at least reasonably educated and our country focuses heavily on using English as second language so that should be no big barrier. And why would you want inconsistent documents/code?!
And this is not the first time people don't stick to what is decided for things like formats and language... Getting a bit tired of it tbh...5 -
Does anyone have experience on just "taking" the team organizer slot? My current team meetings are just nuts. A lot of ummms and awkward silences no structure and each runs at least 100% longer than the allotted time. No preparations are made before the meetings. The oldest team member has only been with the company like 1,5 year. I crave more organization1
-
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?
Fun times.1 -
I hate my scrum calls so much. People go into the fucking weeds and the scrum master is so clueless. Doesn't stop them and let people ramble. Jesus christ.
If scrum calls last more than 10 minutes, I think you're doing it wrong.1 -
My team lead wants all tickets reviewed but it takes them forever to review them. The 2 juniors (incl. me) have now 6 tickets in review each.
"Scrum master" (if we can call it that) assigns all tickets upon creation. There are currently no unassigned tickets left in the backlog that I can start with. -
I’m in the middle of a 2:30h SCRUM meeting and the only thing I have to say is that Bill Cosby drinks would be less soporific.
Honestly, why managers can’t just hand out the tasks instead of forcing us to look at them discussing them?2 -
Scrum masters are a joke. I think we should take half of their salary and tack it on to the tech lead and let him run the show.6
-
Returning to tech after 3 years working with agile, training and coaching Scrum, Kaban and XP practices. Applying for team leadership positions. Advice?1
-
So I've been asked if I want to take the role of scrum master along with my job as developer.. I must say that I am quite interested in taking on that role and it's responsibilities, but I'm somewhat scared by the things I read on the internet (especially when combining it as dev on that same team).
Let's hope I don't become the bad guy in this story after some time by being an a-hole of a scrum master lol4 -
I'm having a weird time with my current project.There are many companies involved and we are several teams coordinating with each other. My team was initially very large, for various reasons we were divided into smaller groups and I must say that the transition has been catastrophic.
We are doing SCRUM…sort of. The customer assigns the tasks to be completed at the end of the sprint, the story points are given without full understanding of the implementation and the deadlines are tights. I always find myself rushing to the release day with code that isn't production-ready but since the customer requests it and there's no objection among my superiors (please note, i tell them the deadline is tight) I gotta rush to deliver.
The customer doesn't know what he wants, but if he does know the deadline is unreasonable, or if he has just an idea of what he wants he still demands it... somehow without specifying what kind of implementations is expecting.
The current senior project developer takes everything (any task) as an emergency, it's never possible to defer to the next sprint, it's quite demeaning.
And I'm here wondering if maybe I've missed something, if the project simply lacks method and coordination, if I have more responsibility than I think, if my project leadership is too absent but I know one thing, at the moment I'm in anxiety about the current sprint due date because there is a task that will take longer than expected.
Any advice?5 -
Question about scrum in terms of developer/QA workflow. We have a problem in our team: basically when a dev submits an MR it needs to get 2 approvals from devs and then task is marked ready for qa. Now problem here is that qa takes 2-3 weeks to get to the task and when they do usually MR has merge conflicts and since QA are quite new-ish they have to wait for dev for conflicts to be resolved, ergo rendering the MR unable to be tested until dev resolves the conflicts.
Our teamlead proposes to solve this by forcing devs to rebase everyday (even if QA will get to working on the task 3-4 weeks later). Problem with that approach is that each conflict resolve removes approvals. So I had a situation where in 3 weeks I rebased like 15 times and 5 times I had resolve coflicts and because approvals were lost I had to annoy all devs and ask for reapprovals. And this is only with 1 MR. Now imagine all devs doing rebasing daily and spamming each other for reapprovals. Its not efficient.
Anyone could advice how to solve this issue?7 -
Having some lazy scrum team members and it is getting out of hand. For the past 1 week or so we have one dev who's daily standup written report is: regression. In our test case summary I can't even find her name, which means she is not doing anything.
Same goes for two of our new QA's who joined like 2 months ago. We have like 20 ready for QA tickets pending, but QA is saying that they are doing regression. Yet when I check how many cases they actually covered, it's something that even I as a dev during my first weeks in the company would have completed in a halfday. Right now we have one senior QA guy who is doing all the heavy lifting and I want to change that.
Wondering how to politely call out their bs during standup? It's kinda annoying seeing them covering their lazyness with "regression" for two sprints in a row now :)3 -
Small start-up story:
The company hired independent foreign devs. The tech lead developer has decided to leave (due to some disputes with the boss(es)). The rest of his team are subcontractors/other independent devs that are good friends with the lead dev. We also recently adopted a 'scrum' which they really dislike.
So I guess there is a small change we will have a back-end team in the near future.2 -
What is the point of doing retros and giving feedback, if the fucking scrum master is not going to enforce it?
I hope we can rid of this stupid scrum master position. Don't get me wrong we need managers, but we don't need glorified task readers.2 -
It’s me or Scrum trivialize developer’s skill development? My company replaced almost all the training with Googling and “peer to peer training” in which some junior with no teaching experience prepares a presentation/lesson on some technology and then shows it to others.
Following this logic with all the true crime which I’ve watched I should be a detective.7 -
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 -
How do you deal when you are overpromising and underdelivering due to really shitty unpredictable codebase? Im having 2-3 bad sprints in a row now.
For context: Im working on this point of sale app for the past 4 months and for the last 3 sprints I am strugglig with surprises and edgecases. I swear to god each time I want to implement something more complex, I have to create another 4-5 tickets just to fix the constraints or old bugs that prevent my feature implementation just so I could squeeze my feature in. That offsets my original given deadlines and its so fucking draining to explain myself to my teamlead about why feature has to be reverted why it was delayed again and so on.
So last time basically it went like this: Got assigned a feature, estimated 2 weeks to do it. I did the feature in time, got reviewed and approved by devs, got approved by QA and feature got merged to develop.
Then, during regression testing 3 blockers came up so I had to revert the feature from develop. Because QA took a very long time to test the feature and discover the blockers, now its like 3 days left until the end of the sprint. My teamlead instantly started shitting bricks, asked me to fix the blockers asap.
Now to deal with 3 blockers I had to reimplement the whole feature and create like 3 extra tickets to fix existing bugs. Feature refactor got moved to yet another sprint and 3 tickets turned into like 8 tickets. Most of them are done, I created them just to for papertrail purposes so that they would be aware of how complex this is.
It taking me already extra 2 weeks or so and I am almost done with it but Im going into really deep rabbithole here. I would ask for help but out of other 7 devs in the team only one is actually competent and helpful so I tried to avoid going to him and instead chose to do 16 hour days for 2 weeks in a row.
Guess what I cant sustain it anymore. I get it that its my fault maybe I should have asked for help sooner.
But its so fucking frustrating trying to do mental gymnastics over here while majority of my team is picking low hanging fruit tasks and sitting for 2 weeks on them but they manage to look good infront of everyone.
Meanwhile Im tryharding here and its no enough, I guess I still look incompetent infront of everyone because my 2 weeks task turned into 6 weeks and I was too stubborn to ask for help. Whats even worse now is that teamlead wants me to lead a new initiative what stresses me even more because I havent finished the current one yet. So basically Im tryharding so much and I will get even extra work on top. Fucking perfect.
My frustration comes from the point that I kinda overpromised and underdelivered. But the thing is, at this point its nearly impossible to predict how much a complex feature implementation might take. I can estimate that for example 2 weeks should be enough to implement a popup, but I cant forsee the weird edgecases that can be discovered only during development.
My frustration comes from devs just reviewing the code and not launching the app on their emulator to test it. Also what frustrates me is that we dont have enough QA resources so sometimes feature stands for extra 1-2 weeks just to be tested. So we run into a situation where long delays for testing causes late bug discovery that causes late refactors which causes late deliveries and for some reason I am the one who takes all the pressure and I have to puloff 16 hour workdays to get something done on time.
I am so fucking tired from last 2 sprints. Basically each day fucking explaining that I am still refactoring/fixing the blocker. I am so tired of feeling behind.
Now I know what you will say: always underpromise and overdeliver. But how? Explain to me how? Ok example. A feature thats add a new popup? Shouldnt take usually more than 2 weeks to do my part. What I cant promise is that devs will do a proper review, that QA wont take 2 extra weeks just to test the feature and I wont need another extra 2 weeks just to fix the blockers.
I see other scrum team devs picking low hanging fruit tasks and sitting for 2 weeks on them. Meanwhile Im doing mental gymnastics here and trying to implement something complex (which initially seemed like an easy task). For the last 2 weeks Im working until 4am.
Im fucking done. I need a break and I will start asking other devs for help. I dont care about saving my face anymore. I will start just spamming people if anything takes longer than a day to implement. Fuck it.
I am setting boundaries. 8 hours a day and In out. New blockers and 2 days left till end of the sprint? Sorry teamlead we will move fixes to another sprint.
It doesnt help that my teamlead is pressuring me and asking the same shit over and over. I dont want them to think that I am incompetent. I dont know how to deal with this shit. Im tired of explaining myself again and again. Should I just fucking pick low hanging fruit tasks but deliver them in a steady pace? Fucking hell.4 -
Need advice about switching to contracting.
TL;DR;
So I had 2 years of exp as an android dev, then I had a 1.5 year gap from doing android and now for the past 6 months Ive been doing android again fulltime. Im thinking of switching to contracting due to my debts and boring project and life crushing slow corporate processes in my current fulltime job, so I need tips and advices as to where should I start looking for new contracting gigs and in general what should I pay attention to. If it helps, I am based in EU, but am open to any EU/US gigs.
Now the full story:
Initially when I joined my current fulltime job after a break I had zero confidence, lowered my and employers expectations, joined as a junior but quickly picked up the latest standards and crushed it. Im doing better than half devs in my scrum team right now and would consider myself to be a mid level right now.
Asked for a 50% bump, manager kinda okayed it but the HQ overseas is taking a very long time to give me the actual bump. I have been waiting for 10 weeks already (lots of people in the decision chain were on and off vacations due to summer, also I guess manager sent this request to HQ too late, go figure). Anyways its becoming unnaceptable and I feel like its time for a change.
Now since I have mortgage and bills to pay, even with the bump that I requested that would leave me with like maximum 700-800 bucks a month after all expenses. I have debts of around 20k and paying them back at this rate would take 3 years at least and sounds like a not viable plan at all.
Also it does not help that the project Im working on is full of legacy and Im not learning anything new here. Corporate life seems to be very slow, lots of red tape kills creativity and so on. I remember in startups I was cooking features left and right each sprint, in here deploying a simple popup feature sometimes takes weeks due to incompetence in the chain. I miss the times where I worked in startups, did my job learned nre skills and after 6 months could jump on another exciting gig. Im not growing here anymore.
So because my ADD brain seems to be suited much better for working in startups, and also I need to make more money quick and I dont see a future in current company, I am thinking of going back to contracting. All I need right now is to build a few side apps, get them reviewed by seniors and fill my knowledge gaps. Then I plan of starting interviewing as a mid level or even a senior for that matter, since I worked with actual seniors and to be honest I dont think getting up to their level would be rocket science.
Only difference between mid and senior devs that I see atleast in my current company is that seniors are taking on responsibility more often, and they also take care of our tools, such as CD/CI, pipeline scripts, linters and etc. Usually seniors are the ones who do the research/investigations and then come up with actual tasks/stories for mids/juniors. Also seniors introduce new dependencies and update our stack, solve some performance issues and address bottlenecks and technical debt. I dont think its rocket science, also Ive been the sole dev responsible for apps in the past and always did decent work. Turns out all I needed was to test myself in an environment full of other devs, thats it. My only bottleneck was the imposter syndrome because I was a self taught dev who worked most of my career alone.
Anyways I posted here asking for some tips and advices on how to begin my search for new contract opportunities. I am living in EU, can you give me some decent sites where I could just start applying? Also I would appreciate any other tips opinions and feedback. Thanks!3 -
So we are 8 devs in our scrum team but 2 major refactors felll on my shoulders (initially they were supposed to be fairly simple tasks, but like that malcolm in the middle video 2 tasks became 10 tasks in the past month) and I have been working from 11 am till 4 am for the past 1 or 2 weeks. Just yesterday I worked until 7am. Slept only 4 hours... Trying to play it cool, since I asked for a raise 5 weeks ago and still waiting for answer.
I havent told anyone because partially its my own stubborness of wanting to learn things and not wanting to bother others with questions, but Im starting to loose it.
And all because my pushed initial features resulted in unexpected blockers so scrum team leaders had an all hands meeting and my newly appointed teamlead started shitting bricks.
Meanwhile all other devs pick a low hanging fruit tasks and sit around for 2-3 weeks while I have to do heavy lifting alone with some guidance from other devs.
We dont even have QA resources. We have 2 new hires who will be useful maybe after 3-4 months and we have 1 QA guy who judging by his output is working part time. Also same guy managed to take 2 weeks of vacation in the past 4 weeks.
So due to lack of QA and due to code reviews taking long time it takes over a week for code to be reviewed and tested and each time if a blocker happens I have like 2 or 3 days to rush until end of the sprint in order to fix the feature for upcoming release or I have to move tasks to another sprint and feel bad about spillover.
Imagine implementing something in 2 weeks, just to wait for another 1-2 weeks for changes to be reviewed/tested and now having to fix blockers. And then teamlead comes up to you with being surprises how come shipping of this is taking longer than 4-5 weeks? Dude, I did my fucking part in 1-2 weeks, its not my fault that other devs perform code reviews late and they dont even launch the app to test. Its not my fault that we have very limited QA resources and our only QA guy is not even testing out everything properly.
Seriously Im starting to fucking loose it. We are basically 8 devs in a team where 2 people are doing all the heavylifting. -
I started my first IT job nearly 2 years ago, and since then I have already had 4 different "project/scrum" managers for my team.
I don't know how I should feel about it3 -
What should you do if the project manager is not assigning you any new work after the backlog already has been cleaned up?
I currently work as a junior front-end dev. For the past few weeks, the 2 juniors (incl. me) are lacking tickets. For example, I got 2.5 days of work assigned during our 3-week sprint. We already followed some courses, read some books & created some designs for upcoming features (that have no "functional specifications" written down).3 -
I have to participate in this retarded conference for 2 days and then I will have to join this fucking summer gathering on my weekend and that will take whole day. Fuck this fucking corporate bullshit. Better give me a fucking raise or better yet start fucking managing this scrum team because half of devs are not pulling their fucking weight.
Fucking BA too lazy to update issues with new details after grooming so each time I pick a new task I either have to somehow remember what we discussed weeks ago or I have to spam you with questions so you would run around like chicken without head while gathering answers to questions that were already discussed because you are too lazy of a fuck to compile notes. And even that is not enough, my merged MR's apparently dont cover all the use cases because your'e too incompetent to even figure out how our app works and define properly the task.
And then theres supposedly a techlead dev whos not taking a ticket when theres 3 days left till end of the sprint and he goes: "But a task spillover will happen!!!". Yeah so I guess just sit on your ass and wait for new sprint so you could pick yet again another low hanging fruit task and marinate it for weeks.
Motherfucker I checked your MR's in the last 6 weeks you did 1 week worth of work. You are a techlead but your only dev colleague is asking us for help daily because you dont even help him Fucking lazy and incompetent bastard. -
I'd like to learn SCRUM/AGILE/JIRA or whatever management thingie is available out there that helps to manage projects in a team. anybody can share any link/blog/video? thanks6