Nurturing the Agile Culture In the Project Office September 15, 2015

Transcription

1 Nurturing the Agile Culture In the Project Office September 15,

2 Introductions Who s in the room? 2

3 Introductions - speakers Melodi Cottongim Steve Kvavle Rachel Nedrow 3

4 Nurturing the Agile Culture in the Project Office Agenda Background Context Agile & Dept. of Licensing Changes that enable an Agile Culture Values Symbols Systems Mind-sets Results 4

5 Background / Context 5

6 Background Washington State Department of Licensing 6

7 Context - Agile Frameworks 7

8 Context: 1 Agile team in

9 Context: All Teams Agile in

10 Background: Need and Support for change Shorter delivery of projects Training Coaching All levels of the organization Acknowledgement of scope of change 10

11 Nurturing cultural change 11

12 Values 12

13 Change in values From To Adapt Control 13

14 Change in values - examples Control Locked down requirements Detailed schedule and sequence Scope we must do it all Answers to complicated how to before we start Adapt Demonstrate the working system and adapt We know the next most valuable things we will do We will do just enough Start and figure it out 14

15 Symbols 15

16 Symbols of Agile

17 Symbols of Agile Customer (product owner) present EVERYDAY

18 Symbols of Agile Fun ceremonies

19 Symbols of Agile Has the water cooler culture changed?

20 Systems 20

21 Agile Project Management Systems 21

22 How can we be Agile in a Waterfall World? Need to adapt a hybrid approach consisting of both Waterfall and Agile (SCRUM) Structure - Waterfall planning required to provide structure for State and Federal stakeholders for scheduling, funding and compliance planning Adaptability The Scrum Methodology is an Agile approach to project execution. Technology modernization and changing business requirements requires greater adaptability and closer coordination with business partners in the maneuvering execution and deployment of IT projects today 22

23 The DOL 3 Layered approach for Software Development 23

24 The Bridge from Waterfall to Scrum Five Stages evolving the work from a Charter to User Stories 24

25 Roadmap Project Integration Strategy 1. Architectural Roadmap Strategy Review Purpose: Develop proposal for mapping and integrating business strategy to the technical execution strategy Participants: SLM, Architects, Business SME s/product Owner, Analysts, PM, Technical Leads(as needed) Output/Outcome: Proposals with recommendation to the Business Strategy Team concerning the integration of approved work with current preflight/inflight commitments. Frequency: Quarterly and as required by emergent circumstances 25

26 Project/Work Effort A S O N D J F M A M J J A S O N D J F M A M J J A S O N D CD31 Done DLDV 9/16/2015 PDPS MOD 10/11/2015 CIS R&E CIS R1 CIS R2 WSP CLP Federal Compliance BTM DRIVERS SHB 1276 (Impaired Driver) ESSB5987 Fee Bill (Transportation) Non Domicile Real ID Oregon Letters 12/30/2015 Pre-Production Env. Production Support W/O's Continuous /1/2015 3/10/2015 5/1/2016 DTG Layer 1 Roadmap Q3/2015 7/1/2016 1/30/2017 9/1/2016 5/1/2017 6/1/2017 Date unknown /1/ /1/

27 Feature and Function Identification 2. Business Requirements Discussions Purpose: Define business requirements and identify high value business feature sets Participants: Business SME s, Analyst, Product Owner, PM, Testers. Architects for consultation and situational awareness. Technical Leads (only if required) for consultation. Output/Outcome: High value business feature sets and business functions and business requirements. Frequency: Ongoing as required 27

28 Architecture and Requirements planning/sizing 3. Architectural Review of Business Feature Sets Purpose: Develop a proposals that documents the technical options to implement business feature sets Participants: Architects, Technical Leads, Analysts, SLM, PM, and other technical staff as needed. Output/Outcome: Initial T-shirt sizing of business feature sets. Proposal of one or more technical options with recommended option. Approved recommendation by IS and Business Strategy Team. 28

29 Functional Roadmap & Resource planning 4. Feature Roadmap Planning Purpose: Develop a feature release roadmap ratified by the business Participants: SML, PM, Analyst, Technical Leads and Architects Output/Outcome: T-shirt sized business functions. Feature roadmap of all approved work with a planned target. 29

30 Not official: Version Aug, E2SHB 1276 Impaired Driving Legislation Effort Feature Functions Size Hours OCT NOV DEC JAN FEB MAR APR MAY Resources Pre Trial IID Restrictions Manage & Maintain (add modify remove CRUD) PODEPT (a blue screen) M 80 * Venu Display in ADR, Courts, LE, EOS(COLD fiche), Datamart M 80 * Venu/John/Sharmila/Jamie Store OOS License Numbers L 80 * Venu/Nhat/John Expand Eligibility of IIL Allow issuance of IIL to out of state driver M 80 * Nhat Create new letter for ALL IIL (including OOS driver) manually thru DOLLI S 40 * Garima/Nhat Allow issuance for additional actions M 80 * Venu/John Blood Tests - THC for PDL Add new THC codes for PDL (violation codes, DAFs, Activity/Reason codes) S 10 * John/Nhat/Venu Add new batch Letters including DOLLI XL 260 * Venu/John/Garima/Nhat Display in ADR, Courts, LE, EOS(COLD fiche), Datamart M 25 * Venu/John Correlate RCW to violation and DAF codes S 10 * John/Nhat/Venu Open Container THC (Open baggie) Minor Alcohol Event Conviction Retention Display in ADR, Courts, LE, EOS(COLD fiche), Datamart M 80 * Venu/John/Sharmila/Jamie Add new violation codes S 10 * John/Nhat/Venu Update ADR Service S 20 * Sharmila/Jamie Update existing retention tables to retain for lifetime S 10 * John/Nhat/Venu * = Production Release month Total Hours 865 SIZE HOURS E 500 hrs XL hrs L hrs M hrs S < 40 hrs 30

31 Requirements Breakdown fro Scrum execution 5. Sprint Business Function Commitment Purpose: Generate Stories with acceptance criteria and manage the distribution of stories to teams based on availability and capability. Participants: SLM, PM, Architects, Analysts, Product Owners and Team Leads Output/Outcome: Sprint Plan at the Function Level ready for distribution to Sprint Teams 31

32 Layer 2 Activities, Participants and Artifacts typical to Projects Phase Description/Tasks Owner Supporting Participants Location Output (Artifact) Business and Technical Work Review Project Manager Architectural and Requirements Planning Project Template Analysts, Business SME's, Product Owner(s), Project Manager, Service Line Manager, Service Line Manager, Technical Leads OneSource Link to the artifact Proposals with recommendation to the Business Strategy Team concerning the integration of approved work with current preflight/inflight commitments. Identify Technical SME's Project Manager Analysts, Architects, Technical Leads Technical SME's identified Identify high level project features Analyst Architects, Business Team, Product Owner(s),Project Manager, Technical Leads, Work Team Rough draft of expected features Describe the business perspective for the project Product Owner(s) Analyst, Business Team Summary of Objectives Identify top business feature priorities (High Level - subject to change) Product Owner(s) Business Team High level prioritization of draft features Stage 1 Identify High level functions Analyst Business Team, Product Owner(s) High level functions for each feature with high level workflow Review High level Features, Functions, and Business Priorities Product Owner(s) Analyst, Architects, Business Team, Project Manager, Technical Leads, Work Team Modifications based on review for above listed items Discuss high level estimates (T-Shirt sizing) DTG Architects Analyst, Business Team, Product Owner(s), Project Manager, Technical Leads, Work Team Rough estimates for Features and Functions for product Identify constraints and risks (external, schedule, resource, etc.) Project Manager Analyst, Architect (Enterprise), Product Owner(s), Technical Leads, Work Team Register Define impacts and interdependencies between different technologies/systems DTG Architects Analyst, Product Owner(s), Project Manager, Technical Leads, Work Team Diagram of systems and dependencies Identify architectural improvement opportunities & ensure technical alignment DTG Architects Analyst, Product Owner(s), Project Manager, Technical Leads, Work Team N/A - Updated Stage I document Align Technical and Business needs DTG Architects Analysts N/A - Stage I document High Level Feature Roadmap (ARTIFACT) Project Manager Analyst, Product Owner(s), Project Manager, Technical Leads, Work Team Roadmap (.mpp,.ppt,.vsd, etc.) Business Requirements Discussion Analyst Analyst, Business SME s, Product Owner(s), Project Manager, Testers. Architects for High value business Work feature sets business functions and business consultation and situational awareness. Technical Leads (only if required) for consultation. requirements discovery. Refine previously Identified business functions for each feature Analysts Business Team, Product Owner Updated Feature/Function documents Stage 2 Prioritize the value of business features/functions Product Owner(s), AAnalysts, Business SME's Prioritized list of updated Features and Functions Identify Core Requirements of functions Analysts Business SME's, Product Owner Documents and Diagrams of Features and Functions of Business Requirements Determine Business Process Flow Analysts Business SME's, Product Owner User Scenarios & Use Cases specific functions Review of Prioritized Requirements Analysts Business SME's,Product Owner(s), Project Manager, Technical Leads, Work Team Prioritized Requirements that defines project scope Architectural Review of Product Feature Sets Analyst Analysts, Architects, Project Manager, Service Line Manager, Technical Leads, other technical staff as needed. Understand high level Feature Requirements Analyst Business SME's, Project Manager, Technical Leads, Work Team, N/A Understand how technical components/subsystems connect Analyst Architect, Business SME's, Project Manager, Technical Leads, Team Diagram of systems and dependencies Identify interdependencies of affected components Analyst Business SME's, Project Manager, Technical Leads, Work Team Diagram of systems and dependencies Stage 3 Discuss possible design options Architect Analyst, Business SME's, Project Manager, Technical Leads, Work Team List of design options Determine the preferred design Architect Analyst, Business SME's, Project Manager, Technical Leads Recommended Design T-Shirt Size the Functions defined Architect Architect, Business SME's, Project Manager, Technical Leads, Work Team EPIC stories created with sizing Generate Architectural Diagrams Architect Architect, Business SME's, Project Manager, Technical Leads, Work Team Updated Architectural Diagram (.vsd,.ppt, etc.) Comprehend enterprise Architectural impact Architect Business SME's, Project Manager, Technical Leads, Work Team, Diagram of systems and dependencies? Communicate enterprise Architectural direction to ISD Architect Analyst, Business SME's, Project Manager, Technical Leads, Work Team Feature Function Roadmap & Diagram of Process Flow Feature/Functionality Roadmap Planning for DTG Project Manager Analyst, Architects, Project Manager, Service Line Manager, Technical Leads T-shirt sized business functions. Function Roadmap of all approved work with a planned target Organize and group functionality based on priority, time, logic, architecture, Project Manager Technical Leads, Technical Teams, Analyst, Product Owner Functional Work Effort Roadmap interdependency Stage 4 Ratify Work Effort Roadmap Product Owner Administrators, Asst, Administrators, Analyst, Service Line Manager, Project Manager Proposed Work Effort Roadmap Integrate project into all other service line defined work efforts Product Delivery CoService Line Manager, Project Manager, Analyst, Architect, Product Owner,Tech Team Service line functional roadmap Ratify Functional Roadmap Plan Product Owner Administrators, Asst. Administrators, Analyst, Service Line Manager, Project Manager Approved Functional Roadmap Update Roadmap Plan if needed Product Delivery CoService Line Manager, Project Manager, Analyst, Architect, Product Owner, Work Team Updated Approved Functional Roadmap Commit Product Backlog to Layer III Product Delivery Service Line Manager, Project Manager, Architects, Analysts, Product Owner(s)s and Team Coordinator Leads Sprint Plan at the Function Level ready for distribution to Sprint Teams Develop Stories and Acceptance Criteria Analyst Business SME's, Product Owner(s), Technical Leads, Testers, Product Owner Stories with Acceptance Criteria Group Stories by function and System/Application/Domain commonality Analyst Business SME's, Product Owner(s), Technical Leads, Testers, Product Owner Grouping by function by existing stories Story Time Analyst Business SME's, Product Delivery Coordinator, Product Owner(s), Technical Leads, Testers Stories point sized and ready for Work Team Stage 5 Technical Review/Discussion Architect Analyst, Business SME's, Product Delivery Coordinator, Product Owner, Technical Leads, Testers, Work Teams Understanding of work and how to approach Develop Release Roadmap for Business Features/Functions Product Delivery CoAnalysts, Architects, Product Owner(s), Project Manager, Service Line Manager, Team Leads Projected Release Roadmap Update Layer I based on the Release Roadmap Project Manager on behalf of the IS Service Line Managers Product Delivery Coordinator Updated Project Roadmap 32

33 Waterfall & Scrum Integrated Phase Who What Output Artifacts LAYER I Projects/Portfolio Discovery Requirements / Analysis Design Business / PM/Project Sponsor Identify Business requirements Analyst / Architect Identify Features High Level Feature(s) Product Owner / Business Feature(s) Priorities Ranking of Features Tech Leads / Analyst T-Shirt Sizing of Feature T-Shirt Sizing Business Requirements Defined /Charter Approved/High Level Schedule/Capacity Planning/Prioritization Analyst / Architect Identify Functions High Level Functions Product Owner Function(s) Priorities Ranking of Functions Tech Leads / Analyst T-Shirt Sizing of Functions T-Shirt Visuals Sizing (flow charts, wireframes, etc) to communicate Analyst / Architect Feature/Function Flow Business High level requirements design of functions needed to implement Analyst Conceptual Design Feature sets Developer Detailed Design How the function will be developed technically Developer Product Owner / Business Prototypes Approval of Prototypes LAYER II Features and Functions Planning Prototype to show Product Owner / Business early-on to ensure appropriate design is in place to meet customer needs Common agreement between Business and Developers on approach toward implementing function(s) LAYER III User Stories & Tasks Project in Project Server - PM brings to Developer team High level Roadmap of Features Epic Stories of all Functions, categorized under their respective features Designs created, both high level and detailed Prototype created and demonstrated to business for approval to move forward Product Owner Reprioritize Feature/Functions based on Up to date prioritized backlog business needs Sprint-Ready User Stories created, tasks created Analyst Stories for Functions Epics for large Functions / Stories for 1 to 1 functions Scrum Team Story Points Stories given point estimates Development Analyst AC Acceptance Criteria for Story Tester Test Cases Attached Test Cases to User Stories Scrum Team Prioritize individual stories based on order needed to Stack Rank complete Developer Tasks for Stories Activities Developer needed completes to complete tasks for the User Story Stories committed to Developer Development in a sprint Stories picked up by scrum teams - ready for QA Tester User Story Functionality tested based on AC Story is tested to ensure functionality is in place Stories fully tested in QA environment, and TEST Developer Demo of completed story to Product Owner Product Owner sees working functionality demo'd to Product Owner. Stories ready for Product Owner Story evaluated against AC / Test Cases Accept or rejection of Story. Story closes production Implementation Developer Deploy Story to Production Environment Functionality released from QA environment into production Stories moved to production Maintenance Stories maintained and/or improved in Developer Function maintained and improved Function continues to work and/or improve over time production 7/2/2015 S. Kvavle July 1, 2015 version

34 Mind-sets 34

35 Agile Project Management Mindsets 35

36 Project Manager Role Heavy on paper vs. heavy on doing the doing Waterfall Form project team(s) Agile/Scrum Scrum Team already in place Create high level WBS Team creates Roadmap Create Project Schedule Create project artifacts Roadmap is used to break work down into functional stories with success criteria Create charter, and risk, issue and decision logs 36

37 Project Manager Role (cont.) Big Picture keeping an eye on the goal Servant Leadership Encourage, mentor, teach Clear roadblocks Report status Contractors Budget 37

38 The Team Ensure right skill set to complete work Team self assigns work that can be done in a sprint Track velocity Adjust for out of office 38

39 Monitoring (mindset) Team Foundation Server (TFS) can be used for tracking project work 39

40 Status - Scrum Board Day-to-day progress of projects by story and task and roadblocks 40

41 Sprint Reports TFS can produce helpful project status reports such as this one 41

42 Sprint Reports (cont.) and this 42

43 Iterative Approval from customer Demos providing customers and stakeholders with a first-hand look at what s been built so far 43

44 Reporting, Communication Portfolio Status - communicating all projects status to a wide distribution including sponsors, users, stakeholders, and other interested parties Monthly Team Portfolio Report 44

45 Results of a Nurtured Agile Culture 45

46 Agile 46

47 Collaborative workplace

48 The highest value work gets done 48

49 People have fun at work 49

50 Changed culture.that permeates everything 50

51 Thanks for your time 51

52 For more information Steve Kvavle, PMP, CSM Senior Project Manager Information Services, Washington State Department of Licensing (360) Rachel Nedrow, PMP Senior Project Manager Information Services Washington State Department of Licensing (360) Melodi Cottongim Project Office Manager Information Services Washington State Department of Licensing (360)