Which of the following l&T implementation methods requites the HIGHEST level of participation by users at multiple stages of software development?

Agile methodologies are inherently designed around iterative development and continuous feedback loops. A core principle of Agile is the close, ongoing collaboration between the development team and business users or their representatives (e.g., a Product Owner). Users are actively involved in all stages, from defining and prioritizing user stories in the backlog to reviewing and providing feedback on each incremental software delivery at the end of every sprint. This sustained, high level of engagement is fundamental to the Agile process to ensure the final product continuously aligns with evolving business needs, making it the method that requires the highest level of user participation.

A. Hybrid: User participation in a hybrid model is variable, depending on which elements of different methodologies are combined; it does not inherently require the highest level.
B. Traditional: In traditional (e.g., Waterfall) methods, user involvement is concentrated at the beginning (requirements gathering) and the end (acceptance testing), with minimal participation during the development phases.
C. DevOps: The primary focus of DevOps is on fostering collaboration between Development (Dev) and Operations (Ops) teams to streamline and automate the software delivery pipeline, not on user participation in development.

1. ISACA, COBIT 2019 Design Guide: Designing an Information and Technology Governance Solution, 2018. In Appendix A, Table A.10, "Design Factor 10: Development Method," the description for Agile explicitly states it "implies short development cycles (sprints), flexibility in requirements and a close collaboration between development teams and business." This contrasts with the descriptions for Traditional and DevOps, which do not emphasize this level of business/user collaboration.

2. ISACA, COBIT 2019 Framework: Governance and Management Objectives, 2018. The management objective BAI03 Managed Solutions Identification and Build covers software development. In an Agile context, practices like BAI03.02 Manage solution requirements definition and BAI03.06 Manage solution development require continuous stakeholder interaction, unlike the traditional approach where requirements are typically frozen upfront.

3. Hohl, P., et al. (2018). IT-Governance in a Digital World: A COBIT 5-Based Management Approach. In: Business Information Systems and Technology 4.0. Springer, Cham. https://doi.org/10.1007/978-3-319-74322-611. This publication, while referencing COBIT 5, discusses the shift toward Agile and DevOps. It notes that Agile methods "are characterized by close cooperation with the customer" (Section 11.3.2), reinforcing the principle of high user participation that is carried forward and recognized in the COBIT 2019 framework.