This is the best summary I could come up with:

Even though the research commissioned by consultancy Engprax could be seen as a thinly veiled plug for Impact Engineering methodology, it feeds into the suspicion that the Agile Manifesto might not be all it's cracked up to be.

One standout statistic was that projects with clear requirements documented before development started were 97 percent more likely to succeed.

"Our research has shown that what matters when it comes to delivering high-quality software on time and within budget is a robust requirements engineering process and having the psychological safety to discuss and solve problems when they emerge, whilst taking steps to prevent developer burnout."

A neverending stream of patches indicates that quality might not be what it once was, and code turning up in an unfinished or ill-considered state have all been attributed to Agile practices.

One Agile developer criticized the daily stand-up element, describing it to The Register as "a feast of regurgitation."

In highlighting the need to understand the requirements before development begins, the research charts a path between Agile purists and Waterfall advocates.

The original article contains 501 words, the summary contains 175 words. Saved 65%. I'm a bot and I'm open source!

Normal development: measure twice, cut once. Agile development: measure once, cut twice.

Shockedpikachu.jpg when things fall apart.

Lol I'm going to send this to my project manager

Someone would look at our process and say "that's not agile!" and they might be correct, technically speaking. I don't personally care what it's called as long as it works.

We agree to requirements up front with our customer; we might change stuff as we go along if our customer realizes that what they asked for won't work (this happens occasionally), which is fine, but otherwise we don't let them change stuff around on a whim, and we don't allow scope creep. If they want a new feature, that's version 2 (or 3, or 4).

We don't meet very frequently. We do check in to make sure we're on target, and deliver features incrementally when it makes sense to do so. We do sprints. We talk about when things are working and when they aren't, but only when we think it's a good time to do so.

At the end of the day, you need to tailor the process to your needs and what makes sense to you and your team.

Should I remove my Agile experience from my resume?