BIO PRESENTATION W3 6/28/2006 11:30 AM R ISK M ANAGMENT ON AN A GILE P ROJECT Michele Sliger Rally Softw are Development Better Software Conference June 26 – 29, 2006 Las Vegas, NV USA
Michele Sliger Michele Sliger has worked in software development for almost 20 years. Michele has extensive experience in agile methodologies, having employed agile practices as a founding member of the engineering teams at biotech start-ups UroCor and Genomica. At Genomica, Michele honed her Scrum and XP skills while working under Mike Cohn, a recognized founder of the Agile movement. She carried that experience forward into Qwest, where she served as an XP Coach on a team tasked with developing high-profile financial applications. She has an undergraduate degree in MIS and an MBA. She is a certified Project Management Professional (PMP), a Certified Scrum Master (CSM) and an active member of the board of the Agile Denver chapter. Currently, Sliger works as an agile consultant at Rally Software Development, where she trains software development teams in agile methodologies. In addition to her work for Rally, Sliger is also an adjunct faculty member of the University of Colorado where she teaches Software Project Management to graduate engineering students. Throughout her career, she has performed the gamut of software development roles, including programmer, database administrator, quality assurance manager, process manager and project manager.
Risk Management on an Agile Project Presented by Michele Sliger Agile Coach and PMP Better Software Conference & Expo 2006
Background on Speaker � Michele Sliger � 15+ years software development experience � PMP (Project Management Professional) � CSM (Certified Scrum Master) � 6 years experience on Agile teams � Agile Denver Board Member � Currently an Agile consultant for Rally Software Development � Adjunct instructor at the University of Colorado - Boulder 2 Better Software Conference & Expo 2006
Objectives for Today � What you will learn: � The differences between risk management in traditional and agile environments � Where the project manager and the team fit in the agile risk management process � Typical risk management activities on an agile project 3 Better Software Conference & Expo 2006
A Brief Agile Overview Better Software Conference & Expo 2006
Agile Principles— The Agile Manifesto “We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: � Individuals and interactions over processes and tools � Working software over comprehensive documentation � Customer collaboration over contract negotiation � Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more.” -- http://www.agilemanifesto.org/ 5 Better Software Conference & Expo 2006
Agile — Project Vision Drives the Features Waterfall Agile The Plan creates The Vision creates cost/schedule estimates feature estimates Constraints Features Cost Schedule Value / Vision Driven Plan Driven Estimates Cost Schedule Features 6 Better Software Conference & Expo 2006
A Generalized Agile Process • Feature 1 Release 1: Theme • Feature 2 • Feature 3a R Release Backlog Iteration 1 Iteration 2 Iteration 3 Iteration … Backlog • Story 1 • Story 1 • Story 3 • Story 5 • Story 8 • Story 11 • Story 2 • Story 2 • Story 4 • Story 6 • Story 9 • Story 12 • Story 3 • Story 7 • Story 10 • Story … • Story … 7 Better Software Conference & Expo 2006
Measuring the Transition Agile Development Iterative and Acceptance Waterfall Iterative Parallel Incremental Test Driven Year + 2 weeks Cycle Time Increase Throughput Whole Increment Detailed Decrease Investment Project Inventory Most defects Most Defects caught in Feedback caught in Decrease Operating Expense the feature Delays system test development $1,200,000 $50,000 Decrease Risk! Risks 8 Better Software Conference & Expo 2006
The Agile Framework Addresses Core Risks � Intrinsic schedule flaw (estimates that are wrong and undoable from day one, often based on wishful thinking) A Detailed estimation is done at the beginning of each iteration � Specification breakdown (failure to achieve stakeholder consensus on what to build) A Assignment of a product owner who owns the backlog of work � Scope creep (additional requirements that inflate the initially accepted set) A Change is expected and welcome, at the beginning of each iteration � Personnel loss A Self-organizing teams experience greater job satisfaction � Productivity variation (difference between assumed and actual performance) A Demos of working code every iteration Core risks from Tom DeMarco and Tim Lister: “Risk Management During Requirements” IEEE Software 9 Better Software Conference & Expo 2006
Relating traditional risk management activities to agile practices Better Software Conference & Expo 2006
Risk Management Planning The process of deciding how to approach and conduct risk management – Traditional Agile � Planning meetings with � Review of corporate risk managers and corporate requirements and representatives discussions of need � Resulting in a formal � Little or no documentation document outlining the risk on the process management process � Merging corporate � Tell the team requirements into emergent team activities 11 Better Software Conference & Expo 2006
Risk Identification Determining which risks might affect the project and documenting their characteristics – Traditional Agile � Via checklists, doc � Via info gathering, reviews, info gathering, assumption analysis assumption analysis, � In every planning diagramming meeting with the whole � In limited meetings team � Formally documented � Informally documented 12 Better Software Conference & Expo 2006
Risk Analysis Analysis and prioritization, determining which risks warrant response – Agile Traditional � Qualitative and � Qualitative Quantitative � Prioritization � Prioritization (Probability and (Probability and Impact) Impact) � Risks to respond to and � Risks to respond to and risks to watch risks to watch 13 Better Software Conference & Expo 2006
Risk Response Planning Developing options and actions to reduce threats and increase opportunities – Traditional Agile � One or more people � The team brainstorms assigned to develop strategies*: strategies: � Avoid � Avoid � Mitigate � Mitigate � Contain � Plan Contingency � Evade � Transfer � Accept *From “Waltzing with Bears” DeMarco & Lister 14 Better Software Conference & Expo 2006
Risk Monitoring and Controlling Watching for new risks, tracking and validity of identified risks, tracking and reviewing risk responses – Traditional Agile � Risk reassessment � Risk reassessment in planning meetings � Risk audits � Reviews and � Variance/trend analysis Retrospectives � Technical performance � Task Boards and measurement Burndown Charts � Reserve review � Daily Stand-up meetings � Status meetings 15 Better Software Conference & Expo 2006
Risk Management Techniques for Agile Projects Better Software Conference & Expo 2006
Identifying Risks in Planning 17 Better Software Conference & Expo Meetings 2006
Identification Daily Daily Stand-up Meeting • Done since last meeting • Plan for today • Obstacles? 24 hours 18 Better Software Conference & Expo 2006
Risk Analysis and Response 19 Better Software Conference & Expo Planning 2006
Response Planning, Monitoring, Controlling 20 Better Software Conference & Expo 2006
Response Planning, Monitoring, Controlling 21 Better Software Conference & Expo 2006
22 Monitoring Better Software Conference & Expo 2006
Summary � Risk management is owned by the team � The project manager facilitates the process and makes the results visible � Risks are identified in all planning meetings: release, iteration, and daily � Risks are analyzed and addressed in iteration and release planning meetings – the focus is on qualitative analysis, not quantitative � Risks are monitored by the use of high visibility information radiators, daily stand-ups, and iteration reviews and retrospectives 23 Better Software Conference & Expo 2006
The Art of the Possible “People who don’t take risks generally make about two big mistakes a year. People who do take risks generally make about two big mistakes a year.” – Peter Drucker 24 Better Software Conference & Expo 2006
Better Software Conference & Expo 2006 msliger@rallydev.com Thank You!
Additional Sources Websites: � http://www.agilemanifesto.org/ � http://www.agilealliance.com � http://www.scrumalliance.org � http://www.rallydev.com/agile_knowledge.jsp Books: � Waltzing with Bears by Tom DeMarco and Tim Lister � Agile Project Management with Scrum by Ken Schwaber � Lean Software Development by Mary and Tom Poppendieck 26 Better Software Conference & Expo 2006
Recommend
More recommend