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
-
This story is 100% true.
I got hired onto a team of construction workers to build a house. We set up a meeting with Management to find out what kind of house they wanted us to build, where’s the floor plan, what it’s going to be used for, who it’s for, etc. Management said that they didn’t know all that, we should just get started. They told us that we were going to use “Agile” which means that we just work on small deliverables and build the thing incrementally.
The developer team lead argued that we at least need to know how big the thing is going to be so that we can get started pouring the foundation, but Management told him they just don’t know. “What we do know,” Management said, “is that the house is going to have a bathroom. Just start there, and we’ll know more when it’s done. You have two weeks.”
So we just bought a port-a-potty, and screwed around on the internet for two weeks. Management was outraged. “You call this a house? This is the worst house ever! It doesn’t even have a tv!”
So we bought a tv and put it in the port-a-potty, attached to an outdoor generator. We were going to buy a a dvd player and get it hooked up to cable, but Management rejected the expense request, saying that they didn’t know if we needed it, and we’d come back to that later.
Management decided that we definitely need storage space, so we bought a boxcar and duct-taped the port-a-potty to it. Then to our horror they set up some desks and put a few miserable business interns in there. It went on like this…
After a few years the boxcar grew into a huge, ramshackle complex. It floods, leaks, it’s frozen in the winter and an oven in the summer. You have to get around in a strange maze of cardboard tubes, ladders and slides. There are two equally horrible separate buildings. We’re still using just the one outdoor generator for all power, so electricity is tightly rationed.
Communication between the buildings was a problem. For one of them, we use a complex series of flag signals. For the other we write notes on paper, crumple the paper up, and toss it over. Both of these methods were suggested as jokes, but Management really liked them for some reason. The buildings mostly talk to each other but they have to talk through us, so most of what we do is pass messages on.
It was suggested that we use paper airplanes instead of crumpled up balls, but the fat, awkward fingers of the Business Majors who inevitably take those jobs couldn’t be trained to make them. I built an awesome automatic paper airplane folder, but once again they couldn’t be trained to use it, so they just went back to crumpling the notes up in balls.
The worst part of all this is that it’s working. Everyone is miserable, but the business is making money. The bright side is that this nightmare complex is done so now we know what kind of building they actually needed in the first place, so we can start work on it. Obviously we can’t tell Management anything about what we’re doing until it’s finished. They noticed the gigantic hole in the ground where the foundation is coming in, but we told them that it’s a cache reset, and they mostly ignore it except when the occasional customer falls in.
I’ll probably be out of here before the new building gets finished. I could get a 50% raise by switching jobs, but Management still doesn’t think I should get a raise because I missed a couple sprints.7 -
"Let's do some pair programming! It will be fun!"
... Fuck no.
Either I start coding and you open a beer, or the other way around. And sure, I do not mind doing each other's code reviews. I respect your feedback.
But I can't look over your shoulder while you misspell keywords. When I write code, I search, try, debug and play at a high speed.
I'm an impressionist/surrealist writing messy passionate functions, breaking lots of things with broad paintbrush strokes before finishing it into detailed perfection. I remember all the places in the code I need to work on, and cover everything with tests.
You're a baroque coder, sometimes even a hyperrealist, with your two-finger 10 wpm typing, writing code strictly line-by-line, decorating every statement with the right checks & typehints in advance. You can not keep two functions in your head at the same time. You write tests reluctantly, but you hate that I barely plan. You plan everything, including your pee breaks.
As a coworker I respect you.
But there is no bigger hell than pair programming with you.14 -
The following dialogue is inspired by a career of similar conversations.
--
Manager: What's the status?
Dev: It works, but I just found a security hole. That contractor did not sanitize all the different kinds of user input and someone approved the PR with "LGTM." A customer can run malicious code and get us in real trouble. I'm patching this now.
Manager: How long with that take?
Dev: If done right, 4-5 days. If done fast, I can squeeze 3.
Manager: Let's not boil the ocean. We need to ship by tomorrow so we can't spend too much time on something that we can fix later.
Dev: Surprising deadline aside, I made a Jira workflow state called "Later" for when you close the ticket after this conversation.
Manager: We need to talk about how your negativity impacts the team.
Dev: Sorry. I just don't want to knowingly release a critical vuln.
Manager: We can introduce a procedural change and have ops vet the documents. We already have a screen where they can approve what uploads get to the customer. If we let a bad egg through, then we'll right-size according to customer feedback.
Dev: Lawsuits are feedback?
Manager:
Manager: I mean
Dev: *Googles "brain parasite symptoms"*
Manager: Hey. The kind of thing you are worried about probably won't happen soon, and we'll be able to handle things in the short term.
Dev: Because it's better that our staff have unprotected sex with the Internet on our corporate network than use a few more days to move everyone along worry-free?
Manager: It's a calculated risk. We're Agile after all, right?
Dev: When it's an excuse.13 -
I recently joined the dark side - an agile consulting company (why and how is a long story). The first client I was assigned to was an international bank. The client wanted a web portal, that was at its core, just a massive web form for their users to perform data entry.
My company pitched and won the project even though they didn't have a single developer on their bench. The entire project team (including myself) was fast tracked through interviews and hired very rapidly so that they could staff the project (a fact I found out months later).
Although I had ~8 years of systems programming experience, my entire web development experience amounted to 12 weeks (a part time web dev course) just before I got hired.
I introduce to you, my team ...
Scrum Master. 12 years experience on paper.
Rote memorised the agile manifesto and scrum textbooks. He constantly went “We should do X instead of (practical thing) Y, because X is the agile way.” Easily pressured by the client to include ridiculous (real time chat in a form filling webpage), and sometimes near impossible features (undo at the keystroke level). He would just nag at the devs until someone mumbled ‘yes' just so that he would stfu and go away.
UX Designer. 3 years experience on paper ... as business analyst.
Zero professional experience in UX. Can’t use design tools like AI / photoshop. All he has is 10 weeks of UX bootcamp and a massive chip on his shoulder. The client wanted a web form, he designed a monstrosity that included several custom components that just HAD to be put in, because UX. When we asked for clarification the reply was a usually condescending “you guys don’t understand UX, just do <insert unhandled edge case>, this is intended."
Developer - PHD in his first job.
Invents programming puzzles to solve where there are none. The user story asked for a upload file button. He implemented a queue system that made use of custom metadata to detect file extensions, file size, and other attributes, so that he could determine which file to synchronously upload first.
Developer - Bootlicker. 5 years experience on paper.
He tried to ingratiate himself with the management from day 1. He also writes code I would fire interns and fail students for. His very first PR corrupted the database. The most recent one didn’t even compile.
Developer - Millennial fratboy with a business degree. 8 years experience on paper.
His entire knowledge of programming amounted to a single data structures class he took on Coursera. Claims that’s all he needs. His PRs was a single 4000+ line files, of which 3500+ failed the linter, had numerous bugs / console warnings / compile warnings, and implemented 60% of functionality requested in the user story. Also forget about getting his attention whenever one of the pretty secretaries walked by. He would leap out of his seat and waltz off to flirt.
Developer - Brooding loner. 6 years experience on paper.
His code works. It runs, in exponential time. Simply ignores you when you attempt to ask.
Developer - Agile fullstack developer extraordinaire. 8 years experience on paper.
Insists on doing the absolute minimum required in the user story, because more would be a waste. Does not believe in thinking ahead for edge conditions because it isn’t in the story. Every single PR is a hack around existing code. Sometimes he hacks a hack that was initially hacked by him. No one understands the components he maintains.
Developer - Team lead. 10 years of programming experience on paper.
Writes spaghetti code with if/else blocks nested 6 levels deep. When asked "how does this work ?”, the answer “I don’t know the details, but hey it works!”. Assigned as the team lead as he had the most experience on paper. Tries organise technical discussions during which he speaks absolute gibberish that either make no sense, or are complete misunderstandings of how our system actually works.
The last 2 guys are actually highly regarded by my company and are several pay grades above me. The rest were hired because my company was desperate to staff the project.
There are a 3 more guys I didn’t mention. The 4 of us literally carried the project. The codebase is ugly as hell because the others merge in each others crap. We have no unit tests, and It’s near impossible to start because of the quality of the code. But this junk works, and was deployed to production. Today is it actually hailed as a success story.
All these 3 guys have quit. 2 of them quit without a job. 1 found a new and better gig.
I’m still here because I need the money. There’s a tsunami of trash code waiting to fail in production, and I’m the only one left holding the fort.
Why am I surrounded by morons?
Why are these retards paid more than me?
Why are they so proud when all they produce is trash?
How on earth are they still hired?
And yeah, FML.8 -
Manager: I need estimates for your sprint tasks
Me: I've never done any of this before, my estimates have no context and are effectively worthless
Manager: don't worry it's just for the Jira board.
Me: OK *gives estimates*
End of sprint comes...
Manager: Why isn't task X done?
Me: *sigh*
I don't miss my old job :)
3 -
Let's build a house with no blueprint, no idea how it should look but have daily meetings about the bathroom... #Scrum3
-
Holy shit balls it works (so far)
-
So I’ve been working on a project... well feature for the past year (yes 12 whole fucking months - anti agile I know)
And today I got to merge that bitch of a pull request into the current working branch and deploy it to UAT - no conflicts 😵I think I need to put the lottery on tonight!
And some how, by some stupid lucky roll of the dice it just works.
I have never felt so afraid and delighted in my life!6 -
Agile in practice.
I finished my story with 3 days left in our 2 week sprint.
Me: What story should I pull in next?
PM: Story <number> to add <new feature>
Me: ok, sounds good
PM: Will you finish it before our sprint ends?
Me: No, probably will take me 5-7 days.
PM: But it can't spill over, it will make our metrics look bad.
Me: I can't finish it in 3 days.
PM: ....
Me: Can't you just explain the spillover as us working ahead?
PM: It will look bad on our <automated-report>
Me: ....
Me: So don't want me to get started on <new feature>?
PM: ....
Me: <internally sighing> What do you want me to do?
PM: Maybe you can pair program with <Overpaid-Idiot-Programmer> to help finish their story
Me: ....
Me: feelsbadman.jpg15 -
Feeling like I've gone back in time about 15 years!
Just told my CTO about various improvements we could make to the development process. Things like git, continuous delivery, agile project management apps such as Jira, task management such as Gulp, etc.
His response - "never heard of them. I bet they'll pass in a few months. Just another round of fads".8 -
Infinite loop...
Got a story assigned with no requirements listed this sprint. Since I finished the rest already I was like, lets be pro-active and see what it's about during the stand-up.
Me: Hi, I only have story X remaining, what's it about, there are no requirements listed in Jira?
SM: Yeah person Y is going to reach out to you with the reqs.
Me: Ok, when is Y going to reach out?
SM: Y doesn't have time now, will probably be in 2 weeks.
Me: Ok, so why is the story included in this sprint then?
SM: Because they want X implemented this sprint.
(Me wondering if the Scrum Master is familiar with infinite loops, thinking let's try this out)
Me: Ok, if X should be completed, can Y reach out to me with the requirements?
SM: Y doesn't have time now, will probably be in 2 weeks.
Me: Ok, why is the story included in this sprint then?
Stand-up lasted a lil' longer today... Hope the SM got the message not to assign stories without reqs or clear communication anymore.4 -
Fellow developers,
For all people asking u to be partners of their "billionaire" idea, and to be paid from revenue ONLY when the plateform goes live or shit like this, BEWARE.
For all of them i had the same answer: "ok, ill share with you the project, but until it goes live, i am the only one who is giving sacrifice, and since we are partners, i want us both to do same level of sacrifices in order to deserve later the share of revenue... That being said, u have to pay the hours of devlopment, all of them, and when it goes live, from the revenue ill get, ill pay you back what you paid on dev cost"
It is the only way to be really even...
And if he refuse, ask them again "why? I taought u where 100% sure that your idea will work and become a billionaire why u think it is risky tp pay few thousands????"
... Now he is having second thaughts24 -
Me: Hey Guys we've been working on this application(project 1) for 4 months and i think we're almost done.
Owner of Company(Not My Boss): CooCook4Choo we moving you to project 2, forget about the previous one.
2 months go by, project is completed.
Boss: I've got another project for you
Me: Awesome!
1 month later...
PM: We're moving you back to project 1
Me: Why?
PM: Our senior dev resigned, we only have junior Devs and we need a lot of help before deployment next month.
Me: Why am i moving back to a project i was taken off of
PM: Where an agile company and you will be moved off many projects
Me: **Fuuuuuuuuuuck!!!* Ok i'll need documentation of everything that happened in the past three months, the current issue, what the current sprint revolves around and A demo of what has been added.
PM: Relax, I've got a lot of work myself, you will get them soon.
2 days later, still don't have what i need, PM is on vacation.
Me: Guess i don't have any work to do.3 -
worst part of working in scrum: trying to remember what you worked on Friday for Monday morning's stand-up meeting.2
-
Is anyone getting any actual value out of them? As much as I dig agile some of the rituals plain just don’t work.
Fight me!
13 -
No, I do not wish to work on your Scrum-managed project.
I do not wish to contribute to the Taylorism of my profession.
I do not wish to be an interchangeable cog in your software sausage machine.
I do not wish to be tracked by some pointless metrics like a call-centre worker.
I do not wish to bust my tight, cute ass to sprint after some idiotic management request that could have been factored in earlier.
I do not wish to obtain some piss-ant qualification that "authorises" me to do my job.
I do not wish to be party to your lie that technical debt will be avoided by refactoring---whatever the cost.
I do not wish to contribute to the death of software engineering to have it replaced by software development.
Agile? Sure. I can pick up the phone and talk to the client, users and fellow devs. After all, that's what it FUCKING MEANS. Communi-fucking-cation.
See that burndown chart? See your anus? Know what's happening next?
Fuck Scrum and every fucking bottom-feeder that is scamming a living by promoting it. You're killing this business.
Hugs and kisses,
Platypus15 -
I can assure you there's nothing agile about an all day meeting that definitely doesn't require every dev to be there. Industry is weird.3
-
When you move from one "agile" company to a truly agile company. Wow. Productivity has gone through the roof!2
-
team is hiring interns and one candidate put “googling” on their resume as a skill - appreciate the honesty7
-
devRant is awesome, but Disney also manages to light-up my day.
This is how Wall-E became a beloved member of our team, and helped me put a smile on my face throughout a very frustrating project.
It all started in a company, not so far far away from here, where management decided to open up development to a wider audience in the organization. Instead of continuing the good-old ping-pong between Business and IT...
'not meeting my expectations' - 'not stated in project requirements'
'stuff's not working - 'business is constantly misusing'
'why are they so difficult' - 'why don't they know what they really want'
'Ping, pong, plok... (business loses point) ping, pong'
... the company aimed to increase collaboration between the 2 worlds, and make development more agile.
The close collaboration on development projects is a journey of falling and getting back up again. Which can be energy draining, but to be honest there is also a lot of positive exposure to our team now.
The relevant part for this story is that de incentive of business teams throughout these projects was mainly to deliver 'something' that 'worked'. Where our team was also very keen on delivering functionality that is stable, scalable, properly documented etc. etc.
We managed to get the fundamentals in place, but because the whole idea was to be more agile or less strict throughout the process, we could not safeguard all best-practices were adhered to during each phase of a project. The ratio Business/IT was simply out of balance to control everything, and the whole idea was to go for a shorter development lifecycle.
One thing for sure, we went a lot faster from design through development to deployment, high-fives followed and everybody was happy (for some time).
Well almost everybody, because we knew our responsibility would not end after the collection of credits at deployment, but that an ongoing cycle of maintenance would follow. As expected, after the celebrations also complaints, new requirements and support requests on bug fixes were incoming.
Not too enthusiastic about constantly patching these projects, I proposed to halt new development and to initiate a proper cleaning of all these projects. With the image in mind of a small enthusiastic fellow, dedicated to clean a garbage-strewn wasteland for humanity, I deemed "Wall-E" a very suited project name. With Wall-E on board, focus for the next period was on completely restructuring these projects to make sure all could be properly maintained for the future.
I knew I was in for some support, so I fetched some cool wall papers to kick-start each day with a fresh set of Wall-E's on my monitors. Subsequently I created a Project Wall-E status report, included Wall-E in team-meetings and before I knew it Wall-E was the most frequently mentioned member of the team. I could not stop to chuckle when mails started to fly on whether "Wall-E completed project A" or if we could discuss "Wall-E's status next report-out". I am really happy we put in the effort with the whole team to properly deploy all functionality. Not only the project became a success, also the idea of associating frustrating activities with a beloved digital buddy landed well in our company. A colleagues already kickstarted 'project Doraemon', which is triggering a lot of fun content. Hope it may give you some inspiration, or at least motivate you to watch Wall-E!
PS: I have been enjoying the posts, valuable learnings and fun experiences for some time now. Decided to also share a bit from my side, here goes my first rant!
3 -
"A well defined problem is a problem half solved."
~ Charles Kettering.
Feel like crying on hearing this when the product feature requirements change in so aGiLe way.3 -
Six people(4 engineers, 2 managers) in the room, it took fucking 45 mins for daily scrum/standup meeting. Seriously, why do you want talk about every line you wrote?
I excused myself after 35 mins.7 -
Management said "we are agile"...now they ordered us to do changes in production server in daylight...I'm seriously think said FRAGILE...3
-
Looking at one particular job ad
“Experience with agile”
“Excellent knowledge of agile frameworks”
“Work with agile software development team”
Basically in the first few paragraphs it mentions agile about 10 times.
Then the first bullet point in the essential column
“Must have experience working to tight deadlines”
D’oh3 -
Delivering next 6 month’s product roadmap to CEO, other directors and senior management.
I know it’s all going to change.
They know it’s all going to change.
I know they know.
They know I know.
No words are spoken. -
I fucking hate estimating time.
I appreciate that agile is better than any planning type before it, but HOLY SHIT is estimating time a fool's game.
I've been at this over a decade now and I'm still like.. 50% accurate at best. The complicated shit is seldom obvious, and usually if I think something will be complicated it ends up being very simple once I dig in.7 -
Client: we are using Scrum. Next week we have sprint review organized by the project manager.
Me: it’s not Scrum.
Client: in the next sprint we work on a mockup not releasable in production.
Me: it’s not Scrum.
Client: sprint backlog is changed again, at the end we must do everything that is written in the contract with that fixed amount of money.
Me: definitely not Scrum.
Client: we are using Scrum.
Me: Ok.1 -
Today I make a big progress in agile development.
You don't say fuck you. You say your request is in the back log.
😎 -
I just joined devrants and starting my rant here with a dig at the Project Managers I have worked with.
4 -
A coworker during scrum today: "Last week, I worked on the new feature. Also, I have an announcement for everyone: I'm going through a divorce so I moved in with my parents and will be working remotely for a while. I have no blockers...except for the divorce."1
-
New PM thinks it's a great idea to start micromanaging my team's (private) repo names. Can't wait to hear his opinions on our class and variable names! 😭3
-
This is PART 1/2 of a series of rants over the course of a software engineering class years ago.
We were four team members, two had never failed a class, I’ll refer to them as MT and FT, male and female top students, respectively, and an older student with some real world experience who I’ll refer to as SR.
Rant 1: As I was familiar with the agile methodologies I became the Scrum Master and was set with the task of explaining it to the team members, SR showed up late and nobody seemed interested in learning new methodology. At this point I knew we'd have trouble as a team.
Rant 2: FT made up her project proposal without informing anybody, which required a real client/product owner. We only figured it out after her proposal was accepted as the project, so we ended up working with fake requirements.
Rant 3: This one is partly my fault. I researched first and then worked, which meant I was the last to turn up my work. In one activity MT pressures me and I agree to a deadline so everyone can send their work to the teacher in a timely manner. Since I was the last to finish, I was also asked to give the doc some formatting, which I did in a hurry so it wasn't the best.
The next day MT and FT start complaining about me, saying I took too long and that they expect me to do better next time or else. At the same time they were stressed and in a hurry because we had to explain the project outline in front of the class and they didn't study.
Turns out copying and pasting all your work in less than an hour means you don’t learn anything. FT actually asked me for help days before and I sent her a website in English, which she wasn't very good at, so she just ran it through Google Translate and called it a day.
Later FT called me rude for interrupting MT in the presentation, which I did because he started making up stuff about the project.
Rant 4: SR expressed his dislike for school through profanity in variable names and commit messages. This caused MT and FT to dislike him. I thought it was immature but if anything it should’ve been reported to the teacher and move on.
Rant 5: I was stuck trying to get the REST API working for the project Admittedly this was my fault, too, because I was pushing for the usage of things nobody was familiar with for the sake of learning. This coupled with SR’s profanity led to drama and the progress was dropped, starting over from scratch.
At this point I stepped down from the Scrum Master role as nobody seemed to listen anymore.4 -
When your team wants to do daily scrum but there's only four of you and you work for different clients.1
-
Gotta love product owners that don't seem to understand agile.
We delivered the set number of items in the sprint we committed to plus a little extra polish. During the last day of the sprint we're spending the time to push all our work to UAT do he can actually perform acceptance testing...
He decides he should chase all of us up on stuff that we never commited to or even mentioned we'd touch.
Had to explain it to him at least 5 times during the day.5 -
Every piece of work I have to do is blocked, waiting on someone else pulling their finger out. 2 days now, and no progress no matter how much I chase. Bored!7
-
Agile Coach: you need to take part in the next quarter planning of the work. Work with your business team to create a healthy backlog. Provide your input to the user stories. It’s a collective effort.
Me: why tf it’s not a collective effort when code breaks and only one dev is trying to fix it while taking in all the heat.
Of course I can’t say that out loud without getting fired.4 -
Attendance at the daily standup [related to a project that hasn't even started yet] is mandatory!
What did you work on yesterday?
An unrelated project.
What are you working on today?
An unrelated project.
What are you working on for the next 3-6 months?
You guessed it: An unrelated project.
Any blockers?
This is interfering with an unrelated project, but when Agile says "jump", you say "how high?"!4 -
Nope, definitely not going to work for that customer anymore. Fuck this shit. At least for this week.
My background: mid-30 years old, some kind of business & IT consultant / lead dev working for a mid sized CRM consulting company, with approx 15 years of experience in development and software architecture, most of the time "thinking" in C#, still learning new languages, being a cloud evangelist and team lead. We usually have customers with customers (B2B/B2C).
Personality type "campaigner" (ENFP-A).
Today the project lead of my client (a big corporation in the energy industry) told me that he still didn't order all the necessary resources for the cloud project. Just to be clear: He's on the client side. We (the architects, one internal and me) told him one month ago what we need for the beginning. Just a few things - an Azure subscription, a license for the CRM platform, and our dev tools.
And now let's guess when the project is planned to begin? Yeah, right: 1st of April. NO APRIL'S FOOL. And guess what? Next Tuesday we'll do the onboarding for the new (external) devs, and NOTHING will be ready. Yeah, just let us build stuff in our minds, and on the whiteboards, because it's an AGILE project, right? We don't need any systems and tools...
And now he sent me the questionnaires which need to be answered before any cloud service can be ordered by the corporate IT. And yes, he didn't answer a single thing, and just meant "Those are architecture questions" (they are not) and (of course) "please provide the answers until Monday morning, so we can FINALLY order the services."
Yeah, you fucktard. Of course it's MY FAULT now. Maybe I should write an email to your boss asking how we can speed things up a little bit...4 -
I'm a developer with scrum master certification but the company wanted me to use their existing google spreadsheet for managing the tasks of 60 developers. I study agile for nothing. Kill me now please. I'm out.5
-
When your product owner tells you to forget about architecture and unit testing, "just push it out"...
2 -
Corporation.
Meeting with middle level managers.
Me - data scientist, saying data science stuff, like what accuracy we have and what problems with performance we managed to solved.
Manager 1: Ok, but is this scrum?
Manager 2: No they're using kanban.
Manager 3: That's no good. We should be using DevOps, can we make it DevOps?
So yea, another great meeting I guess..4 -
The whole point of having a daily scrum is to let your team know about the progress you've made from last day and what you'd be needing to stick to the sprint plan.
So ideally everyone has 30-60 seconds to give a gist of their activities. And a small scrum team would be productive because everybody is on the same page.
Our scrum meetings usually wait for all of us to assemble with our coffees and donuts, sit down, joke, and then agonizingly go over everybody's existential crisis as a developer because of the task they've been assigned to has too many dependencies. And this happens every single fucking day! These "scrum" meetings tend to go for 1 hour. FML!5 -
Some people are really getting high on this Agile shit. Probably because they learned some new bullshit bingo phrases - and it suits them: lots of vapory talk and expensive meetings and others will have to do the work anyway, while they can circlejerk on how to have shorter iterations to improve the time to market, increase the business value, inspect and adapt to faster deliver a minimal viable product - yeah, do the agile transformation, update to the digital age, you noobs. Throwing around some catchy phrases will let you compete with Google? Maybe need some blockchain or machine learning?
While you are clustering your post its, the coders who keep the ship afloat, sit in their legacy code base that's so bitrot they are mainly doing bugfix releases without a single feature for three fucking years. Consider this.5 -
I'm crying-
And idk if I'm crying from it being so funny or so sad...
Forwarded to me by my boss, found somewhere on the internet, creds to who made it
2 -
Scrum Master? More like Scum Master.. The nutjob sends a calendar invite for daily stand up for 30 minutes which extends to 50 minutes.. 50 minutes for a team of 6 people ? Fuck off.7
-
I only wish that my agile team comes up with the task breakup and documents the implementation approach to our project, as good as this kid did, while panning for a party!
img source: reddit
-
When the PO asks for a last second code change right before the sprint review, and now it's your turn to demo
2 -
When an application has tons of security holes and fixes never make it into sprint prioritization because "they're not new features"4
-
Rant time of 'Derp & Co.'
Today I decided that I am going to find another job, I just can't keep with this shit.
They said that use Agile: FALSE.
• Daily (best scenario) take like 1 hour and a half.
• New task enter the sprint and "Fuck you, more task in the same time". This is something regular done.
• "Oh, dev, we need you to check this other project" I am in the middle of my sprint on this project. "But you have to fix this bug here". (3 fucking days the bloody bug) "You are late again with tasks".
• Meeting for fresh sprint: 6 BLOODY hours... nonstop
The workflow is garbage:
• SOMEONE should did all the devops shit on the first sprint, guess what? They did nothing!, guess now who is being blamed for it (not only me, but a few coworkers).
• Nothing is well designed/defined:
~ task are explained like shit
~ times measured wrongly
~ We are in the last fucking SPRINT and still doing de ER of the DataBase cause Oh, apparently no one has work before with SQL (damn you MongoDB! (Not really)) so I am doing my best, but "jezz dev, this is so hard... maybe we can do it WRONG and easy".
~ No one is capable of take responsability of their mess, they just try to push down the problems. (Remember the devops situatuion? Why is.my fault? I came at the 3 or 4 sprint and I am doing backend tasks, I know nothing about devops).
But the big prize, the last one:
• Apparently you can't send whatever you want to the boss, it has to pass a filter previously of coordinators and managers, hell yeah!
And I am an idiot too!
because I see that we can't reach our schedule and do hours on my spare time!
This is because there are a few good coworkers who probably ended with my unfinished tasks... and they are equaly fucked as me...
This is just the tip of the iceberg. I am not a pro, I am not a full stack developer and still need to learn a lot, but this is just not normal, eight months like this...3 -
Haha, today I learnt that agile doesn't just stop in the enterprise with SAFe (Scaled Agile Framework), management has continued the theme in my new company with Lean-Agile Center of Excellence (LACE) and Agile Release Trains (ARTs).
Software development in 2021...9 -
My coworkers just invited me to a "scum meeting" and that's the most accurate meeting invite I've ever received.1
-
One Pro Tip for all developers :
(in my experience - a short story)
Our team chose agile development. We have items to deliver each sprint.
I was the guy who would always slip in my tasks due to issues that would pop up.
It was due to my own faults, I was less careful and failed to concentrate on one single item when I was working.
I started slipping a lot and my manager started questioning me on my performance. I tried a lot of productivity apps and other methods. Nothing seemed to change my life.
One day, An experienced person in the team said to me,
"Start Going to the gym" and it'll change everything.
I enrolled to the nearest gym and started working out every morning. Had sore arms /legs in the first few days. Nothing seemed to change.
After one week, my work patterns changed. I automatically started to work with a lot of concentration. I still don't know how things changed.
After 2 weeks, everything was completely different.
I was able to complete my sprint tasks in the first few days and started contributing to others work. Got a lot of recognition. My work was recognized a lot and my manager appreciated me.
So this is a real life changer folks.
"start hitting the GYM", and it'll change your life.
Please try it out and tell me how your work patterns change.4 -
Broken teams,
define Agile principles in 2 lines :
Take 2X to your velocity,
and work 80hours a week ;)3 -
In "Sprint Planning", the team is supposed to come up with stories, break those down into tasks, estimate those tasks as a team, then let devs choose what tasks they want to work on based on the stories pulled into that particular sprint.
Instead, our manager creates the stories. He assigns the stories to each developer and then has that developer announce his theoretical tasks (without any research on feature's or project's requirements!) in front of the entire team. So, when I say, "I think it will take me 6 hours to implement this feature", he says, "6 hours? I think it will take 3." and then types the estimate as 3. I have so much rage when that happens. Then we continue to sit in the room for 2.5 hours where we go through this long data entry mess of him typing out tasks and second guessing estimates. There is no team deliberation or collaboration, its whatever the manager says.
While there are many issues I take with this approach, my pet peeve would be the second guessing of the estimates. It would make sense for teams members to second guess estimates as long as they are the same teammates who have the ability and possibility to take on the tasks themselves.
But I disagree with a manager seconding guessing an implementation feature that "I" definitely have to do alone, and they do not possess the immediate knowledge to implement it themselves.5 -
Me : There is a hotfix needs to be done.
Boss : So what ?
Me : Its assigned to you from last 2 weeks and deadlines are near.
Boss: (speaking politely) oh.. is it? Can you take a look ?
Me : .. -
Before 2012, I always worked in cubicles and had weekly status meetings. In 2012 I moved to a big city and learnt there was something worse than cubes: the open work plan. Marketed as a way to increase coloration, the open work space is really just the result of real estate prices being expensive in cities and how desks are cheaper than 3-cube walls.
Up until 2013, we'd usually just have the weekly status meeting. Here are your tasks for the week. I'd do them at my own pace. Some days fast, some days slow, but they'd all get done by the end of the week and I'd proudly go down my list of stuff I had done.
Since then, it's all been "agile" and "stand-ups" every. fucking. day. The work is endless. A Product Owner once told me that stand ups weren't suppose to be status meetings; that you were only suppose to say if you're blocked or need help. But in every place I've worked at, they're daily status reports. You have to preform every day.
I really hate IT today more than ever. I miss the cube. I miss the weekly status reports. Today things are so high stress and higher paced and the work is endless. You can't even really pace yourself anymore.2 -
How do you guys prevent yourself from overworking? With deadline pressures I feel like it is very easy to work more than your regular 8 hours22
-
On a scale of 0 to who fucking cares, how important is it to stand on your feet during dailies?
I really hope this company never hires someone who uses a wheelchair.9 -
I proposed agile training to my company.
I choose a well known coach around here, with good references.
First 3 days were great. After a month he came back for another session and check progress.
This time, he literally fell asleep during the workshop. Several times. He would ask questions, sit down and quietly fall asleep while waiting for our answers.
We were astonished and embarrassed.
He apparently had a very hard working period and could not cope with traveling and working so much. He apologized some day afterwards and didn't charge us for the day.
He never came back. The team didn't take it very well and my reputation was compromised, as well as trust in the methodology I think.
I kept saying that everybody can have a bad day, but it was probably just to defend myself and my fucking stupid idea of changing the world.
A real fucking shame. Still I can't believe when I remember this.2 -
We have “adopted” Agile as our development process. Now I will be honest that I don’t know everything about Agile because I am very new to developing things in a professional setting. But the person who has been the advocate of Agile always starts his sentences with: “Whatever I have read about Agile..”
You can understand why I don’t get a good feeling/confidence regarding this adoption strategy. Things haven’t changed, just the presence of words like “DevOps”, “Agile”, etc has increased in the morning meetings.11 -
Is there anyone else who works at a company that takes longer to plan sprints than the actual sprints?2
-
You know what's fun? When your client insists you use an agile process with a delivery at the end of each sprint, then proceeds to bitch at each release at the features that weren't implemented yet. The thing isn't even slated to be done until 4Q 2018 and is on schedule/early. Glad I am not on that team . . . yet.
-
Our agile scrum team has finally shattered into two parts.
On the one hand we have front-end guys.
On the other hand we have backend- /dev-ops guys.
The FE guys don't care about the BE guys business.
They don't join pairworking and only noticing things that went bad, when a Backend guy has caused it.
Goodbye fullstack dev-ops team...
I really dislike that arrogant basterds.
Frontend Hobo-Bitches...! -
As I am now in a leading position in the middle of a agile transition:
has anyone got a source for a project done completely with user stories?
I am searching a real life example with already finished stories an active backlog and a documentation.
I just can't wrap my head around it. When and what do you document? In which Form do you document? How are you writing user stories with more content like diagrams and such?
(we use jira and confluence but just started with stories)
I read some articles on the topic and watched some talks but sill don't get the picture.8 -
Agile my ass.
What has become of: "Individuals and interactions over processes and tools"?
A fuckton of rules and processes to do it the 'right' way: tickets, estimations, hours of sprint planning. Yeah, we're so professional we no longer have time to write code.
Note: manifest was mainly full of fluffy business buzzword bullshit (effective sustainable excellence), but one thing resonated:
>Simplicity--the art of maximizing the amount of work not done--is essential.
(I cherish every line of code deleted or unwritten, so it needn't be maintained)5 -
Ok, so we have the Spotify Agile Model now (tribes, squads, chapters, etc). I have seen it implemented in a few large companies, and they seem to be doing ok.
It's just... doesn't anyone worry about the product that came out of this great way of working?
Spotify is great as a service, but it has to have one of the worst usability/success ratios of any modern mobile / web app. You can almost feel the various squads doing their own thing, not thinking about the whole experience.
Doesn't the product count when considering using someone's way of working? Is the Spotify Agile Model the project management equivalent of Twitter's Bootstrap?5 -
Since I started working at my current job, I've been growing to admire agile development more and more (or the ideal at least) to the point where I manage my LIFE with an agile perspective now!
It honestly works so well! 😁3 -
Agile coach Agiling: We shouldn't need code reviews as long as there is pair programming.
Me Internally: bad code + bad code doesn't make good code :( -
The team in our office was forced to have, and I'm not kidding, TWO hours long agile meetings EVERY day. That's right, only 6 hours a day for work. Crazy managers
-
My boss thinks we're "Agile" because we spend 30 minutes every day talking about what we did, what we're doing and discussing every single imaginable outcome of life.1
-
Fuck me I'm pissed. This sprint, my tech lead has been away and a senior dev has been covering for him. We plan a load of work and distribute stories and we churn threw it quite well. However, my senior dev says let's not deploy until all the works done. I was like, how is it going to be tested? He was like well it will be fine because it's all one test. Bs. We now have 2 days left, tester is getting stressed because they don't know what to test or what's been finished. Scrum master is asking why all of it should be tested at the same time and I'm here like this is fucking dumb. Also the tester decided to start testing with the most complex piece of work, rather than prioritising.
Starting to wonder if I'm just the outsider or whether no one understands that granularity is better.2 -
This is PART 2/2 of a series of rants over the course of a software engineering course years ago.
We were four team members, two had never failed a class, I’ll refer to them as MT and FT, male and female top students, respectively, and an older student with some real world experience who I’ll refer to as SR.
Rant 6: After the previous drama MT built the groundwork for the project without allowing us to intervene for a week. When he finally disclosed his code he gave us tasks and I was stuck unable to run the new project, due to the friction with MT I asked SR for help which took a couple of days. MT accused us of not wanting to work and claimed he’d just do everything himself. I continued working on the task improving MT’s code and committed the work, which surprised MT and told me I didn’t have to do it. He ended up complimenting my code and complained less about me as a result.
Rant 7: MT kept giving SR flak for not working and took him out of the repo, which I promptly forked just in case he tried anything scummy. SR was indeed working on certain things, but he wasn’t listening to MT’s demands, there was no team coordination. I had to act as a proxy and push some of SR’s changes myself while informing him of the state of things.
Rant 8: When MT finally added SR back and some of the tasks were cleared up, FT didn’t cooperate. She seemed to have zero initiative and always relied on MT to tell her what to do, which didn’t include coordinating with SR to get the front-end templates running. I tried getting them in a group chat but it didn’t work, she just ignored him.
I learned a few things from that.
1. No matter how smart or experienced someone may seem, sometimes people are just petty or take things too personally.
2. Top students are sometimes too focused on their grades and disregard depth of knowledge and work quality.
3. A bad team at college can somehow make something acceptable if everyone works on things that add some kind of value.1 -
Any dev who is asked to give “deadlines” then cried about how it’s “waterfall” and you cannot produce business requirement deadlines in agile methodology needs to stop being dependent on terminology and learn that part of programming is proper estimation.
Milestones, business deadlines and agile can go-exist. Anyone who says they don’t, then cries “waterfall” when asked to produce deadlines greater than 4 weeks out, please never work with me11 -
Prof - Students, from now If someone asks you what you did yesterday, explain every minute detail of the task... Use fluent English, use rich vocabulary and MOST IMPORTANTLY -- if you were not able to complete your plans, make sure the other person knows it wasn't UR MISTAKE.... Don't forget to call out things that u asked for but will be delayed due to "unavoidable circumstances".
Make sure you take atleast 2 mins to finish. At the end greet everyone by saying "That's it".
-
HOW TO BECOME EFFECTIVE STANDUP SPEAKER -
Management: let's be agile... we can all meet and discuss a project that will take more than likely 6 - 12 months but you guys can estimate and create a road map....
Engineer: I'm not sure you understand agile3 -
We estimated out how long a new project was gonna take using story points. It wasn't too big and the estimate came out to two months. We discussed it and it seemed to be all good.
Later on someone pointed out a Quora question where my boss asked why it would take so long to develop such a project.
My boss trusts people on Quora more than his own employees.2 -
Product Owner.
Not Product Liaison.
Not Product Buddy.
Not Product Suggester.
Own it. Bend it to your will. Make it better or sunset it and build it again. But don’t be a wet noodle and say “I’m just following orders”. You give the orders, you own it.3 -
Reminder, include legal language in next project that says if we're using JIRA then we're using JIRA and not a thousand emails with requirements embedded in spreadsheets and PowerPoints.
-
My boss uses agile development so he doesn't has to think about use cases he wants to be covered by the application.
He's just throwing in a "design" (an image that is probably created with Paint) without any further specifications and inconsistent elements, let the developer work two days on it, see the outcome, complains why it's not how he wanted it to be and then starts thinking how the feature should be integrated in the app and notices that his "requirements" from the image could not provide any advantage or usage at all for the user of the application. Asking for clarification before starting to work just leads to spongy statements or silence when he notices that he didn't think through to the end.
Sad is that this has not happened only once but is usually the way a new feature is developed...1 -
Innovation week is upon us! Rejoice and delve into the years of tech debt to be refactored within one week!
Why does anyone pitch "innovation week" as a fun learning experience when a we are doing is cleaning under the rugs? We can barely get typical feature requests out the door in a week due to the overbearing demands of SAFe and Agile ceremonies.
-
The worst of Agile and Sc(r)um: All those people knowing the right way(™) to do it. Endless discussion about useless tooling: the proper use of the custom workflow in Jira, on when and how to create sub tickets. The hour-less meta-discussions on what should be discussed where and when (what's subject of the backlog refinement, retro, etc), the roles: the PO's, what he should do, cannot, the PM's. Who is allowed to pull a ticket to the sprint or not. How many reviewers need to acknowledge a pull request. To and fro. Pointless, but fought with heart and blood, full of sound and fury, signifying nothing.
And everywhere I hear: "In my previous company, we did Scrum like.. and it worked perfectly!"
Some of you might remember my rants on Mr. Gitmaster, with whom I thought I'd made my peace. Guess what? He's now a team member and turning into Mr. Agile - a more severe reincarnation! As our company starts flogging that dead horse of Agility, he seems to feel strong tailwind. Our team lead would constantly cut his monologues, but he's now on holiday, so we have no escape from the never ending: "In my previous company..."
If it was so great, why didn't you stay?
We are not allowed to pull a ticket to the sprint unless every team member is notified? I don't fucking care. If our software fails on customer's machines and I can fix it, I will do if there is a ticket, if it's in the sprint or not. Screw Scrum, if it is getting in the way of it. You can waste your hours discussing horseshit, I want to sit at my desk, deep in the test-compile loop and ship some fucking code.3 -
Doing GUI agile testing with the QA before passing my code to test server. I do this 'cause the QA marked in the past a lot of bugs that aren't bugs because he didn't liked the wording (in spanish there's A LOT of ways to say the same thing), the color of a button or an icon, and this delayed the release of the code a lot of times. So, this way I can change things to avoid unnecessary bugs... if the QA is not so busy XD
-
I find Scrum Masters useless. I'd rather have a developer replace them. Am I overseeing their value? Could someone enlighten me?
I also think that if a group comprised of smart people, things spontaneously happen without needing a handrail to walk along.4 -
I'll be starting a new job soon, and I'm sure there will be a chance to implement some form of process for the dev team to use...
To Scrum or to Kanban?2 -
"Standup" meetings are based on the assumption that standing up gets uncomfortable after a while. In our team however, the meetings are not getting any briefer, we are just getting fitter. Perhaps we should introduce some more uncomfortable position, such as jump-up-and-down daily scrums, or yoga daily scrums.5
-
I was brought into my new position as part of an transformation of waterfall to agile methodology.
We are now running 4 while projects and need to restart the remaining 29 projects using agile principles. The business management type people love agile, but somehow the people inside the current waterfall practices doesn't.
They are afraid their silo work will either expand or not exist thus making it hard to transform the company. Also the company have been subjected to the dead sea effect.
Therfore, the project that is currently in the space of transformation is making my blood boil because people just ain't passionate enough about software.
Either you craft software, or, well you sit and suckle other's money. People suckling should please grow up and start venturing beyond there cozy 9 to 5 and transform to be a professional software doer rather than a BA, DEV, IT GUY.
YOU BASTARDS GET A SHITLOAD OF MONEY AND DON'T DESERVE IT FOR THE EFFORT YOU BRING.
It is your software, own it, be proud of it. Read up to make it better. And as always, the people debugging your code can be a violent psychopath -
Trying to understand why do I have a course on Software Engineering which consists 80% of lectures on what Agile and Scrum mean.
Why can't we get to implement a project and work on agile as we go? 😐😣7 -
I'm absolutely fuming why on earth would someone try to apply exactly all rules of a theoretical concept. I hate those so called "scrum masters". We can't apply all rules of agile we're not machines. There's real life and theory.1
-
I really want my dev team to ask me to go to happy hour so I can suggest meeting at Foo Bar. Though, that may be why no one's asked..4
-
RAT. HOLE. FUCK.
The retrospective is not the time to develop features and designs. We have burnt 45 minutes of an already ludicrously long retro ( 3 hours ).
Too much coffee + this horse fucking shit is geeking me out. -
I've lost sight of the minimum viable product. I've spent months making a product I have to redesign now.
-
Is there a team that works truly productive and happy via an agile (scrum) workflow?
Or does it always distill down to an excuse for a chaotic workflow?
My experience and cynic nature has let me to assume the latter.
(That being said, I never had a dedicated scrum master to work with. So that may be the first of many problems.)5 -
So my team (read: not the team at all) has decided that we are going to scrum. Someone ease tell me it's not as fucking tedious as it sounds. Sounds like it's just more meetings. Especially on this team which is actually already pretty agile. And the way our "certified scrum master" describes the retrospective sounds like it was designed by the type of shitlord PM that forces everyone to wear ugly t-shirts to the mandatory company barbecue for "team building". Please tell me he's just a terrible salesman.7
-
Changing instances to arrays. So we've all had this issue:
Option 1 was the most flexible and abstract option where a lot of functionality could be built on this.
Option 2 was the fastest solution, that would solve only specific problems.
The whole Agile philosophy points to option 2. The problem is that clients will always want to add that functionality in option 1, and changing requirements makes us lose time, the precious resource that managers supposedly cherish, yet they always want us to choose the fast option.
We're at that point where the client wants to add functionalities, but since we already built with the previous requirements in mind. Ugh.
Changing instances to arrays.1 -
We had our first "real" sprint planning yesterday. This was a very superficial planning session, as my manager is, by the looks of it, not to keen on the whole "new process thing". Probably because it's not his way of doing things... or simply more simply put - this way round means he'll need find some new ways to crawl up the CTOs ass!
So glad I'm leaving! -
Dev: [does some weird code to make test pass]
Me: this won't work. Literally the documentation says what you did won't work once we move towards our end goal architecture.
Dev: [shows middle finger and requests merge and somehow managed to get code merged]
.... One Sprint later nothing works...
Dev: [does some weird code to make test pass]
Me: no. You need to solve underlying problem.
Dev: [shows middle finger and requests merge and somehow managed to get code merged]
.... One Sprint later nothing works...
Me: please stahp
Dev: [shows middle finger and requests merge and somehow managed to get code merged]
Me: WTF man do your fucking job
Scrum Master: stahp lowering our velocity
Me: wut? 😒2 -
It's done. Agile has taken over my life. The other day I looked outside and thought, "As a user, I can stand on my lawn without my feet disappearing." And that's how I decided to mow my lawn.
-
What is the point of removing code that will literally be added back in on another story? I just don't get it. I am in the code. It took two seconds to fix it but because it is not part of the story that i am working on someone is going back and ripping it out even though the next story is to put it in. Don't fucking complain to me because we are behind on this fucking project.
2 -
I'm at that point where I want to lash out at our team for not finishing a sprint. I've been doing the scrum master/dev role for months now and each sprint is incomplete since we have started the agile way.
Most of my team members are seasoned senior devs and my team's downfall are caused by not acting as a team. I'm the youngest in the team and have been acting as a babysitter for them.3 -
My company misses the word agile so much, now we are deploying 3-4 times to prod in a day 🤦🏽♂️🤷🏽♂️5
-
What is your opinion on Agile?
I was studying through my textbook for a test tomorrow and the Agile Philosophy section sounded like a Team Rocket manifesto at some parts:
Responding to change over following a plan
Individuals and Interactions over processes and tooks
Working software over comprehensive documentation
Customer collaboration over contract negotiation.4 -
Everytime I applied long leave, my client and PM will plan for important feature, but they say start the sprint and for other new people i have to give KT, and they will take care. I know how that will screw up the system. So at the time it's nightmare late night at office, in office time KT, no weekends, stand-up for 1hr(every time QA will ask, what we get after this sprint). Stupid clients changing the requirements after stand-up.
Everytime code base screwed and need to refactoring. So as much as possible core functionality I'll complete and only bug fixing for newbie. I hate those days. -
We have decent linting on our codebase which covers off code quality and style.
We also have a developer who insists on making code reviews about formatting and spacing rather than functionality even tho we've tried in multiple ways to say:
- our linting covers it, if that's happy we should be (and the rest of the team is)
- it's a waste of time doing it
- it wastes the time of the team reading it
- the noise it generates makes it hard to see any legit comments
I swear to god if I see another comment saying "new line" i will scream. -
So... My friend got Agile Carpet Development.
And this is the example of one being fixed on the fly.
3 -
My teammate doesn't understand that the quantity of lines/method that he does in one commit nor the number of commits he does in one day translate directly into the quality of his commits.2
-
New bossman is looking for KPIs.
We're an agile team who build a back end system for a large corporation. Specifically the system we build is used by the sales guys when they are putting through a sale. I have no idea where to start with KPIs.
Can't measure number of sales as that's down to the salesmen. Can't measure speed of sale as again that's down to the salesman and how much they chat.
Any ideas?8 -
If you're always too busy doing the wrong things the wrong way, you will never have time time to do things right
-
I hate project managers trying to stay relevant to a agile development methodology. Our PM doesn't care if we are working and providing value to the customer, only about checking off his Project check boxes.
tech lead CANCELS Monday stand-up becuase they cannot attend. and I work and status and update my tasks in or virtual task board. I forget to send a message mentioning I'll be kissing Tuesday standup. Then he sends me emails like the following sent to me, my manager, and my tech lead: "please remember to notify your team if you cannot attend the standup, and to send an agile status to the team. This is something that is required and not optional. We are trying to firm up all stories and tasks and need to hear a status. We are in week 1 of iteration 4.3. Thanks."
I'm coding and delivering value to the customer. Wtf are you doing dude? -
Our team moved to scrum a while back. But everybody still does story point estimation by mentally assigning 1 story point for each day of work it would require. :/
On top of that, management compares the performance of two *different* scrum teams based on the story points they finish in a sprint. :// -
Demo driven development.
Fucking nightmare.
Did a simple search for TODO Statements in the code and almost fucking spilt my coffee.
And the best part, they will demo most of this in Sprint review as done.. WTF.
Done means "Ready to Release" not "Ready to Demo".2 -
I had a gentleman tell me I was overqualified, and then proceed to ask me for help with Agile software (jira)! 😂 I gave him my card!
-
I really hate all kinds of tattle that sweeps the hallways of corporations, the gossip behind one's back, BUT this colleague of mine starts pissing me off. Recently joined that team where he should support us getting the Agile thing going. And he can go on for hours of how it should go and how flawlessly it worked in his previous company - all that needless meta talk - so much that a team member jokingly even said: yeah, shut up asshole. But he is all talk. When the name of a library was dropped his experience in using it went to upstream patches. His Linux experience lets us speechless. He is so convincing, I'm even doubting my accusations. Yet his only contribution in code wouldn't show and other team member wasted hours upon hours to recompile plugins to show that shit. Man, just leave us alone watching your youtube live-streams so we can get the shit done.
-
The company i work for is getting into scrum. Hired consultants, product owners and scrum masters. First action was 'lets spend 2 days in meetings estimating the rest of the project'.
Agile as fuck3 -
And again some "evangelists", saying certifications and training, start talking a hit about some method or practice unchained...
How the fuck people don't say the problem with borderline charlatanism...
If Scrum doesn't work it means you're not doing TRUE Scrum...
You should do TRUE TDD (the definition is so long and complex that you can fuck it up) and it'll solve your problem.
Every time is like fucking cults " you have to see the true light, then there is no possible problem... Everything will be solved".
So fucking infuriating!!3 -
I know your code is great and that you learned about scrum a month ago. But I didn't know the scrum training had to say you don't assign yourself tasks, mark them as done and be surprised when other team members haven't done them, two minutes to five the day before a national holiday (yesterday).
-
In organised "standup" where people either offer nothing or try to clear up an issue with someone mid way through.. 'nuff said.
-
Can anyone freaking tell me that Agile is still relevant and yet one of the most hated approach??
I'm freaking confused.7 -
When agile is everywhere (including toilets). Do you want me to poop in agile way? 💩💩
What can be the agile way of shitting?
2 -
So, our project is making the transition to the cutting edge Agile methodology (hello, 2005 called).
From what I see, I'm starting to believe that we're also changing our target from delieverin software to deleivering meeting botes and meeting preparation docs.6 -
Lead dev asks me to take on the restful api aspect to a new internal tool UI I have been building. Happy for the challenge, I spend the 4 days (half of that in my own time), writing out 1k lines of C# that I endeavoured to keep clean, thoroughly decoupled and something I can be proud of.
I give regular updates.
This morning he responds to my last update “we already have most of that code in place”.
This stuff happens a lot. Back of a fagpacket planning and then cries all around when it INVARIABLY goes wrong.
Does this kind of bullshit happen in a properly organised, Agile team? We are about to take on a huge project and frankly I want to save myself the ballache and go find a well oiled team if what I am witnessing isnt just how things are in software land, but as I rather suspect a product of lack of communication and organisation.1 -
I'm about to start as junior programmer. I'm taking a course which includes Scrum, where the teacher said '99.9 % of IT uses agile'.
That can't be right, right?!?
Or am I just being pessimistic? Can I get some estimates from the pro world, i.e. you?9 -
just a little pool here, do you, yes, you, do you think an inexperienced intern should take an epic story?
(not that there we work with agile, that would be great, but it's a task equivalent to an epic.)2 -
Ha! There's nothing like listening to a couple of crotchety devs talking shit about agile for half an hour, just to have a junior dev bust into the room and frantically exclaim "we have to start over from scratch again!" Apparently, someone didnt fully understand the requirements... 😉1
-
did little coding today... Spent most of my time learning Agile with Scrum. Suddenly so much of what went on in the 'Silicon Valley' tv show began to make sense. Jared [Donald] was a shrewd businessman.
resting now... Business & tech fascinate me. Perhaps there is still hope for this high-school dropout afterall! -
CS teacher: "I want you to do this project using DSDM. Every member needs to be appointed a role that is best suited to their abilities."
He has never heard of Agile.1 -
Continuation (no. 2): So because of my bad conscience I was very polite and friendly to the colleague I pestered about... but my boss was not. Instead he broke loose his second fight with Mr. git master. He's joking about that he now already had a fight with almost anybody (mostly team leads). He's leaving the company anyway, so he needn't care, but I start to love his love for conflicts. Some PM or upper boss already said something along the lines: "If something's wrong, I know you'll escalate." Of course you should not for every triviality, but nothing is worse than those lingering, dormant time bombs of projects that went so awry they're just waiting to explode... or silently be canceled.
Well, so they clashed again, and Mr git / scrum master fought for his concern that my boss, who's also product owner, must not enter the team. I looked at the git logs: Mr git master's only contribution - he's supposed to be a member of the team - since joining (like over a month) were 300 LOC, which was actually copy pasting our old copy right form, peppering it with some html tags to ensure it would not work without recompiling the 3rd party lib with a fucking webengine.
My boss now rather wants to remove "agile" as it's not fitting. Just let the three or four of us yank out the code so we actually have a chance to deliver in three months. He told the upper boss that we can take our tasks ourselves so independently we even need no team lead, but could report directly to him. It's still not clear what's gonna happen, but it's like they could let us loose, free radical elements who just do motherfucking programming. Feels awesome. -
Sometimes a poorly planned project makes coding a lot harder especially if features and UI/UX always changes 😭
-
"We follow the AGILE methodology."
A fancy way to say :
- We mostly work on tight deadlines.
- We will come with last second changes.
- We have little/no overtime payement policies.
- We will ask you to do basically anything even if you said explicitly that you don't know how to do it.2 -
The customer wants to drop Agile in favor of their in-house development methodology. They just sent an e-mail describing it...
I think my team needs a room decorated with cotton flowers and small huts to get into the right mindset.1 -
In a sprint planning meeting. Getting frustrated. I guess it's my fault. I guess I assumed that attending the same schedule meeting each week meant that we all knew when everything was due. My bad.
Seriously, I fucking hate systems people sometimes. We have 4 major tasks coming down the pipe, but they are scheduled in such a way in which they are staggered. But they want to punt the 1 of the 4 that is fucking done because it is going to cause a lot of testing, but the other three aren't coming til end of next month AT LEAST. So they want to stick their thumbs up their ass holes and wait to test the other three before testing the one that, again, IS FUCKING DONE!!! Are they worried that a super massive black hole will spontaneously form in earth's orbit and cause time to run backwards and somehow cause December to happen in October!?!?
No wonder systems is so fucking far behind. They can't see the forest for the trees. They're so big picture that months and years are at the same level of granularity. Fucking hell how is scrum better than our current agile process again? Besides the fact that it makes me attend more useless meetings and get more angry.
They are punishing the left hand for the actions of the right. Systems wasn't doing their job so now software has to slow down and miss schedule.2 -
True story: We had once a project where the manager tells the client we are using the Waterfall but internally the devs are actually doing Agile. >_<1
-
Yes I know that's too many points this sprint.
I understand you have to have all the things.
No I can't move the stories out bc you gave us a hard deadline for the release. -
*weekly team planning session, my first week*
They: "We don't estimate on effort required, we estimate on the number of unknowns"
Me: "How do you know unknowns?"
They: "Exactly. Also, we don't account for 0 unknowns."
Me: "What if it's a simple text change?"
They: "There's always unknowns."2 -
I suppose to be on leave after few hours... The team leader added five task to my sprint tasks... No wonder...
-
Is anyone’s team here fully Agile and how has that been so far? My team is currently in sprint 0 and I’m already tired of the meetings.24
-
I hate so much all those sprint related meetings. They literally take one day totalled (every 2 weeks).
Review, dry run demo, actual demo, planning, daily hourly meetings.... so much talking.8 -
I finally found out what is agile: You get assigned to a ptoject with fixed estimations of the tasks, but you have 30 minutes daylies in which you get micromanaged to do more work. The added AI blockchain value is that these dailies count as dev time for you, while for others it counts as TL, PL, PM, PC, Front office time.
And now for final deep learning, inovative, DevOps, java, javascript cutting edge, bleeding edge business aspect.... THIS IS A FUCKING SOLO PRoJECT!!!1 -
To those who have worked in mad RAD solo environments, with next to no testing...
...and those who have worked full Agile, with high code coverage, code review amongst hoards of T-shaped developers...
...how much difference does it make to wellbeing and upskilling in the two?
Bonus points if you have done both and can compare in an n=1 way.4 -
In the last three days our team has had 4 people who were the final decider on priority for a single project.
Im staying here until my contract has ended but then I will tell my company they can find a new project for me...1 -
We all know that one guy at work that explains and overshare stuff using a lot of jargons for the sake of using jargons at the daily scrum. Then it turns out, he's ranting about something so trivial, basically wasted a lot of time. And don't get started on meetings. Oh god. Please send help.1
-
TLDR, need suggestions for a small team, ALM, or at least Requirements, Issue and test case tracking.
Okay my team needs some advice.
Soo the powers at be a year ago or so decided to move our requirement tracking process, test case and issue tracking from word, excel and Visio. To an ALM.. they choice Siemens Polarion for whatever reason assuming because of team center some divisions use it..
Ohhh and by the way we’ve been all engineering shit perfectly fine with the process we had with word, excel and Visio.. it wasn’t any extra work, because we needed to make those documents regardless, and it’s far easier to write the shit in the raw format than fuck around with the Mouse and all the config fields on some web app.
ANYWAY before anyone asks or suggests a process to match the tool, here’s some back ground info. We are a team of about 10-15. Split between mech, elec, and software with more on mech or elec side.
But regardless, for each project there is only 1 engineer of each concentration working on the project. So one mech, one elec and one software per project/product. Which doesn’t seem like a lot but it works out perfectly actually. (Although that might be a surprise for the most of you)..
ANYWAY... it’s kinda self managed, we have a manger that that directs the project and what features when, during development and pre release.
The issue is we hired a guy for requirements/ Polarion secretary (DevOps) claims to be the expert.. Polarion is taking too long too slow and too much config....
We want to switch, but don’t know what to. We don’t wanna create more work for us. We do peer reviews across the entire team. I think we are Sudo agile /scrum but not structured.
I like jira but it’s not great for true requirements... we get PDFs from oems and converting to word for any ALM sucks.. we use helix QAC for Misra compliance so part of me wants to use helix ALM... Polarion does not support us unless we pay thousands for “support package” I just don’t see the value added. Especially when our “DevOps” secretary is sub par.. plus I don’t believe in DevOps.. no value added for someone who can’t engineer only sudo direct. Hell we almost wanna use our interns for requirements tracking/ record keeping. We as the engineers know what todo and have been doing shit the old way for decades without issues...
Need suggestions for small team per project.. 1softwar 1elec 1mech... but large team over all across many projects.
Sorry for the long rant.. at the bar .. kinda drunk ranting tbh but do need opinions... -
Is there anyone out there who uses absolutely everything JIRA has to offer? I've worked with it since starting my career and I still find it a massive fucking overkill.
-
Today, I found a bad bug. I fixed it and tried to understand what happened there. Story description was ok, dev was done on time, review performed (1/3 of the time needed to developed), testers were happy: story was DONE.
I feel uneasy as all protocols had been respected, and still, the code was bad and features were broken :( -
Worked with two different customers
(customer 1 is up to date because of active development and customer 2 got his update long ago)
Changed something for customer 1 and accidently pulled customer 2. 49 changesets (needs a db update probably). Rolledback and now keeping an eye on the error logs -
In my previous agile sprint I somehow completed my task before the halfway, that's why I got less buffer time and point in this sprint.
-
I'm a scrum sprinter using my agile-ity to dodge rock-rigid waterfalls.
My take at another lame joke.
But I still have my legs and can walk... -
I spent 2 hours in an agile workshop with the "I do not think it means, what you think it means" guy.
When finished I could swear that if you asked the people what is agile, they would start crying. -
Community Question:
I'm on a lone-project for work. That means I have to make a design plan and documentation. I have zero experience with this, anybody know a good example on the web of either of these? Much appreciated!2 -
here we go again
the remote-retrospective-where-most-of-the-team-are-muted-and-clearly-tweeting-or-doing-other-stuff
any ideas on how to improve this?15 -
Robert Martin says in clean code, or maybe clean architecture, that one should separate the tests into what is hard and easy. GUI tests are hard and therefore brittle and so we should test against view models.
However on clean agile he says a story is not done until it passes automated acceptance tests which in my experience are always brittle and grow so large and brittle that things grind to a halt.
What am I missing? Are stable acceptance tests possible on the GUI? Should we test only an API?6 -
every fucking time when the product owners start talking absolute shit that you have no idea and you would never need to know or listen to.
ITS A WASTE OF MY FUCKING TIME. SHUT THE FUCK UP AND TAKE IT OFFLINE. -
Working with non-existing specs. Just have to pick a guess what arguments and columns that will be needed. Right now it feels like I'm up to a very fuzzy task, that will need to be done over and over again until it gets right, instead of doing it right once and for all. If this is agile, then agile is a waste of time!5
-
Just sat the shittiest exam of my life yesterday. It involved among other things: TDD with java (on paper), critiquing and rewriting gherkin scenarios, and diagnosing problems with agile teams based on a limited description. I was short for time at the end and chose not to answer some questions because it would tire my hand too much to attempt them, and it's time consuming af to edit stuff you wrote down.
Many other exams are switching to online tests, and this one really could have benefited from that given the sheer volume of crap I had to write down.
I'm basically hoping to God that I didn't fail this thing, but the lowest exam grade I've had so far is 70 so it would be crazy if I did. Still, fuck these people for writing such a difficult exam. -
!rant
Agile devs— do you attend sprint planning?
I want to, but my boss told me not to go (waste of my time, he says). Only leads attend them, then they come back with tickets for the rest of the team. But a few other devs I’ve spoken to found that absurd, since attending lets you choose your tickets to a certain extent.
Do you attend yours? Is it crazy not to? Am I missing out? (I ask bc ours is happening right now— and it’s so empty in here!)4 -
Has anybody experience with Scrum in small web development agencies? Especially estimating stories with story points instead of hours/days?
We have a new junior project manager, without any practical experience working agile, who wants to establish scrum because what he read about it sounded so good... I already worked agile with kanban before and I loved it, but I only have little experience with scrum.
I think scrum, or agile in general, won't work with the clients we have. Most of the time, our clients have a fixed deadline, a fixed budget (either money or time) and they know their requirements, so there is no much room for beeing agile.
Regarding story points, I just adding an unneccessary layer of abstraction, because the customer wants to know how long a specific feature takes. Sure, story points are just another, more dynamic unit for time, but then why nut estimate in static time unit in the first place? Another fear I have, is that some devs may be more ignorant regarding deadlines and expectations on customers side. "yeah I'm working for 10 days on this story, but it's 8 points!" instead of informing the project manager "Currently I spend 2 days on this feature, we estimated 3 days, but it seems I need 3 days more".
Maybe I shouldn't be worried, but it would be great if you could share your experience and learnings. Thanks in advance!14 -
Yesterday, I attended a seminar about agile methods, Agile Islands. I attended it last year too, and have previously attended more or less evangelist lectures about agile so my expectations were frankly not that high. But, I have to say...WOW! Now I finally get what agile is all about! The reason that I haven't been convinced until now is that we've been doing it all wrong :)3
-
Honest question, if you work in an agile environment, do you prefer story points or counting of hours to gauge tasks?4
-
The waterfall model of executing agile: Planning phase -- how to execute agile?
The loudest voices are often the people who contribute much else.
How many of these meetings have you been witness to ? -
Why do they demand 12-month goals when we use Agile Methodologies?
If we do it right, we don't know what we are working on next sprint, let alone 12 months.
Our goals are to work on the highest priority stories. We are not to work on stuff "in the background", so how can we have any long-term goals?
The only things we can plan are outside of our actual jobs (like conferences, training, pilot programs/hackathon projects, etc.) So the only things we can review at the end of the year are not the most important things we do.
Poor managers love numbers and checklists to hide behind.2 -
Si this was a very good and bad week at work. The good part is I finally learned how to properly write tests. Not that I am a pro at it, but at least they don’t suck now.
The bad is I took a ticket that I now see was terribly underestimated, but hopefully I will finish it and the rest on time. -
We are in a course for the scrum certifiaction. Most of my partners are more concerned about they can't take the decission about using scrum or not. Is so sad because os a really small organization.
-
Once upon a time I worked for a startup in school as one of two developers.
I learned many technologies in this role. I built massive front end systems, debugged back end systems. They even gave me a little section on their site that was all about me and giving me credit for me work. The only actual employee was the "CEO, owner, and designer". A team of three in total.
Inevitably the company went under but the site remains. A skeleton of a dead dream. The CEO took my name and info off their website and took credit for all the work I put months into. I was never paid, never giving any recognition whatsoever for the work I did.
I'm not looking for an award or anything like that, but like bro?!?? I built your companies interface for free and you throw me out like trash.
Wtf is being a developer?!?4 -
When a co worker pretends to work all day by "fixing" something that you've already fixed. Just so that they have something to talk about at stand up in the morning.
Git commit -nothing 🙄 -
The Sprint started and this Stupid Lady did not finish her work yet and I am stuck till that. Funniest part is figuring out what to tell in the Daily Stand Up. ' Going through the Code and getting Familiar' :P
-
scaled agile day long planning meetings sitting around watching other teams point their pointables.
1 -
When a developer refers to everyone on the team as family and you're thinking the complete & total opposite.
-
Who still use Trello as Kanban and why don’t you change to an another (better) system?
And if you use a specific system, what is it?
My team work with Trello since the beginning. But as the team grows, it become impossible to say organize with a such simple system as Trello.3 -
!rant
Use BitBucket Cards to manage your issues as a Scrum Board. It makes your life way easier!
http://www.bitbucketcards.com/ -
I’ve been reading “Agile Testing” by Lisa Crispin. The list of tools that I learn about and go on to star it on GitHub is never-ending! Are you expected to be proficient in each and every one of these?
-
Currently our team is in a cycle of blaming the PO (indirectly) & feeling bad about it. He's really a nice guy and is doing his best! (☞ ͡° ͜ʖ ͡°)☞
Top Tags
Weekly Rant
View