TANGIBLE STRATEGIES FOR ALIGNING YOUR PROCESSES WITH AGILE

Transcription

1 Slide 0 TANGIBLE STRATEGIES FOR // ALIGNING YOUR PROCESSES WITH AGILE 2016 Project Management Symposium

2 Slide 1 Government Guidance and PMI Best Practices / Success? Agile Development Methodology

3 Slide 2 / Nearly 30 years of project management and business operations experience, primarily in IT Builds relationships, actuates performance, and analyzes business processes PMP, certified SAFe Agilist Lifelong Learner

4 Slide 3

5 Slide 4 /National Nuclear Security Administration Program Management Information System Generation 2

6 Slide 5 / How many of you are familiar with the Agile development method?

7 Slide 6

8 Slide 7 12 Principles of The Agile Manifesto 1 Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. 7 Working software is the primary measure of progress. / 2 Welcome changing requirements, even late in development. Agile processes harness change for the customer s competitive advantage. 8 Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter time scale. Business people and developers must work together daily throughout the project. Build project around motivated individuals. Give them the environment and support they need, and trust them to get the job done Continuous attention to technical excellence and good design enhances quality. Simplicity the art of maximizing the amount of work not done is essential. The best architectures, requirements, and designs emerge from self-organizing teams. 6 The most efficient and effective method of conveying information to and within a team is face-to-face conversation. 1 2 At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

9 Slide 8

10 Slide 9

11 Slide 10 G2 v1.0! /

12 Slide 11

13 Slide 12 / Product Vision Product Backlog Release Planning Sprint Planning Potentially shippable product increment Groom Backlog / Team Retrospective

14 Slide 13

15 Slide 14

16 Slide 15

17 Slide 16 Process is a Dirty Word /

18 Slide 17

19 Slide 18

20 Slide 19

21 Slide 20

22 Slide 21 / 13 artifacts in this stage alone

23 Slide 22 Software Engineering Methodology /

24 Slide 23

25 Slide 24 Agile Principle 12 / At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. -The Agile Manifesto

26 Slide 25

27 Slide 26 / The most important question that can be asked when making decisions about a project s process is: Does this make sense for us?

28 Slide 27

29 Slide 28

30 Slide 29

31 Slide 30 / Does this make sense for us?

32 Slide 31

33 Slide 32 So what is truly critical to successful change? / Ensuring that each team member s concerns are not only heard but considered

34 Slide 33

35 Slide 34 Define & use a process for instituting / change Define a common goal Provide a conducive environment for change Include team members Provide opportunities for feedback (and don't judge) Be aware of the need for iterations and refinements of the process Live the Lessons Learned process

36 Slide 35 How We Defined Our Process / Sensible adherence to SEM while maintaining our Agile roots Engage leadership Involve the entire team Ask, ask, ask,... and then listen Iterate with intention Update the process Use retrospectives Practice engaged listening

37 Slide 36 The Outcome / Annual Review 1. Project Plan 2. System Requirements Specification 3. Configuration Management and Software Change Control Plan 4. Software Quality Assurance Plan 5. Cyber Security Plan 6. Deployment Guide 7. Nondisclosure Agreement Ongoing 1. Backlog 2. Coding Standards 3. Functional System Design Documents 4. As-developed Architecture 5. Organization Chart 6. Setup and Configuration Processes 7. Release-basedTest Plans 8. Online Help/User s Guide 9. Release Notes

38 Slide 37 Software Engineering Methodology PMBOK /

39 Slide 38 /Find a straightforward way to document what you ve done and why

40 Slide 39 / PMI Knowledge Areas Project Integration Management Project Scope Management Project Time Management Project Cost Management Project Quality Management Project Human Resource Management Project Communications Management Project Risk Management Project Procurement Management Project Stakeholder Management PMI Project Management Process Groups Initiating Planning Executing Monitoring and Controlling Closing G2 Project Charter G2 Project Charter G2 Project Plan Product Roadmap G2 SRS G2 CM and Software Change Control Plan Backlog (and Backlog grooming) Release Planning Meetings Daily Scrum Weekly Team Meetings G2 Project s SharePoint Site User Training Materials G2 User Guide and Online Help Design Documents RTM Source Code and Deployed Code Customer Demos Deployment Guide Daily Scrum Weekly Team Meetings Retrospectives Meetings with Executive Sponsor QA Testing UAT Backlog (and Backlog grooming) Backlog (and Backlog Release Planning Meetings grooming) EAC EAC Reviews Monthly Cost Reporting G2 SQA Plan Application Test Plans and Reports Defect Reporting QA Testing Process Audits Code Reviews Peer Review G2 Project Plan G2 Organization Chart G2 Project, Nondisclosure Agreement G2 Project Plan G2 SRS G2 Project Plan G2 Failover Plan ORNL Cyber Security Program Plan Supplement: Nonproliferation Systems Hosted Applications Product Roadmap Backlog (and Backlog grooming) Release Planning Daily Scrum Weekly Team Meetings Retrospectives Task Board Interconnection Security Agreement between G2 and the National Security Alarm Training (NSAT) system G2 Project Plan SOWs Source Selection Criteria G2 Project Plan Daily Scrum Backlog (and Backlog grooming) Daily Scrum Weekly Team Meetings G2 Project s SharePoint Site Subcontracting Agreements Internal agreements with ORNL IT Services Division Daily Scrum Weekly Team Meetings G2 Project s SharePoint Site Daily Scrum Weekly Team Meetings Contract Compliance Receipt of Deliverables The Agile development method (used on this project) is based on routine and continuous stakeholder engagement spanning the Planning, Executing, and Monitoring and Controlling Project Management Process Groups Release Notes User Acceptance Verification User Training Contract Termination De-obligation of Funds

41 Slide 40

42 Slide 41

43 Slide 42 / How many of you ever thought something was on auto-pilot only to have a monkey wrench thrown in?

44 Slide PMI Distinguished Project Award /

45 Slide 44

46 Slide 45

47 Slide 46

48 Slide 47

49 Slide 48 / Software Engineering Methodology PMBOK

50 Slide 49

51 Slide 50 / choose and implement one or more of these

52 Slide 51

53 Slide 52

54 / Slide 53

55 Slide 54

56 Slide 55

57 Slide 56 / Remember Does this make sense for us?

58 Slide 57

59 G2 Planning Meeting March 2016 Slide 58 /

60 Slide 59 To improve a highly functioning Agile team: / Listen, gather necessary data, and proceed with intention

61 Slide 60

62 Slide 61

63 Slide 62

64 Slide 63

65 Slide 64

66 Slide 65

67 Slide 66 / Processes with Agile, PMP

68 Slide 67 Thank you for attending // Tangible Strategies for Aligning Your Processes with Agile 2016 Project Management Symposium