393
The Great Software Quality Collapse: How We Normalized Catastrophe (techtrenches.substack.com)
submitted 1 year ago by to c/technology@lemmy.world
134 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 6 points 1 year ago (4 children)

My hot take : lots of projects would benefit from a traditional project management cycle instead of trying to force Agile on every projects.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 1 point 1 year ago (3 children)

    Agile SHOULD have a lot of the things 'traditional' management looks for! Though so many, including many college teachers I've heard, think of it way too strictly.

    It's just the time scale shrinks as necessary for specific deliverable goals instead of the whole product... instead of having a design for the whole thing from top to bottom, you start with a good overview and implement general arch to service what load you'll need. Then you break down the tasks, and solve the problems more and more and yadda yadda...

    IMO, the people that think Agile Development means only implement the bare minimum ... are part of the complete fucking idiot portion of the industry.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 2 points 1 year ago (1 child)

    Agile was the cool new thing years back and has been abused and misused and now, pretty much every dev company force it on their team but do whatever the fuck they want.

    Agile should have a lot of traditional project management but doesn't because it became the MBA wet dream of metrics. And when metrics become the target, people will do whatever they need to do to meet the metrics instead of actually progressing the project.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •