Avoiding the software death march with Agile

Traditional development leads to wasted time and effort

Large software projects in the past were run like a military campaign. Large groups of consultants were hired and thrown at a project. The project was supervised by a project manager and deadlines were set in an arbitrary fashion with no input from the people doing the work. The process was filled with waste and people worked against the clock to deliver value. After long hours and “crunch time,” the software was revealed to the executives who commissioned the work. These meetings were often filled with acrimony because what the executives were expecting and what was demonstrated did not match. Deadlines were missed, more money was spent, and the process would repeat until the project was canceled or the software was shipped. When the client did ship software, it was over-budget and buggy.

Telling a better development story with Agile

Agile is a response to the death march. Instead of long periods of work without feedback from the client, the software team and the customer work together in sprints. At the end of the sprint, the customer reviews the work and has the ability to make any needed corrections or improvements, understanding they will be able to see those changes in effect after the next sprint. Each sprint is like a new chapter in a novel. Together, these chapters make up the story, with the earlier chapters informing the later chapters. The team stops sprinting when the project delivers the value the client is expecting.

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Codal Inc.

Codal Inc.

17 Followers

A digital solutions partner with a data-driven approach that empowers companies at the intersection of UX design, development, & business.