Roles: Scrum Master & Project Manager Scrum Master: Facilitate collaborative meetings Track team performance Remove impediments (Risk, Issue) Validate team alignment to Agile framework and scope Drive accountability and cooperation of team members Deliver working software Define level of expected quality Drive planning milestones Mentor team members Focus on a single work stream and how it could impact others Request external group participation Project Manager: Validate project alignment to vision Perform Release Planning Deliver successful project Track project performance Identify areas impacting quality Escalate Risks and Issues beyond project Manage Companion and Dependent project interactions, impacts, and participation Manage and communicate project status and metrics while balancing time, cost, and scope Manage delivery against major milestone and objectives Manage project staffing and invoicing 1
Roles of the Core Team Business Analyst: Facilitate scope workshops Understands the business needs Focuses on the business value Creates artifacts Supports developers Works with Testers Tester: Identifies User Stories that are Done Creates test plans Performs testing Updates quality metrics Manages defects Developer: Creates working software Adheres to coding standards Practices Test Driven Design Collaborates with BA and Testers User Experience Designer: Facilitates design workshops Defines usability Conducts usability testing Usability Focus Learn, efficient, memorable, error, satisfaction 2
Agile Team Skills Visionary Problem Solver Product Knowledge Supportive Supportive Deals with Ambiguity Whatever It takes Applies WIT Attitude Adaptable to Change Strong Leadership Able to Multi-task Forward Thinking Effective Communicator 3
Agile Planning Vision Roadmap Project Release Iteration Daily 4
Agile Planning Levels Development Planning 5
Planning: Product Vision & Roadmap Product Vision: Validate and assess target market Determine user needs Identify critical product attributes Assess existing products (internal and competitor) High-level target timeline for launch Estimate ROI Product Roadmap: ID Task Name Start Finish Duration 1 Loyalty 03/04/2013 09/06/2013 27w 2 Guided Navigation 05/06/2013 02/28/2014 43w 3 Open API s 01/07/2013 06/06/2014 74w 4 Mobile Presentation 07/08/2013 11/22/2013 20w Q1 13 Q2 13 Q3 13 Q4 13 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Q1 14 Q2 14 Q3 14 Jan Feb Mar Apr May Jun Jul Aug Sep 6
Development: Project Plan Trade-offs The total points identified within the Trade-off Sliders table should equal 15 points in order to ensure balance. Points included in the Trade-off Sliders matrix can be adjusted to the focus or interests within a company, department, or project. The project Trade-offs are used to review to project decisions regarding risk, issue, change, or decisions. 7
Cost Time Scope Product Backlog 8
Development: Sample Release Planning 9
Development: Sample Release and Iteration Plan 10
Development: Sample Iteration Plan 11
Development: Sample Iteration Plan 12
Agile Scope Management Product Backlog identifies high level requirements User Stories and User Story Narratives further define the requirements Sample Governance Model Proposal Proposal Project Sample Governance Model Project 13
Scope: Sample Life of a User Story 14
Life of a User Story to a Card Wall 15
Traceability of Project Scope 16
Scope Decomposition 17
Agile Methodology Artifacts Agile Project Type Decision Tree Agile Project Type Decision Tree Product Backlog User Stories Project Management Plan Work Breakdown Structure Agile Guiding Principles What tool to determine if project team is setup for success with Agile methodology Why provides guidance on what projects fit into Agile methodology Who PM with help from the team When Project Initiation 18
Agile Methodology Artifacts Agile Project Type Decision Tree Product Backlog User Stories Project Management Plan Work Breakdown Structure Product Backlog What list of all requirements that will be considered for the end product Why critical tool in Scope Management Who BA is responsible to maintain When throughout the project Agile Guiding Principles 19
Agile Methodology Artifacts Agile Project Type Decision Tree Product Backlog User Stories Project Management Plan Work Breakdown Structure Agile Guiding Principles User Stories What Single document used to define the system requirements, use cases, and functional design for an iteration Why Provides for a one document view of requirements from which developers can work Who BA is responsible to maintain When throughout the project 20
Agile Methodology Artifacts Agile Project Type Decision Tree Product Backlog User Stories Project Management Plan Work Breakdown Structure Agile Guiding Principles Project Management Plan What Outlines management practices for all areas of project management Why Provides single view of how the project is being managed using Agile methodology Who PM with input from team When Created in Iteration 0, updated throughout the life of the project 21
Agile Methodology Artifacts Agile Project Type Decision Tree Product Backlog User Stories Project Management Plan Work Breakdown Structure Agile Guiding Principles Work Breakdown Structure What Agile schedule template Why Offers alignment of iterative development for Agile projects to help manage the sprints, releases, and project budget based on resource allocation. Who PM with input from team When Created in Iteration 0, updated throughout the life of the project 22
Agile Methodology Artifacts Agile Project Type Decision Tree Product Backlog User Stories Project Management Plan Work Breakdown Structure Agile Guiding Principles Agile Guiding Principles What Reference document which provides standard process, artifacts, and tools for Agile methodology Why Improve Agile planning, practices, and process alignment Who All project participants When New to Agile or as needed for review 23
Considerations for Agile Introduction Prioritize Estimates Metrics Demos Retrospective 24
Agile Scope Prioritization Investments Benefits Needs Satisfiers 25
Agile Scope Estimation Planning Poker: Finite Scale for Story Points 0, ½, 1, 2, 3, 5, 8, 13, 20, 40, 100,? Large stories should be split Not enough information to estimate Triangulate Story Point Estimates Compare stories with similar story point sizes 26
Agile Metrics Velocity Burn down Charts 27
Agile Demos Demonstrate working product functionality Not a slide presentation Gain alignment / direction on product functionality Input into Product Backlog for future release / sprint planning sessions 28
Agile Retrospectives Valuable tool offering ability to adapt learnings going forward Safe environment to share What worked well? What did not work well? What should we do different? What should be continue to do? 29
Initial Agile Project Selection Criteria Business objectives are clear Requirements can be modular or built in succession Based upon maturity or ownership of dependent products, limited number of applications being impacted Majority of teams members are allocated to the project at 80% or more Limited project duration Project leads have some experience with Agile development Business Partner engaged in project and empowered to make decisions 30
Questions? 31