The Defense Innovation Board has published set of guidelines that will help the Defense Department and other program executive offices determine if agile development processes are being followed, GovernmentCIO Media reported Friday.
The document called Detecting Agile BS provides standards for identifying real or false claims of project teams in complying to agile development practices.
DIB found that the lack of communication between the software development team and the users of the system code, the priority to meet requirements first before developing an actual effective product and contractors acting autonomously are signs of a fraud agile project.
Other indicators of false agile development progress are the absence of end users throughout the development phase and the use of manual instead of automated processes in the development, security and operations culture.
The guide also noted that the use of tools such as repository hosting sites and modification tracking applications indicate that project teams are legitimately executing an agile development process.
Additionally, Detecting Agile BS provides the DoD with a set of questions it could ask customers and users and teams for programming, program management and leadership regarding their software development efforts.