Principles for Agile Development

Abstract

The Manifesto for Agile Software Development [Beck 2001] and the Principles behind the Agile Manifesto were written specifically for software development teams. Since the manifesto does not appear to apply to systems or large programs with multiple teams of development, how it applies to systems engineers is not apparent. The Principles for Agile Development are recommended for cross‐functional teams that include Systems and Software Engineers working on customer “pull” projects to produce software products. These principles provide a foundation for the working relationship across the teams. We believe these principles apply to programs that include both hardware development and software development; however, we limit our examples to software intensive development for this discussion. As we strive to produce products more affordably in this ever‐increasing, global marketplace adopting these principles will serve as a foundation for working together to develop high‐value capabilities incrementally.

Group Flow: The Genesis of Innovation

“…The author proposes that group flow is key, since it is not only conducive to efficient and creative work, but energizes and engages team members as well. It also supports each of the Principles for Agile Development (Marbach, et al 2015) and design thinking. This paper provides guidelines to establishing an external environment conducive to group flow and tools to guide and focus the team to achieve maximum value from each member's capabilities.…”

“…Colocation is optimal for facilitating both good commu nication and concentration. Experts in agile development and design thinking also advocate collocating the teams utilizing these processes (Ince 2015 andMarbach, et al 2015).…”

“…General Leslie Groves protecting Oppenheimer and the Manhattan Project is an example, as is Kelley Johnson isolating the innovative Skunk Works (Bennis 1997, 213). Transformative leaders in agile development and design thinking also attest to the need to defend the group from interruptions, time constraints, and pressure to succeed (Marbach, et al 2015).…”

“…Since we are more conditioned to be contemplative and assess all the risk ahead of time, he pushes the pendulum far in the opposite direction. Agile development experts also recommend working in "iterative, time-boxed periods" and limiting work-in-progress as a form of risk management (Marbach, et al 2015). And of course customers will not accept open-ended project durations in the name of innovation.…”

Agile Insight ‐ Gating Alternatives for Agile Projects

“…Principles for Agile Development proposes wording changes to the Manifesto and its supporting principles to make their applicability to systems engineering clear. The value statements of the Manifesto are shown to be applicable to systems overall as well as software, with a single adjustment of focusing on working capabilities rather than working software (Marbach, P. et al 2015). Table 2 summarizes these values and their use in structuring gate reviews for agile projects.…”