An Application of Agile Principles to the Systems Engineering Process
1
Presenter: Zain Malik Authors: Zain H. Malik, Dr. Enrique Campos-Nanez, Dr.
Pavel Fomin, Dr. James Wasek
November 2, 2013
Copyright © 2013 by Zain Malik. Permission granted to INCOSE to publish and use
Overview & Purpose
2
• Systems Engineering Processes and Challenges
• Agile Overview
• Framework for Implementing Agile Principles into Systems Engineering Process
• Case Study Demonstrating Proposed Method
To illustrate the benefits of applying agile principles to the Systems Engineering Process
Systems Engineering Models
3
Prototypes Activities Artifacts
Detailed process control Formal deliverables
Gate reviews
Improve speed Mass production applications
Detect design flaws
V-Model Spiral Model
Prototyping Model
Sequential design process Documentation
Waterfall Model
Challenges of Traditional Systems Engineering Processes
Implementation of the Systems Engineering Processes presents challenges depending upon the implementation model:
! Lack of up front information ! Cost vs. benefit of formal documentation ! Responding to change ! Requirements driven ! Lack of focus on customer satisfaction
4
Principles behind the Agile Manifesto
! Customer satisfaction
! Early and continuous delivery
! Changing requirements
! Performance to shorter timescale
! Work together throughout the project
! Sharing information
! Sustainable development
! Reducing unnecessary work
! Simplicity
! Self-organizing teams
! Lessons learned
References: http://agilemanifesto.org/principles.html
5
Traditional vs. Agile
6
Challenges to Agile Adoption
1. Teams had difficulty collaborating closely
2. Procurement practices may not support Agile projects
3. Teams had difficulty transitioning to self-directed work
4. Customers did not trust iterative solutions
5. Staff had difficulty committing to more timely and frequent input
6. Teams had difficulty managing iterative requirements
7. Agencies had trouble committing staff
8. Compliance reviews were difficult to execute within an iteration timeframe
9. Timely adoption of new tools was difficult
10. Federal reporting practices do not align with Agile
11. Technical environments were difficult to establish and maintain
12. Traditional artifact reviews do not align with Agile
13. Agile guidance was not clear
14. Traditional status tracking does not align with Agile
GAO Report 12-681 Effective Practices and Federal Challenges in Applying Agile Methods
7
Customer High-level
Requirements
Systems Concept
(Function A)
Systems Concept
(Function B)
Systems Concept
(Function C)
Systems Concept
(Function D)
Systems Engineering
Customer Spec
Customer Inquiry / Project Vision
Iteration 1
Function A
Iteration 2
Function B
Function D
Iteration 3
Function C
Software Engineering
System Build A
Iteration 1
Iteration 2
System Build B
Iteration 3
FINAL PRODUCT
Hardware 1
Iteration 1
Hardware 2
Iteration 2
Iteration 3
Hardware Engineering
Systems Integration
Application of Agile Principles
Resource: E. Fale, Z. Malik, Agile Principles to SE in the Commercial Environment (2013)
Agile Application Team Structure
9
! Small Cohesive team
! Sub-system leads
! Permission to make quick decisions
! Access to sponsor
! Flattened organization
! Ability to bring in experts
! Program manager reports directly to customer in charge of program
! Program deputies co-located
Traditional Team Structure
Modified Team Structure
Framework for Agile Application
10
Concept Stage Development Stage Production Stage Utilization Stage
Retirement Support Stage
Planning Requirements, Design, Development, Integration & Test Operations & Maintenance Disposal
Product Backlog
Sprint Backlog
Release M
Sprint 1 Sprint 2 Sprint N
Requirements based on priority
Design Development
Test
Sprint Review
New Requirements / Modification
Release 1
Sprint 1 Sprint 2 Sprint N
Release 2
Sprint 1 Sprint 2 Sprint N
INCOSE SE Process
Human Portable Radiation Detection System Case Study
! A Department of Homeland Security program
! Developed for Transportation Security Administration, Coast Guard, and Customs and Border Protection
! Developed for secondary screening
! Demonstrates the application of agile systems engineering for a mixed hardware and software project
! Design and develop a fully functional radiation detection system
11
HPRDS Team Structure
! Small Cohesive team
! Sub-system leads
! Permission to make quick decisions
! Access to sponsor
! Flattened organization
! Ability to bring in experts
! Vendor program manager reported directly to the head of the program
12
Sponsor Program Manager
Software Lead
Hardware Lead
Nuclear Detection
Module Lead
Lead Systems Engineer
Software Engineers
Hardware Engineers
Nuclear Detection Engineers
Part-time SME Support
HPRDS Process
13
System
M 1
SubSys 1
SubSys 2
SubSys 3
M 2 M 3 M 4 M 5 M 6 M 7 M 8 M 9 M 10 M 11 M 12 M 13 M 14 M 15 M 16 M 17
R1 R2 R3 R F
Sprint D
esig
n
Del
iver
Develop Test
Review
Release X
Inte
grat
e
Del
iver
Test
Review
! Process flow made it possible to meet cost and schedule
! Development was performed concurrently
! Used the concept of build a little, test a little and learn a lot
! Focused on meeting the needs of the customer
! Minimized documentation
Concepts:1 and 2 Concept 3 Concept 4 Concept 5 TODAY
HPRDS Product Concepts
14
Application & Lessons Learned
Applying Agile Principles to the systems engineering lifecycle process ! Small teams with direct link to sponsor ! Give authority to make decisions ! Allow outside help as needed ! Co-locate leaders ! Use interactive design reviews ! Tailor out irrelevant processes ! Test and analyze as fast as possible
15
