Abstract
AbstractCurrent technical oversight approaches (e.g., Stage‐Gate reviews) are not agile – their expectations are not aligned with agile development cadences, and they are not adequately responsive to continuous unpredictable change. These mismatches lead to the (incorrect) assertion that agile projects don't need technical oversight, and to more accurate concerns that current gate reviews do not effectively provide insight into gaps and risk on agile projects. Large complex agile efforts need a light weight, interactive approach to technical oversight that provides insight in the form of good predictive feedback to agile projects with minimal burden of labor on the project and the reviewers. Fixed expectations of how oversight is done, and non‐agile oversight approaches written into contracts and processes impede the evolution of gating for agile projects. This paper explores ways to provide insight and responsive forward looking actionable guidance for agile projects in the context of government and defense programs. It proposes a general oversight approach that produces minimal drag and disruption and keeps pace with agile product development.
Sign-in/Register to access full text options 
Free) 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
