Satisfyyging DoD Contract Reporting With Agile Artifacts · Report Documentation Page Form Approved...

18
Defense, Space & Security Lean-Agile Software Satisfying DoD Contract Reporting With Agile Artifacts Dick Carlson [email protected] SSTC 2011 BOEING is a trademark of Boeing Management Company. Copyright © 2011 Boeing. All rights reserved.

Transcript of Satisfyyging DoD Contract Reporting With Agile Artifacts · Report Documentation Page Form Approved...

Defense, Space & SecurityLean-Agile Software

Satisfying DoD Contracty gReporting With Agile Artifacts

Dick [email protected] SSTC 2011

BOEING is a trademark of Boeing Management Company.Copyright © 2011 Boeing. All rights reserved.

Report Documentation Page Form ApprovedOMB No. 0704-0188

Public reporting burden for the collection of information is estimated to average 1 hour per response, including the time for reviewing instructions, searching existing data sources, gathering andmaintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information,including suggestions for reducing this burden, to Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, ArlingtonVA 22202-4302. Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to a penalty for failing to comply with a collection of information if itdoes not display a currently valid OMB control number.

1. REPORT DATE MAY 2011 2. REPORT TYPE

3. DATES COVERED 00-00-2011 to 00-00-2011

4. TITLE AND SUBTITLE Satisfying DoD Contract Reporting With Agile Artifacts

5a. CONTRACT NUMBER

5b. GRANT NUMBER

5c. PROGRAM ELEMENT NUMBER

6. AUTHOR(S) 5d. PROJECT NUMBER

5e. TASK NUMBER

5f. WORK UNIT NUMBER

7. PERFORMING ORGANIZATION NAME(S) AND ADDRESS(ES) Boeing Defense, Space & Security,PO Box 516,St. Louis,MO,63166

8. PERFORMING ORGANIZATIONREPORT NUMBER

9. SPONSORING/MONITORING AGENCY NAME(S) AND ADDRESS(ES) 10. SPONSOR/MONITOR’S ACRONYM(S)

11. SPONSOR/MONITOR’S REPORT NUMBER(S)

12. DISTRIBUTION/AVAILABILITY STATEMENT Approved for public release; distribution unlimited

13. SUPPLEMENTARY NOTES Presented at the 23rd Systems and Software Technology Conference (SSTC), 16-19 May 2011, Salt LakeCity, UT. Sponsored in part by the USAF. U.S. Government or Federal Rights License

14. ABSTRACT

15. SUBJECT TERMS

16. SECURITY CLASSIFICATION OF: 17. LIMITATION OF ABSTRACT Same as

Report (SAR)

18. NUMBEROF PAGES

17

19a. NAME OFRESPONSIBLE PERSON

a. REPORT unclassified

b. ABSTRACT unclassified

c. THIS PAGE unclassified

Standard Form 298 (Rev. 8-98) Prescribed by ANSI Std Z39-18

EnvironmentBoeing Defense, Space & Security| Lean-Agile Software

Environment

MIL-STD-1521B, the FAR, and DFAR are based on waterfall life-cycle stages for technical reviews and contract reporting, and have specific contract metrics and reporting requirements

“Agile concepts ha e been aro nd for decades In recent ears Agile“Agile concepts have been around for decades. In recent years, Agile matured and personnel became skilled in applying Agile; some DoD contractors started to build internal Agile capabilities and use Agile on DoD programs. Many DoD acquisition programs have also begun to p g y q p g gpropose and use Agile processes, attempting to take advantage of contractor capabilities; however, they have done this without (as yet) any formal DoD guidance, templates, or best practices.”

How can proven Agile practices and principles be applied to projects that are not software centric?

(Source: Considerations for Using Agile in DoD Acquisition, April 2010, SEI)

Copyright © 2011 Boeing. All rights reserved. 2

not software-centric?Boeing experience implementing Agile system engineering activities

OverviewBoeing Defense, Space & Security| Lean-Agile Software

Overview

In the context of this presentation “Agile Systems Engineering” or p g y g gAgileSE is limited to the definition and development of requirements for software systems

We will identify specific systems engineering activities to which Agile was applied

We will also include recommendations for applying Agile for project execution

What will not be included is production relating to assembly and manufacturing and contractual impacts

Copyright © 2011 Boeing. All rights reserved. 3

Agile Practices Applied to SE “V” ModelBoeing Defense, Space & Security| Lean-Agile Software

Agile Practices Applied to SE “V” Model

Agile practices applied during these activities

Copyright © 2011 Boeing. All rights reserved. 4Source: http://www.thefullwiki.org/V-Model

Agile SE/SW Experience ModelBoeing Defense, Space & Security| Lean-Agile Software

Agile SE/SW Experience ModelAgile Software Engineering Activities

Agile Systems Engineering Activities

Controlled Peer

Requirements decomposed into

Analysis

Includes

Defined anddeveloped SWrequirements

Product Backlog

IterationBacklog

Design

C d

and Managed PeerReviews

decomposed into quantifiable tasks

Includes documentation

Code

Test

SE Iterations

SW Iterations

Prioritized

Requirements

Includes documentation

SW Iterations

Acceptance FunctionalSystem Unit

Requirements estimated by

the team

Demo &

Copyright © 2011 Boeing. All rights reserved. 5

testing Systemintegration integration

Automated Testing and Continuous Integration

Deployment

Source: Dick Carlson

Getting StartedBoeing Defense, Space & Security| Lean-Agile Software

Getting Started

Conduct an assessment to determine if implementing Agile adds or p g greduces risk. For example:

Is the customer willing to actively participate, i.e. requirements clarification, product demos, incremental development?Will th b l d f t t i ti ?Will there be regular and frequent customer communication?Would the customer be willing to drive and prioritize requirements?Is the customer willing to provide frequent feedback on items completed?

If Agile can be applied with minimal risk, then train team in Agile

Request an Agile coach be assigned to the project

Focus more on planning than developing plans

Copyright © 2011 Boeing. All rights reserved. 6

Focus more on planning than developing plans

Implement Simple Agile PracticesBoeing Defense, Space & Security| Lean-Agile Software

Implement Simple Agile Practices

Empower teams to self-manage and self-organizep g g

Close customer collaboration

Daily stand-up meetings

Planning and estimating

Short iterations

Prioritize requirements

Copyright © 2011 Boeing. All rights reserved. 7

Artifact reviews – demonstrate functional prototypesSource of “Agile”: www.agilealliance.org

Prioritize Activities & Work ProductsBoeing Defense, Space & Security| Lean-Agile Software

Prioritize Activities & Work Products

Complete most important stuff firstp p

Lean out verbose documentation

Defer architectural and design decisions until needed

Verify all completed items

Review completed items with key stakeholders

Copyright © 2011 Boeing. All rights reserved. 8

Establish a VisionBoeing Defense, Space & Security| Lean-Agile Software

Establish a Vision

A vision that encourages and supports:g ppCustomer SatisfactionFrequent DeliveryMotivated TeamMotivated TeamWorking SoftwareTechnical ExcellenceEmergent DesignEmbracing ChangeCollaborationHigh BandwidthSustainable PaceSimplicity

Copyright © 2011 Boeing. All rights reserved. 9

SimplicityContinuous Improvement

Create a Project RoadmapBoeing Defense, Space & Security| Lean-Agile Software

Create a Project Roadmap

<Date> <Date> <Date> <Date><Date> <Date>

Release 1 Release 2 Release 3 Release 4 Release 5 Release n

<Date>

Iterations 1-n Iterations 1-n Iterations 1-n Iterations 1-n Iterations 1-nIterations 1-n

SE Activities &Work Products

SE Activities &Work Products

SE Activities &Work Products

SE Activities &Work Products

SE Activities &Work Products

SE Activities &Work Products

Project Lifecycle

Copyright © 2011 Boeing. All rights reserved. 10Source: Dick Carlson

Document Your Agile ApproachBoeing Defense, Space & Security| Lean-Agile Software

Document Your Agile Approach

Plan a release strategy through a series of short iterations to complete gy g pwork products

Use simple Agile modeling techniques p g g q

Conduct daily standup meetings to identify previous work completed, what needs to be completed next, and any impedimentswhat needs to be completed next, and any impediments

Hold iteration reviews at the end of every iteration with key stakeholdersstakeholders

Conduct team retrospectives to identify what worked well and improvement opportunities

Copyright © 2011 Boeing. All rights reserved. 11

improvement opportunities

Establish a Viable Release PlanBoeing Defense, Space & Security| Lean-Agile Software

Establish a Viable Release Plan

Identify artifacts that will be developed incrementallyy p y

Explain the importance of active customer involvement and feedback

Elaborate through the project’s Agile approach

Obtain customer approval

Distribute to everyone!

Update often

Copyright © 2011 Boeing. All rights reserved. 12

Enlighten Your CustomersBoeing Defense, Space & Security| Lean-Agile Software

Enlighten Your Customers

Talk to them – let them know there is a viable alternative to the t f ll d l (3 t d thi )waterfall model (3 ways to do this)Respond to a proposal need for AgilePre-proposal – recommend an Agile approachPost proposal provide examples and show them howPost-proposal – provide examples and show them how

Identify the importance of their role in product development

Train them on how to do this

Get them to actively participate in the development validation processGet them to actively participate in the development validation process – their feedback is vital!

Develop an accurate and meaningful release strategy

Copyright © 2011 Boeing. All rights reserved. 13

Develop an accurate and meaningful release strategy

Meet Customers Half WayBoeing Defense, Space & Security| Lean-Agile Software

Meet Customers Half-WayProject Milestone Reviews

OctoberCDR

JulyPDR

SeptemberSWCDR

AprilSSR

JanuarySWTRR

FebruarySRR

JuneSWPDR

SE Release 2 SE Release 3 SE Release 4SE Release 1

January January

February March April May June July August September October November December January

A il

SE Review

SE Review

SE Review

SE Review

Iteration ActivitiesIteration Activities Iteration ActivitiesIteration Activities

Agile Requirements Engineering

SW Release 4SW Release 3SW Release 2SW Release 1

Agile Software

Copyright © 2011 Boeing. All rights reserved. 14

SW Demo

SW Demo

SW Demo

SW Demo

Iteration ActivitiesIteration Activities Iteration ActivitiesIteration ActivitiesDevelopment

Source: Dick Carlson

Make Everything TransparentBoeing Defense, Space & Security| Lean-Agile Software

Make Everything Transparent

Measure performance productivity and qualityMeasure performance, productivity and quality

Keep all work visible to everyoneKeep all work visible to everyone

Announce all activitiesAnnounce all activities

Celebrate successes!Celebrate successes!

Copyright © 2011 Boeing. All rights reserved. 15

Boeing Defense, Space & Security| Lean-Agile Software

Copyright © 2011 Boeing. All rights reserved. 16Slide 16Slide 16

Boeing Defense, Space & Security| Lean-Agile Software

Copyright © 2011 Boeing. All rights reserved. 17Slide 17Slide 17