●Stories
●Firehose
●All
●Popular
●Polls
●Software
●Thought Leadership
Submit
●
Login
●or
●
Sign up
●Topics:
●Devices
●Build
●Entertainment
●Technology
●Open Source
●Science
●YRO
●Follow us:
●RSS
●Facebook
●LinkedIn
●Twitter
●
Youtube
●
Mastodon
●Bluesky
Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!
Forgot your password?
Close
This discussion has been archived.
No new comments can be posted.
Load All Comments
Full
Abbreviated
Hidden
/Sea
Score:
5
4
3
2
1
0
-1
More
Login
Forgot your password?
Close
Close
Log In/Create an Account
●
All
●
Insightful
●
Informative
●
Interesting
●
Funny
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
byRob Kaper ( 5960 ) writes:
There is room in budgets to pay attention to some good practices or enforcement thereof by peer review. But often - especially with custom-made sites - it is simply not enough. I've seen plenty of projects where the design company was granted bigger fees for more hours than implementation, stereotypically also making everyone overly complicated. Even during scrum sessions where developer input is more present, doing it quickly is a much larger focus than doing it right. In the end, that simply leads to sloppy code. This is of course not true for every situation, but I've seen it happen far too often.
twitter
facebook
bygtall ( 79522 ) writes:
"scrum sessions" There's your problem right there. Agile does not encourage good overall design. It is a micromanagering dream and causes coders to only work for the next sprint goals. As long as their little piece of the pie works, they get rewarded. The entire dirty snowball that gets produced is merely a by-product.
byMoarSauce123 ( 3641185 ) writes:
Agile only encourages customers not to tell you what they want. It becomes perfectly acceptable that they change their minds constantly and sell it was "agile" and "iterative approach". Agile is awesome for all those who are too inept to make a decision.
byHornWumpus ( 783565 ) writes:
Agile is a manifesto full of truisms.
Managers only read the parts you cite. Confuse Agile and Scrum.
It's almost always what you say, but not absolutely always.
bydavid_thornley ( 598059 ) writes:
Your description of Agile is not a description of good Agile.
If you're using Agile correctly, you're not micromanaging and developers look at the overall project. That sounds like really bad management. perhaps you're using a variant of Scrum where the manager is the Scrum master, comes up with stories himself or herself (instead of involving the developers), and evaluates the developers on the basis of whether they do exactly what the manager wants.
● threshold.
byMoarSauce123 ( 3641185 ) writes:
So there is no budget for doing it right the first time, but there is budget for gluing together hot patches when stuff blows up in production? Any manager with that idea needs to be slapped with a wet noodle for days.
There may be more comments in this discussion. Without JavaScript enabled, you might want to turn on Classic Discussion System in your preferences instead.
Slashdot
●
●
Submit Story
It is much harder to find a job than to keep one.
●FAQ
●Story Archive
●Hall of Fame
●Advertising
●Terms
●Privacy Statement
●About
●Feedback
●Mobile View
●Blog
Do Not Sell or Share My Personal Information
Copyright © 2026 Slashdot Media. All Rights Reserved.
×
Close
Working...
Working...