Agile Project

1. Agile Project Management Matthew R. Kennedy, PhD, CSP Matthew.Kennedy@dau.mil

2. POTUS and SECDEF: “DoD Will Be Agile” • “The United States is going to maintain our military superiority with armed forces that are agile, flexible and ready for the full range of contingencies and threats.” • - President Obama • “The US joint force will be smaller and leaner.  But its great strength will be that it will be more agile, more flexible, ready to deploy quickly, innovative, and technologically advanced.  That is the force for the future.” • - Secretary Panetta Defense Security Review, 5 Jan 12

3. Benefits from Implementing Agile Ability to manage changing priorities Improved project visibility Increasedproductivity Improved team morale Faster time-to-market Better alignment between IT & Business Objectives Enhanced software quality Simplify development process Reduce risk Improved/increased engineering discipline Enhanced software maintainability/extensibility Reduce cost Manage distributed teams Source: Version One: State of Agile Survey 2011

4. Agile Does NOT Guarantee Success

5. What is Agility? • “The speed of operations within an organization and speed in responding to customers (reduced cycle times)” (Mass. Inst. Tech.)

6. Organizational Structure

7. Aspects of Product Development • Business Aspect • Responsible for the overall acquisition: contracting, funding, operational requirements, and system delivery structure • Project / System Aspect • Overall technical management. Further decompose the requirements and allocate them to software or hardware • Development Aspect • Developmental items

8. Different Focus – Same Goal Project / System Aspect Development Aspect Business Aspect Strategic Goals Contracts FundingOp. Requirements Tech. Requirements Project Planning Systems Planning Technical Standards Integration DevelopmentTest = Projects are held captive by the slowest Aspect

9. Agility within the Development Aspect In the beginning…

10. Agile Manifesto • The foundational document for Agile software development • Signed by 17 software developers in Feb 2001 • Core Values • Individuals and interactions over processes and tools • Working software over comprehensive documentation • Customer collaboration over contract negotiation • Responding to change over following a plan http://agilemanifesto.org/

11. 12 Principles of the Agile Manifesto • Continuous delivery of valuable software • Welcome changing requirements • Deliver working software in weeks/months • Worktogether daily • Build projects around motivated individuals • Face-to-face conversation • Working software is the measure of progress • Promote sustainable development • Good design enhances agility • Simplicityis essential • Self-organizing teams • Reflect on how to become more effective http://agilemanifesto.org/

12. Agile Software Development Methodologies • Scrum • eXtreme Programming (XP) • Dynamic Systems Development Method • Rapid Application Development • Crystal • Kanban • …

13. Scrum • Project management focused • One of the “agile processes” • Self-organizing teams • Product progresses in a series of “sprints” • Requirements are captured as items in a list of “product backlog” • No specific engineering practices prescribed • Uses generative rules to create an agile environment for delivering projects

14. Scrum – Product Backlog • A user Prioritized list of requirements • Time estimates completed by the team performing the work

15. Scrum – Sprint Backlog • Subset of items from the product backlog • Based on teams velocity Sprint Backlog If the teams Velocity was: 275

16. Scrum – The Sprint • Requirements CAN NOT change during the Sprint • Reflect daily on current status • What did you do yesterday? • What are you going to do tomorrow? • Did anything get in your way?

17. Scrum – Product • Potentially shippable product: • “Definition of Done” • Documented • Tested • Passed Information Assurance (IA) • Etc… • Accepted by the user • If not accepted or “Done” - the item goes back into the product backlog and NO credit is given

18. Business aspect

19. Fast, Inexpensive, Simple, Tiny (F.I.S.T.) Manifesto* • Similar to the Agile Manifesto but targets the Business Aspect • Values • Talent trumps process • Teamwork trumps paperwork • Leadership trumps management • Trust trumps oversight * Lt. Col. Dan Ward: DAU Publications

20. F.I.S.T. • Principles • A project leader’s influence is inversely proportional to the project’s budget and schedule; • Constraints foster creativity; • Fixed funding and floating requirements are better than fixed requirements and floating funding; • An optimal failure costs a little and teaches a lot; • Complexity is cost, Complexity reduces reliability, Simplicity scales, Complexity does not; • Iteration drives learning, discovery and efficiency. • Implementation Guidelines • Minimize team size and maximize team talent; • Use schedules and budgets to constrain the design; • Insist on simplicity in organizations, processes and technology; • Incentivize and reward under runs; • Requirements must be achievable within short time horizons; • Designs must only include mature technologies; • Documents and meetings: have as many as necessary, as few as possible; • Delivering useful capabilities is the only measure of success. Fixed Funding + Fixed Requirements + Fixed Schedule by Definition ISNOT AGILE

21. Business Aspect Frameworks C A B IOC FOC Engineering & Manufacturing Development Operations & Support Production & Deployment Materiel Solution Analysis Technology Development • Business Capabilities Lifecycle Framework • DoD 5000.02 Materiel Development Decision FRP Decision Review Post CDR Assessment Post PDR Assessment

22. Project / System Aspect

23. How do we… Business Aspect Project / System Aspect SoftwareAspect ?

24. Agile Practices Kennedy / Ward

25. “Traditional” Project Plan C A B IOC FOC Engineering & Manufacturing Development Operations & Support Production & Deployment Materiel Solution Analysis Technology Development Project / System Aspect Business Aspect Materiel Development Decision FRP Decision Review Post CDR Assessment Post PDR Assessment Provides Stable FundingFlexible Contracts Flexible Requirements Incremental Deliveries Etc… Enables

26. “Traditional” Project Planning Meeting Project / System Aspect (increment n) 1 … Time n Components Design Build Document Test Integrate Test IA UAT Deploy O+S

28. “Traditional” Project Execution Project / System Aspect (Increment n) Build 1 … Time n Components Design Document Test Integrate Test IA UAT Deploy O+S

29. “Traditional” Project Execution Project / System Aspect (Increment n) 1 … Time n Components Design Build Document Test Integrate Test IA UAT Deploy O+S

30. “Traditional” Project Execution Project / System Aspect (Increment n) ? ? 1 … Time n Components Design Build Document Test Integrate Test IA UAT Deploy O+S

31. “Traditional” Project Execution Project / System Aspect (Increment n) ? ? 1 … Time n Components Design Build Document Test Integrate Test IA UAT Deploy O+S

32. RESULTS!

33. “Programmed” Thought Process

34. Step 1: Go to College

35. Step 2: Get a Job

36. Step 3: Develop a Product Project / System Aspect (Increment n) Security Various Testers Testers Tech. Writers DesignEng. Etc… SysEng. Int. 1 … n Components Design Build Document Test Integrate Test IA UAT Deploy O+S

37. Everything is Stovepiped • Even Our Contracts • Development Contract • QA Contract • Technical Writing Contract • Etc…

38. Rewire How We Think

39. Agile Uses Multidisciplinary Teams Agile Traditional Domain Focused Capability Focused

40. The ‘New’ Cyber Security Domain • Universities are offering degrees in Cyber Security • Federal Government is standing up an FFRDC for Cyber Security • Departments have cyber security centers of excellence How will we implement this ‘new’ Cyber Security Domain?

41. How will we respond? Traditional Agile Cyber Security Cyber Security

42. “Agile” Project Planning Meeting Project / System Aspect (Increment n) High Risk / Priority Items Developed First Build/Test/ Document Build/Test/ Document Build/Test/ Document 1 … Integrate / Build / ?? Fixed Time n Components Integrate / Build / ?? Integrate Deploy O+S

44. “Agile” Project Execution Project / System Aspect (Increment n) High Risk / Priority Items Developed First Build/Test/ Document Build/Test/ Document Build/Test/ Document 1 … Fixed Time n Components Integrate / Build / ?? Integrate / Build / ?? Integrate Deploy O+S

45. “Agile” Project Execution Project / System Aspect (Increment n) Build/Test/ Document Build/Test/ Document Build/Test/ Document 1 … Fixed Time n Components Integrate / Build / ?? Integrate / Build / ?? Integrate Deploy O+S Passed the Next Iteration

46. “Agile” Project Execution Project / System Aspect (Increment n) Build/Test/ Document Build/Test/ Document Build/Test/ Document 1 … Fixed Time n Components Integrate / Build / ?? Integrate / Build / ?? Integrate Deploy O+S

47. Incorporates System Engineering Best Practices Configuration Mgmt. Interface Mgmt. Risk Mgmt. Project / System Aspect High Risk / Priority Items Developed First Build/Test/Document Build/Test/Document Build/Test/Document 1 … Integrate / Build / ?? Time n Components Integrate / Build / ?? Integrate Deploy Mx

48. Holistic View Business Aspect Project / System Aspect DevelopmentAspect

49. Traditional vs. Agile Project Management VS

50. The PM Spectrum AgileProject Management TraditionalProject Management Modified from: http://leadinganswers.typepad.com/leading_answers/2007/06/agile_suitabili.html