Abandon Faux Agile & Dark Agile
In so many cases teams or management declares they are "agile" but are not really agile in the sense of the Agile Manifesto, but using that as a crutch to produce poor quality software with no discipline. Ron Jeffries, signer of the Agile Manifesto says "stop it"
"[Agile adoptions] often lead to more interference with developers, less time to do the work, higher pressure, and demands to "go faster". This is bad for the developers, and, ultimately, bad for the enterprise as well, because doing "Agile" poorly will result, more often than not, in far more defects and much slower progress than could be attained. Often, good developers leave such organizations, resulting in a less effective enterprise than prior to installing Agile..." Rui Miguel Ferreira
"No matter what framework or method your management thinks they are applying, learn to work this way:
- Produce running, tested, working, integrated software every two weeks, every week. Build your skills until you can create a new fully operational version every day, twice a day, multiple times a day.
- Keep the design of that software clean. As it grows, the design will tend to become complex and crufty. Resist and reverse this tendency consciously, refactoring in tiny continuous steps, all the time, so that your rate of progress is as steady and consistent as possible.
- Use the current increment of software as the foundation for all your conversations with your product leadership and management. Speak in terms of what's ready to go, and in terms of what they'd like you to do next." Ron Jefferies
Of course SEER for Software (SEER-SEM) can provide the costs, schedule, and risk for clean agile or Dark or Faux Agile. The difficulty is getting the team and management to realize they have an issue.
The SEER-SEM Agile planner shows what to realistically expect from your agile process Produce viable, maintainable software, not just something that works today but is maintainable with minimal technical debt.
Additionally the Agile Manifesto doesn't consider if the software has a positive return on investment or what the total ownership costs will be. SEER-SEM provides that information so good decisions and good agile software can be developed.