Guessing is not a strategy: How to build decision velocity with AI and real-time data
June 10, 2026 | Live Webinar
From Agile Development to New Software Engineering
In 1997, long before agile project management became a buzzword, a paper was presented at a military software conference, entitled “Disciplines Delivering Success” [1]. I find it sobering to read that paper 10 years later and see how little our organizations have advanced over the decades. Brown presented six “project-saving disciplines ignored by management”:
-
Good personnel practices
-
Planning and tracking using activity networks and earned value
-
Incremental release build plan
-
Formal configuration management
-
Test planning and project stability
-
Metrics
It is sobering because those are very similar to the starting recommendations offered by agilists today. Clearly we agilists are not unique in requesting these items--good project managers have been requesting them (and getting ignored) for a long time. I show that list so that we don’t have to re-hash the past yet again. I assume you will take of those things.
More interesting than rehashing the past is deciding how to move forward. To this end I present how software engineering is being revised to take account of what has been learned in the agile movement. It indicates where we should put our attention in the next decade.
Leaving aside navel-gazing questions …
Please log in or sign up below to read the rest of the article.
ADVERTISEMENTS
|
"Substitute 'damn' every time you're inclined to write 'very'; your editor will delete it and the writing will be just as it should be." - Mark Twain |