Agile has the answers?
Some software approaches run in cycles
Gather requirements (sometimes)
Write Code
Test code (sometimes)
Get the requirements wrong and the requirements change midway through writing the code and your writing more code or changing code and the time scale goes up (yes even if the deadline is unmoveable the coders still have to work more hours). Worse yet they change at the testing level and it means more code and yet more testing. Expensive and time consuming when you could use all that to deliver sooner and more to your customer.
Let’s say the cycle takes 6 weeks, 2 weeks in each stage. On week 3 the customer asks you where you are and you either make them wait 2 weeks more or give them an incomplete version. They then ask for this, that and other, with the need to gather further requirements, write more code\change code the cycle is looking longer and longer and the customer is still not seeing what they asked for (and keeps changing their mind). Sounds like scope-creep sure enough but if the customer is not getting what they asked for are you delivering and will they keep paying you? Requirements sign off can help but will the customer agree and be happy that what they signing off is what they asked for (and keep paying you for it). They may have agreed to Black but they ment #001.
Agile has the answer though....
No one has yet said that Agile will save the day and our industry will be bright and wonderful, some agree that Agile works for some things but not others aka THE ENTERPRISE.
I don't personally agree as Agile is not any one thing, it is just a another way of doing things and if you have the foundations right you can adapt it your team\business etc. I don't have all the answers, if you write widgets that control the flow of ear wax in a 3D human head sim can't say what you will need to do. Only YOU can answer that question, you do the job, you know what works and want doesn’t but to cast Agile aside for less than serious reasons will keep you on the same late\failed\expensive project path.
Agile was not dreamed up by a collection of goofy nerds but was a collection of ideas from a group of people who had spent decades in the industry and created the concepts from those same decades spent on software projects (and seeing why projects failed).
Agile does fail too though, lots of stories about failed Agile projects with reasons ranging from incomplete\unworkable adapted Agile process through to failing to understand\follow Agile concepts. If you’re serious about it, hire an Agile coach, sure some cost the GNP of a small nation but they are worth their weight in gold in using their experience and skills to help you adapt and follow Agile processes.
Have you adopted agile, what worked\failed for you?