Unlike commercial Agile practitioners, the Defense sector can rarely restructure their milestones for an Agile approach. The authors show how applying Agile to Systems Engineering (SE) (“Agile SE”) can overcome these constraints. Agile SE is a natural fit within today’s Defense Acquisition Lifecycle, and can therefore bring rapid benefits to one of the largest, most needy areas of development.
This Experience Report presents a case study of a successful Agile SE deployment on a major Defense system. The project used Agile SE to analyze the system requirements and develop requirement backlogs for multiple development teams, in time for the system requirements review (SRR) program milestone. This presentation will dive into the unique adaptation of Scrum and storyboarding techniques to SE, accomplished with Model-Based Systems Engineering (MBSE) tools, using Systems Modeling Language (SysML) Activity Diagrams and Sequence Diagrams for requirements analysis.
These techniques shook up the organization, and the bumps transforming the culture will be discussed. Ultimately, this approach was embraced and successfully accelerated the SRR milestone by 70%. Topics covered will include the importance and impact of rigid Defense Milestones like the SRR, the characteristics of “Agile SE”, assembling and wrangling the teams, eliminating the review cycle, and the specific Agile MBSE technical storyboard and allocation approaches.
The topics presented in this session are highly applicable to any project that uses a traditional waterfall approach but would like to swiftly adopt Agile in their current Systems Engineering processes. This Experience Report highlights that Agile SE can rapidly inject the benefits of Agile to existing Defense programs, whose IT and system budgets exceed 3x that of than any corporation.
Attendees of this session will learn:
• An overview of the DoD acquisition lifecycle challenges and limitations, and where it could be going
• The characteristics of Agile SE, and its work products
• A real-life case study of how Agile SE teams were assembled, organized and operated
• The MBSE approach, using SysML diagrams for storyboarding and allocation
• How the requirements backlogs were generated and allocated to each development team
The following people can benefit from attending this presentation: Scrum Facilitators or Product Owners, Systems Engineers, Project Engineers, Program Managers, Project Managers, business-capture teams, University Grant applicants, Agile champions, and organization leaders.
You must be a Member to view this post and you are currently not logged in.
You can either log in below or sign up here.