Abstract
AbstractThe U.S. Department of Energy's (DOE's) Pacific Northwest National Laboratory (PNNL) and its clients have historically used a structured, plan‐driven approach to provide continuity, direction, and control to large, multi‐year programs. Projects within these programs vary greatly in size, complexity, level of maturity, technical risk, and clarity.On a recent program one of our clients employed hierarchical requirements methodologies for technology development projects, with complex interfaces and tight project schedules, which necessitated frequent end‐to‐end product demonstrations throughout system development. In response PNNL embedded Agile engineering practices into the plan‐driven project life cycle to benefit from the Agile principle of delivering frequent, interim, and functioning products regularly throughout the project's period of performance.This paper describes the application of those Agile practices on a large command and control system development effort. It discusses how the project team benefitted from both the plan‐driven project execution and the rapid prototyping, integration, and client feedback made possible with the implementation of Agile practices. Furthermore, this paper discusses the tools and implementing mechanisms used to transition between each methodology.
Sign-in/Register to access full text options 
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 callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
