Applying Agile Copyright Lockheed Martin Corporation 2004 Applying Agile Processes at Lockheed Martin George Wolke 17 March 2004

Applying Agile Copyright Lockheed Martin Corporation 2004 Agenda A survey of 5 programs that used Agile to some degree: –Maritime Systems and Sensors –Aeronautics –Space Systems Organized as follows: –Agile processes/practices used –What went well –What didn’t go quite so well Summary of results (are there common threads?)

Applying Agile Copyright Lockheed Martin Corporation 2004 Agile Processes Used Project Planning –Sprint Planning –Backlog Lists –Risk Management –Manage scope, not cost/schedule/quality Design –Use agile modeling techniques –Keep it simple –Document just enough to keep you going Implementation and Test –Pair Programming –Refactoring –Test driven design –Continuous integration –Development on the target system

Applying Agile Copyright Lockheed Martin Corporation 2004 Agile SW Development – What Went Well Daily SCRUM Meetings Limited Management Involvement Team Empowerment/Ownership Maintain Focus on Current Sprint Facilitates Handling Requirements Creep Minimal Interruptions Open Design Single Source of Work Prioritization (SCRUM Master) Controlled the Chaos of Conflicting Interests and Needs Daily SCRUM questions: What have you done since the last meeting? What is in your way/need help with? What will you accomplish between now and the next SCRUM meeting?

Applying Agile Copyright Lockheed Martin Corporation 2004 Agile SW Development – What Went Well? Customer observation Continuous prototypes Customer testing Plan in “stories” not SLOC Plan in short releases Plan for change Control scope, not cost, schedule, or quality Agile models/reviews: –UML models –Use case analysis –Use case reviews Continuous integration Requirements were expected to evolve through discovery Resist the urge to add software because of what you might think will be needed later. This adds to complexity and cost of the product under current development. This is not to be confused with designing smart with the idea of flexibility and expandability.

Applying Agile Copyright Lockheed Martin Corporation 2004 Agile SW Development – What Can We Do Better? Be Realistic in Expectations Manage by Metrics that Allow for Flexibility Continued Focus on Lean Thinking Walkthrough Preparation and Meeting Focus

Applying Agile Copyright Lockheed Martin Corporation 2004 Summary of Results – Common Threads What went well: –Team empowerment/group ownership –Plan for and embrace change –Short cycle times allowed for prompt and frequent feedback –Continuous integration –Customer involvement –Pair Programming

Applying Agile Copyright Lockheed Martin Corporation 2004 Summary of Results – Common Threads What can we improve on: –Increased levels of stakeholder involvement –Manage expectations –Agile development processes require agile organizational processes