An Application of Agile Principles to the Systems Engineering Process - - PowerPoint PPT Presentation

an application of agile principles to
SMART_READER_LITE
LIVE PREVIEW

An Application of Agile Principles to the Systems Engineering Process - - PowerPoint PPT Presentation

An Application of Agile Principles to the Systems Engineering Process November 2, 2013 Presenter: Zain Malik Authors: Zain H. Malik, Dr. Enrique Campos-Nanez, Dr. Pavel Fomin, Dr. James Wasek by Zain Malik. Permission granted to INCOSE to


slide-1
SLIDE 1

An Application of Agile Principles to the Systems Engineering Process

Presenter: Zain Malik

Authors: Zain H. Malik, Dr. Enrique Campos-Nanez, Dr. Pavel Fomin, Dr. James Wasek

November 2, 2013

by Zain Malik. Permission granted to INCOSE to publish and use

slide-2
SLIDE 2

Overview & Purpose

  • 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

slide-3
SLIDE 3

Systems Engineering Models

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

slide-4
SLIDE 4

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

slide-5
SLIDE 5

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

s: http://agilemanifesto.org/principles.html

slide-6
SLIDE 6

Traditional vs. Agile

slide-7
SLIDE 7

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

12-681 Effective Practices and Federal Challenges in Applying Agile Methods

slide-8
SLIDE 8

Customer High-level Requirements Systems Concept (Function A) Systems Concept (Function B) Systems Concept (Function C) Systems Concept (Function D)

Systems Engineering

tomer Spec

r Inquiry / t Vision

Iteration 1

Function A

Iteration 2

Function B Function D

Iteration 3

Function C

Software Engineering

System

Iterati Iterati

System

Iterati

FI FINAL L P

Hardware 1 Iteration 1 Hardware 2 Iteration 2 Iteration 3

Hardware Engineering Systems Inte

Application of Agile Principles

Fale, Z. Malik, Agile Principles to SE in the Commercial Environment (2013)

slide-9
SLIDE 9

Agile Application Team Structure

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

slide-10
SLIDE 10

Framework for Agile Application

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

INCO Proc

slide-11
SLIDE 11

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

slide-12
SLIDE 12

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

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

slide-13
SLIDE 13

HPRDS Process

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

R1 R2 R3

Sprint

Design Deliver Develop Test Review

Release X

Integrate Test Review

Process flow made it possible to meet cost and schedule evelopment was performed concurrently sed the concept of build a little, test a little and learn a lot

  • cused on meeting the needs of the customer

Minimized documentation

slide-14
SLIDE 14
  • ncepts:

1 and 2 Concept 3 Concept 4 Concept 5

TODAY

HPRDS Product Concepts

slide-15
SLIDE 15

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

slide-16
SLIDE 16

Questions?

  • ntact Information: Zain H. Malik

zmalik4@gmail.com