To print a PDF version of this article, click here.
The Business Capability Lifecycle (BCL) methodology, which was implemented to develop defense business systems, requires a change in requirements engineering processes. Previous software development work by Systems, Applications, and Products on the Global Combat Support System-Army (GCSS-Army) followed the waterfall Software Development Life Cycle (SDLC), which is not acceptable in the BCL methodology. The typical functional requirement statement is not easily changed and introduces problems into an Agile SDLC. In this article, the author posits that Agile-based requirements (user story and acceptance criteria) best fit the BCL approach. By implementing best business practices and lessons learned from the GCSS-Army project, a typical BCL-led program can achieve significant benefits, such as (a) increased effectiveness in requirements meeting the users’ needs; (b) increased performance of customers and software developers; and (c) reduced requirements volatility.