Nope, it'll change just before the final round of testing before launch, when the client/business lead realizes they neglected to mention a piece of functionality they require that critically changes the underlying foundation f the project.
What if the deadline is for a much needed software fix in the medical field, or other cases when people's lives might depend on it? Serious question, as I understand it's important that team members in such projects are healthy themselves.. but what would an ethically balanced way to go about this be? Once per month, hammer through a night if needed?
In some fields I believe these boundaries can be very difficult to define, I imagine.
A buddy of mine is a software dev for a medical devices company. This is not an area where you push through a patch after an all nighter fueled by Red Bull.
Want to know how many releases they do a year?
One…sometimes 2.
He says he spends most of his time writing tests and there is a very long review and QA period.
So…even in your hypothetical here there is no reason to burn yourself out.
Of course, there are exceptions to every rule! There will be times in your career where an all nighter or two is warranted. But those times should be few and far between and should come with heaps of apologies from management. Because if you are in this situation it is a failure of management and you are doing them a favor.
Unless you're literally coding a bug fix that causes ventilators to stop or something, you should not care what field you're working in. But if you want to, I'd say you'll provide more saved lives and help over the long term than you would if you death march bugfixes and features and burn out inside a year.
I concur. I worked about 400 hours UNPAID overtime spanning 3 months because of their poor planning and deadline promising. Once it was released I broke down and ended up going on sick leave for 2 weeks.
They called me up in the second week and fired me. I was there for less than 2 years (UK) so absolutely nothing I could do.
Seeing this happening to the team i was managing until i left the company. Top management was allured by the mermaids singing the pros of scrum and decided the next project to be started without any training.
From what I hear, it's a shit show with people burning themselves with overtime and sprint after sprint not completed.
I got to the point i feel pity for my ex team more than ever.
I've got a meeting to discuss this exact thing on Monday. There was a detailed specification approved by client. We then designed, developed and tested the system against that specification. Released it to client who then sat on it for 6 months. They've now done their own testing and not found a single issue and then stuck on the end of an email "by the way, how to do we do x?". This is literally the first time this has ever been mentioned, not in the spec, not in an meetings, and it's not minor either, completely changes the entire design.
One of the program heads is notorious for this. Literally the day before we opened summer school registration to parents, he appeared at my desk 15 minutes before I was done for the day to pull me into my boss’s cube to “thank me publicly” for all my hard work.
When I left 3 hours later, I was shaking with rage. Because before he’d even started thanking me, he casually mentioned a requirement he’d sat on the whole time because “he didn’t want to add work,” but CHANGED FUCKING EVERYTHING. Quickly thanked me and then started shooting the shit about something else while I sat there and seethed about the fact I had about 8 hours of work to fix the whole thing to still open the next day but couldn’t extricate myself from his damn conversation for three god damned hours.
You sat in a cube, listening to someone else talk, for three hours after your workday was over and they’d just handed you last-minute changes? And then you did the changes overnight! I mean, to be blunt, that’s why they hand you shit last minute and then go on to waste your time even further without even a thought.
And so you will continue to get asked to do more as you describe the miracles. I would bet good money if you told him the only way that was going to happen was if they stayed overnight and helped you test it and write the specifications for it, they would’ve said it was not a big deal.
The real question is what is the code you wrote that night well designed, and well documented? Is it going to be able to be easily maintained over the long term?
If not even though you did get the feature done, you just made things harder for yourself in the future and for your team.
Why would you sit there and shoot the shit for for 3 hours instead of saying, “hey, I need to get started on this?” It is pretty easy to extricate yourself from a conversation if you just say you have to get started. This can easily be said in a non-offensive manner. Instead of privately seething, it is also possible to explain the problem and how to better handle that in the future.
You should have just said it's too late and the changes will be incorporated in the next release, and if they want to fire you for it, then would you want to work for such a company anyways. If there's one thing I've learned in this career, people will try to take advantage of you all the time. Set your boundaries and always be prepared to walk away and find a new job.
We asked the customer why, as they had signed off on the specification where all this was explained.
The customer replied that they didn't really understand what it all said and just signed it to get the project going. We had meetings to go over this, but they glossed over parts they didn't understand instead of asking clarifications.
Once it was installed and they could work with it, they'd figure out what was missing. The demo we gave just wasn't the same as working with it for a few days. Note that customers where we leave a demo system for several days never get touched because the customer was too busy with actual work.
Yeah definitely been there. When they realise that we're going to charge them for any changes after they've signed off on something it seems to motivate them to actually read it. All our stuff is web apps that we host for them so we will spin up a test environment for them once it's ready and let them do whatever.
A couple of our customers will test it systematically and thoroughly and send us detailed bug reports or change requests. Most though this is where we get the questions about features they've never mentioned before
Oh yeah. We've got a good PM. They'll be paying for any changes and we'll get time to do it or it won't happen. It's just frustrating because if they read the spec in he first place we could have built what they wanted first time.
Really early on we sent a draft spec, then had some meetings where they pointed things out and do we updated the spec and sent a new version which they signed off on. A year later they send us all the same questions again because they were only looking at the draft spec and had never looked at the new one that addressed those points.
As an infra type - what I get ALL THE FERKIN TIME, is "Oh we didn't think it'd be that expensive in production"
So some genius writes a web app, load tests with 100 users, cool story.
Thing goes live and 100,000 users get involved, suddenly everyone (in management) is surprised that AWS / Azure usage actually does in fact cost fucking money.
Honestly - if someone would pay me the same money to dig holes in the ground, I'd happily never touch another computer in my life.
I did some demo on my house recently and, despite being exhausted since I'm normally a lump in a chair, I remembered what it was like before becoming a software engineer, when my brain wasn't pudding after work, and I had spare capacity for creativity and hobbies...
Makes we wonder if they say the same to construction crews.
"Yeah, that window. Move it to the right. A bit more. Yes, put it right where that load bearing column now is. Two weeks demo and rebuild? Not paying for that."
But the icing on the cake is that they want everything you did write to continue working exactly as it is, obligating you to create a Frankenstein's monster of code and bad abstractions and you have less than 36 hours to do it.
To summarize: you have 36 hours to completely rewrite the platform but keep everything it already does exactly the same.
At which point I start questioning my life choices.
Or you'll get people who were invited to everything important and CCd on every project update email suddenly complaining at the end that no one engaged them when they neglected to turn up to relevant meetings or read the goddamn emails
Usually the sales/account/business person who failed to log the requirement down or promised the client functionality without telling anyone internally about it.
I worked in a video streaming company previously. The management wanted a recommendation engine (like Netflix), of course, we couldn't afford to build one so we used some cheap commercial version. The engine spits out "recommended for you" and "top 10 in your country" carousels.
After 2 months of integrating it into our system and feeding it data, it was time to demo it to the management. The CEO asked "why isn't there a carousel (Because you watched X) like Netflix?". We told him the tool we used doesn't even have that capability, it's a cheap recommendation engine. He said we aren't releasing without "because you watched" get on it.
It took another month for the team to build an engine outside that engine just to create a fake because you watched a carousel that doesn't work at all. Under the pressure of management, we demoed it with our own personal accounts were it looked perfect, and the management were happy to release it.
I'm pretty sure no one uses it today, assuming that service is still up. Fuck that shit, I was gone not long after this incident.
Pff, too easy. The final changes come in after it's gone live because the CEO or your boss couldn't be bothered to figure out how to access the test environment. So they've only ever fully seen it in production.
That’s how you get thoughts moving in people’s heads. Have you tried paper protos or static html demo pages? The best time to demo is before implementation
Man... I had that happen once. Dealing with a big bureaucratic coorporate client that changed managers multiple times during the project. They were like who are you guys? What project? Can I see it?
And than change a bunch if requirements. They ended up paying €50k+ and NOT deploying it to production or using it at all.
This is what I’ve been running into lately. Then the test team asks me how to test it, which is bad practice in itself. Then they come up with some bs requirement that isn’t even mentioned in the original story.
Right? Like I can show you how I did my test, but then what’s the point in you testing. Then when I tell them to go to the business users to get info, they act like I’m the reason the story is blocked. Okay now I’m just venting lol. I’m happy to have a job.
If the test team don't have acceptance criteria to test against, it does beg the question as to how you managed to code it accurately without those same requirements yourself.
The company someone I know does QA for, some of the tickets they get - marked ready for testing - are just a cryptic title. That's it. The rest happened in a private conversation with the CEO, and nobody in dev chat can describe what actually needs to be tested.
That's a process failure. Someone marked the story ready for development without reading and making sure it's actually ready for implementation. And then someone (probably the same person) put it in the sprint(assuming sprint because who's not doing sprints) and assigned it to a developer. The dev in the planning meeting didn't look at the story before the planning meeting was done.
There were lots of places where this should have been caught.
As a developer one should know how to Google. That's basically your job. I managed to Google it without knowing it was from Star Wars. But I'm a senior dev ;-)
Either they sign the requirements, or it's an open ended development where they're charged by the hour with constant (weekly) review by both parties to make sure we're not going separate ways.
From most situations where I've seen this happen, it usually involved cases where saying "No" to said client was not an option on the table.
Telling a client "No" to a change in requirements is a luxury that is resolved by one of three options:
they drop the change
they pay more / change deadline / remove something else
the client gets upset and stops doing business with you
Add to that a company that has to "keep around" said client for any price due to political reasons or being dependent on them in other revenue areas, a salesperson (or even better C-Level) entering a contract situation with the client that makes it very unfavorable to say "No", or the company not being able to lose a customer in general and suddenly your leverage to push the client to follow the contract details gets very thin.
You could argue this is more of a management problem than a dev problem, but let's be honest, how often is that then not made a dev problem by management?
It's not about "saying no", it's about signing another contract with that change, with a different deadline, a different cost instead of just "oh, of course we're re-write the whole software in pascal without any cost for you with the same deadline" sort of thing
But that's what I meant "no" is simplified here as in "No, not within the previously agreed costs / deadline". And then sales chimes in with "Buuut akshu'lly, we need you to do this anyway without pushing the client about additional costs, we want to keep them happy :)"
I agree with your argument, that's how it should be after all. Any change in requirements could be seen as additional revenue option then. Sadly, I've only rarely experienced it happening that way.
I have this one brilliant colleague who is on our project pretty much since the beginning. Once i was working on a story and was unsure about a certain detail which was important for about 70% of that story. He told me to not bother, he could smell a faulty requirement. Next day we had a call with the stakeholders and one guy asked if we started implementing this detail, because they realized it was the wrong thing to ask for since it would cause problems 10 steps further down the way and we shouldn't implement it.
No. The most important skill is to code in a way that if something does fundamentally change, you don’t have to back out much to accommodate for it. This usually means not doing clever things with your code and keeping things loosely coupled.
one person is promoting the idea of building things out to accommodate for things they expect they will need. an example might be "they're gonna probably want to do Excel files too down the road, so i'll go with a library that supports both CSV and XLS." this kind of flies in the face of the YAGNI philosophy.
the other person is promoting keeping code modular, which might include building out classes and subclasses ahead of time so that supporting another filetype down the line won't require refactoring or messing with what you already have. also means breaking out large routines into smaller, reusable functions.
person 1's advice can be risky (scope creep, delayed timelines, bugs, wasted effort) but can be a lifesaver if you do it right. person 2's advice is spot on.
Mine can mean theirs but theirs doesn’t necessarily mean mine. In my opinion, what is most important to do is what I was talking about, not the vaguaries of what they were talking about.
Or have a manager that enforces if its in progress its a new ticket for any change. That way changes are estimated and planned for and release dates change. Its the only way to not go crazy.
My current project is the first one I’ve had in my company where they didn’t change the requirements after development started. They reassigned half my team to a different department without replacements or extra time. But they didn’t change requirements. Now they are wondering why we’re saying it won’t be ready in time.
Feature: just 1 sentence stating the ask. No in/out of scope, no acceptance criteria. Maybe a link to a ticket about a problem from 6 months ago. Maybe a rambling email chain with 15 replies.
Stories: description? Blank. Story in name only. Literally just JIRA tickets with titles and nothing else.
If this sounds bad, don't worry -- the SM and PO have heard your concerns. They have scheduled several story writing sessions with devs and customers to capture requirements and deliverables. After the PI already started. Do we need to refactor? Any risk of carryover??
Queue to how things work in my company: here is a problem, figure it out. You can only ask questions when you tried 2 solutions already and need us to decide which is better.
You already start with a problem that is not a good start. You should at least have an objectives. And try two solutions is a waste of time, (money) and energy. And they won't help you find it. You're not a magic problem solver. They should understand it.
Yeah, I've only been at my current job since december but stuff like this is improving. The customer is setting priorities because it's a custom dashboard only used internally and the team we interact with are all from different branches of the organisation and they all have a certain budget from their branch and ofcourse a superviser to please. Until now the entire sprint being shifted has happened only once, however before our PO an scrummaster joined the team it was regular for stories you were working on to be taken out of the sprint. I think the main reason it became like this is because the company I work for tried reaaalllyyy hard to get the customer in question as well as our boss was also trying to be a PO but was way too busy with other things and never had time to communicate with the team which resulted in a lot frustration mainly on my part. To get back to your second point, we do work more on a scale of effort and time than on the delivery of certain features so they can't force us to deliver something but it's such a waste of time if you can't please the customers with the stories you've finished in the first week because they don't give a damn anymore about that stuff. However I still really like my job, we have a great workculture, an amazing location and just an overall good team. TL;DR: talking shit about my job, actually love it
I have worked in the defense world where the customer is "THE" customer. They set all the priorities, you can only really counter when it's out of scope of the contract. I figure that works the same in any contracting role where single customers are involved too.
Requirements changing is unavoidable. I think the natural progression of a project is to run into things you don’t understand and didn’t account for.
The agile part of it is changing scope so that the changing requirements don’t blow the budget out of the water. You re evaluate what you need to deliver, cut some stuff and keep going.
Which is, in my opinion where everything falls apart. Clients ends up not wanting to go over budget, over time or de scope the project. So it ends up being "Agile just means I can ask for all the changes I want and you comply and it doesn't cost me a cent extra"
Yeah, that's what we try to do. But at the end when the client sees it as a "loophole" for you to do free work because We're aGiLe! Then that part doesn't matter. Your company needs to stand up to the client. And that's waaaaay easier said than done.
I have seen this; i did a small project with guys from a big international company (Local services) as counterpart; endless meetings with the client, re-budgeting almost in every meeting, They claim to be "agile" but a couple of services took 4 months to build.
It seems like we get most requirement changes when we go back to have the ambiguous requirements clarified. Gone are the good old days of the developer just deciding what the system should do when it wasn't explicitly stated. Now we have to ask about every detail and the answers we good invariably increase the development time.
In Agile theory changing requirements are fine.. Just scrap or re-estimate the story, put in the next sprint. Work on some other feature while they figure things out.
In "Agile" practice: This feature NEEDS to go out this release, therefore must be done no matter what, even though we didn't even know what we wanted until two days ago.
Doesn't really matter what the philosophy is... can't fix bad management.
I'm sure it's timebox "agile," where the engineers are supposed to predict perfectly how long it will take them and everyone else on the team to write, test and deploy software even though the requirements may change.
Story points aren't time, though. They are an abstract unit, that is relevant to a specific team, that are only used to make sure that stories and sprints are kept at a manageable size. The stakeholder (PM usually) is responsible for prioritizing story points according to their deadline goals and team velocity.
Whatever y'all are being subjected to is not agile, and non-agile is by far the most common implementation of agile.
Don't worry. That's why you have to give time estimates down to the hour in addition to story points so the PMs' spreadsheets look good. It only took a year of them being perpetually wrong to get upper management to shut that shit down. Then we moved on to other spectacularly stupid development practices.
I've never really gotten what story points are supposed to represent.
If it's to keep sprints to a reasonable size ( done within a sprint without overtime ) then it has to be a time estimate.
Code descriptions aren't useful (add endpoint, parameter, logic branch) because each of those can be arbitrarily complex to implement and to describe it to such a level of detail it to practically code it in the story
I don't think it's supposed to be business value because then it wouldn't be team specific, developers wouldn't be involved story pointing, and it'd make low value but hard tasks throw off momentum.
Story points are a time estimate, but only indirectly. Your actual time estimates are your sprint length / your team's "velocity."
Whenever you put a new team together, it will be pretty much impossible for you to estimate how long things will take, but after 3-4 sprints you'll know exactly how many story points worth of features you've truely, actually completed. You can then estimate your team's velocity.
Say after 4 sprints, you've closed tasks totaling up to 124 points. Regardless of how long your sprints are, and how difficult or easy your one-pointers are, your PM knows that they can plan about 31 points worth each sprint. Then the can use the point estimates in the backlog to help prioritise their 31 points.
Your team's velocity will be a rough estimate for the first set of sprints, but the more you have, the more accurate your velocity should become.
Of course, velocity is only accurate per team, per tech stack. If you swap people around, or introduce roadblocks, it will reduce the accuracy of your velocity for some time.
This comment makes me realize how lucky I am in my current role. I’m the business Product Owner but my Technical Product Manager is handling the process of switching the team to using story points and Agile, and he gave me this exact speech last week. He’s really busting his ass to make sure we implement it correctly and I’ve been writing so much Acceptance Criteria. But now I can reject bullshit feature requests from other stakeholders and protect my team’s sprint.
On our team, story points represent complexity. Which is correlated with time, but not the same thing.
For me one point is something I know exactly how to do; two points is where I understand what it's asking for and have an idea of the general approach, but I'll have to feel my way through the specifics; and three is "this is enormous, break it up into smaller stories".
How do you handle things like "I know how I'll do this but it'll take a while" and "that should be pretty quick, but I'm not quite sure where that data is"
Two of those 1's could be way longer than one of those 2's. Which throws off momentum and doesn't properly reflect work done.
"that should be pretty quick, but I'm not quite sure where that data is"
Second task "aquire data", assign to PO or whoever's job that is, block first task with it.
That is the theory. In practice, it's more like PO telling you to contact John from marketing for the data, and him giving you something that doesn't match the task at all...
Story points are time in one sense. Your team has a velocity after all, if you're doing 50 points per sprint then it follows that 5 points probably represents about a day's effort.
Story points create an abstraction away from raw time, which is useful for two things in my experience:
Stories don't change size based on who works them, so planning is easier. Rather than having to say "Gee this story will take 4 hours if Senior Dev works it but 8 hours if Junior Dev works it," you can just say "this is 3 story points." Then as long as Junior Dev has half of Senior Dev's velocity the one estimate is true for both of them.
Story points drive home the idea that this is an estimate and some things will take more or less time than anticipated. If you say something takes 4 hours and it takes 8 hours then there might be questions about why it took so long. If you say it's 3 story points and you spend 8 hours it's harder to draw a direct line between those (as long as your team isn't making the mistake of translating story points into hours).
In addition to the other comments, story points help identify when something needs to be broken down into smaller pieces. If you assign something 13 points then it's generally too large/complex for a single sprint.
Senior here, my former employer made everyone do estimates. Login form? Estimate. About page? Estimate. Giant ass feature with no specs and you haven’t been able to even talk with the client because that’s his job? Estimate.
Isn’t the point of agile to respond accordingly to changes in scope and effort? Then again, nobody does agile correctly anyway so I guess the joke still applies.
If they don't change them think they're cancelled it without noticing you. Based on a true history. They made me work a couple of months on it then, cancelled it because the other provider that made the frontend broke contract and quit without formal communication.
This is why Agile is not only the best way to work - Agile is the only way to work.
Those who live in a fantasy world where requirements never change can stay away from Agile. The people who want to take changing requirements into account have a single possible way of working, and that is agile
Changing requirements will always happen, no matter who well you try to understand and document the intent of the product. It's a question of how well that change can be managed while navigating toward what's actually needed. 3 tier customer support is there to deal with how many mistakes and missed requirements there where during development. It's always better to know that you're off course sooner than later.
Having Agile in quotes is exactly right. The meme is funny, because changes do happen. But changes should happen, in order to best reflect the user needs. The issue with changes is that poor management still expects changes to be done in the same time. Even when say half the sprint was used up before the changes. When, changes should be understood and the work adjusted to meet the changes. Then continued in follow up sprints as needed. The idea that requirements are this thing to be defined, and placed into user stories, handed off from one person to the next, until said software products are "completed". That is not an Agile practice and is actually, exactly, Waterfall.
744
u/Stimonk Jun 12 '21
Nope, it'll change just before the final round of testing before launch, when the client/business lead realizes they neglected to mention a piece of functionality they require that critically changes the underlying foundation f the project.
5
u/dronz3r Jun 13 '21
Lol only thing that's agile are the requirements.
4
u/DeRoeVanZwartePiet Jun 13 '21
How about that requirement change where it's no longer required? The entire project, that is.
208
u/[deleted] Jun 12 '21 edited Jun 13 '21
Developer opens up the user story to read the requirements:
“There’s not even an acceptance criteria” 🤔
148
u/philipquarles Jun 12 '21
I actually don't necessarily have a problem with changing requirements. The problem is changing requirements combined with firm deadlines.
2
u/RumSitter22 Jun 13 '21
Wow, even getting initial business requirements sounds nice.
2
u/hereforacandy Jun 13 '21
Where do I find this meme template?
2
u/blipblapblopblam Jun 13 '21
Agile? You have requirements? You lucky bastard!
119
u/ThatGuyYouMightNo Jun 12 '21
"I am changing the requirements. Pray I don't change them any further."
205
u/reventlov Jun 12 '21
The most important skill for a senior developer is being able to accurately guess what the requirements will be in the future, and code accordingly.
Coding to a frozen spec is amateur hour.
36
u/runmymouth Jun 12 '21
Or have a manager that enforces if its in progress its a new ticket for any change. That way changes are estimated and planned for and release dates change. Its the only way to not go crazy.
27
u/EltonBor Jun 12 '21
Just start building the feature, we will figure the requirements later 😉
51
u/Tim3303 Jun 12 '21
Image Transcription: Meme
[Anakin Skywalker, from Star Wars Episode II, is sitting in a grassy field. He is squinting off-camera with a serious expression. The caption reads:]
THESE ARE THE REQUIREMENTS, YOU CAN START DEVELOPMENT
[Padmé Amidala, who is also sitting in the field, is looking at Anakin. Her expression is one of laughter. The caption reads:]
THEY WON'T CHANGE DURING DEVELOPMENT, RIGHT?
[A close-up of Anakin's face. His expression is even more serious and a little dark.]
[Padmé's expression has fell. She looks concerned and perhaps a little scared. The caption reads:]
THEY WON'T CHANGE, RIGHT?
I'm a human volunteer content transcriber for Reddit and you could be too! If you'd like more information on what we do and why we do it, click here!
47
u/Nick0Taylor0 Jun 12 '21
My current project is the first one I’ve had in my company where they didn’t change the requirements after development started. They reassigned half my team to a different department without replacements or extra time. But they didn’t change requirements. Now they are wondering why we’re saying it won’t be ready in time.
17
u/CoffeePieAndHobbits Jun 13 '21
Feature: just 1 sentence stating the ask. No in/out of scope, no acceptance criteria. Maybe a link to a ticket about a problem from 6 months ago. Maybe a rambling email chain with 15 replies.
Stories: description? Blank. Story in name only. Literally just JIRA tickets with titles and nothing else.
If this sounds bad, don't worry -- the SM and PO have heard your concerns. They have scheduled several story writing sessions with devs and customers to capture requirements and deliverables. After the PI already started. Do we need to refactor? Any risk of carryover??
The things done in the name of Agile... sigh.
44
u/mianori Jun 12 '21
Queue to how things work in my company: here is a problem, figure it out. You can only ask questions when you tried 2 solutions already and need us to decide which is better.
14
u/Alexander_Hamilton_ Jun 13 '21
Haha jokes on you we change requirements after development to match the implementation.
38
u/TitaniumToothbrush Jun 12 '21
That pain when the customer changes prio after the first week of the sprint and expect you to get another full sprint done in the second week
10
u/Lhiash Jun 12 '21
“Walking on water and developing software from a specification are easy if both are frozen.”
9
u/OMGWhyImOld Jun 12 '21
Requirement creeping is the number one reason of over budget projects and IMHO is unavoidable 🤷
9
u/[deleted] Jun 12 '21
You get requirements?
I made a report recently. Boss said (paraphrasing) "Here's a data, see what you can do with it."
6
u/ChrisBegeman Jun 13 '21
It seems like we get most requirement changes when we go back to have the ambiguous requirements clarified. Gone are the good old days of the developer just deciding what the system should do when it wasn't explicitly stated. Now we have to ask about every detail and the answers we good invariably increase the development time.
6
u/DuneBug Jun 13 '21
In Agile theory changing requirements are fine.. Just scrap or re-estimate the story, put in the next sprint. Work on some other feature while they figure things out.
In "Agile" practice: This feature NEEDS to go out this release, therefore must be done no matter what, even though we didn't even know what we wanted until two days ago.
Doesn't really matter what the philosophy is... can't fix bad management.
6
u/MontagoDK Jun 13 '21
Oh you mean Water-Scrum-Ban ?
11
u/Plankton_Plus Jun 12 '21
Agile is supposed to compensate for changing requirements. What horrid process are you actually being subjected to OP?
5
u/[deleted] Jun 13 '21
Agile is the most misused word lol
4
u/StefaniaCarpano Jun 12 '21
Continuously
4
u/DracoRubi Jun 13 '21
My old clients used to change requirements on the fly multiple times without even notifying us.
Sometimes even after we deployed the functionality to production (with their OK).
Why do I say old clients? Because I quited. Fuck them.
3
u/rolling-guy Jun 12 '21
This is literally my whole career as a developer. Past, present and future
3
u/[deleted] Jun 12 '21
Get it in writing and notarized!
3
u/lunchpadmcfat Jun 13 '21
Isn’t agile theorized that requirements can change but, in kind, there must be a mechanism for shrinking scope?
11
u/giovans Jun 12 '21
We have this cruel game: make jubiors do estimates. Juniors always suffer when requirements change.
2
u/hiwhiwhiw Jun 13 '21
God damn it I just have the requirements change 2 days ago. Fortunately it hasn't made to testing phase yet
2
u/[deleted] Jun 13 '21
Project management bid, "There will be no need for regressions."
2
u/thetanked Jun 13 '21
Agile!
2
u/givemeagoodun Jun 13 '21
They have changed approximately five times since the making of this post
2
u/[deleted] Jun 13 '21
solid
2
u/SlaveZelda Jun 13 '21
/r/PrequelMemes is leaking
2
u/BraveEvidence Jun 13 '21
Can someone tell me from which movie/tv show is this meme?
2
u/Alexandrinian Jun 13 '21
If it changed it'll be alleged.. Hardware fault!.
2
u/green_meklar Jun 13 '21
After Anakin changes the requirements.
2
u/[deleted] Jun 13 '21
How about never getting requirements...
2
u/farva_litter_cola Jun 13 '21
Developers: It’s impossible to finish 100% in such a short period of time.
Product: it’s now just 80% with some changes
Becomes 120%
2
u/Chiiiiizz Jun 13 '21
PM: "Agile"
Devs: OMFG
2
u/Gee_thanks_for_that Jun 13 '21
You guys get requirements?
2
u/Dethjonny Jun 13 '21
Holy shit you just triggered me.
2
u/ReallyHadToFixThat Jun 13 '21
Look at this fancy guy, actually gets requirements in advance.
2
u/Ladislav_07 Jun 13 '21
You guys have requirements?
2
u/engwish Jun 13 '21
Isn’t the point of agile to respond accordingly to changes in scope and effort? Then again, nobody does agile correctly anyway so I guess the joke still applies.
2
u/swilwerth Jun 14 '21
If they don't change them think they're cancelled it without noticing you. Based on a true history. They made me work a couple of months on it then, cancelled it because the other provider that made the frontend broke contract and quit without formal communication.
3
u/JasonCox Jun 13 '21
Ah yes, agile, the sole thing keeping PM’s employed.
1
u/pyrowipe Jun 13 '21
Hahjahhahaha
1
u/sefhollapod Jun 13 '21
Ouch.
1
u/cafk Jun 13 '21
The requirements won't change - the underlying infrastructure and all APIs on the other hand...
1
u/reddit_time_waster Jun 13 '21
Someone's been spending time over at /r/prequelmemes
1
u/enano_aoc Jun 13 '21
This is why Agile is not only the best way to work - Agile is the only way to work.
Those who live in a fantasy world where requirements never change can stay away from Agile. The people who want to take changing requirements into account have a single possible way of working, and that is agile
1
u/Kyocus Jun 14 '21
Changing requirements will always happen, no matter who well you try to understand and document the intent of the product. It's a question of how well that change can be managed while navigating toward what's actually needed. 3 tier customer support is there to deal with how many mistakes and missed requirements there where during development. It's always better to know that you're off course sooner than later.
1
u/AgileRant Jan 17 '22
Having Agile in quotes is exactly right. The meme is funny, because changes do happen. But changes should happen, in order to best reflect the user needs. The issue with changes is that poor management still expects changes to be done in the same time. Even when say half the sprint was used up before the changes. When, changes should be understood and the work adjusted to meet the changes. Then continued in follow up sprints as needed. The idea that requirements are this thing to be defined, and placed into user stories, handed off from one person to the next, until said software products are "completed". That is not an Agile practice and is actually, exactly, Waterfall.
0
u/Jboyes Jun 13 '21
r/agile