Copyright 2006 - David Churchville - www.extremeplanner.com XP and Agile Planning David Churchville ExtremePlanner Software www.extremeplanner.com XP Fishbowl.

Slides:



Advertisements
Similar presentations
Copyright © , Armstrong Process Group, Inc., and others All rights reserved Made available under EPL v1.01 Project Management Review Eclipse Process.
Advertisements

Iteration Planning.
Walter Bodwell Planigle. An Introduction – Walter Bodwell First did agile at a startup in 1999 Got acquired by BMC in 2000 and spent the next 8 years.
Steve Collins Richland County IT Manager Agile.  Have Fun  Learn About Agile  Tell Some Stories.
AgileMan Consulting So what the heck is Agile? It came about as a response to the high failure rate of software projects (> 60%), where failure means late,
What is Agile? Agile is a software methodology based on iterative and incremental development, where requirements and solutions evolve through collaboration.
C O N F I D E N T I A L 4-May-15 1 Attendee Management - Being Agile Attendee Management.
Agile Planning. The problem with documentation Argument: “Heavy” documentation too much for most business-style projects.
ECE44x SCRUM Overview slides adapted from Marty Stepp
Agile Project Management with Scrum
What Is Agile? Agile is a group of software development methodologies Scrum Extreme Programming (XP) Lean Etc. Key Characteristics: Small increments Adaptive.
BTS530: Major Project Planning and Design Iterative Development References: Agile & Iterative Development, by Craig Larman, 2004, Addison Wesley. Agile.
An Introduction to Agile SCRUM Methodology
Scrum. An evolutionary/iterative/incremental/agile software process The main roles in Scrum are: – Scrum team: Team of software developers – Scrum master.
Agile Development.
The Business Analyst Role in Agile Projects
Scrum CS These slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
© Timothy Korson Page 1 Scrum by Dr. Korson For CPTR 209 Software Engineering Version
Agile Project Management
Agile Process Models. Prescriptive models don’t work It is unrealistic to not have changes. Why? The Agile Manifesto: Individuals and interactions over.
Agile-SCRUM. Introduction to SCRUM Sanil Xavier What is Scrum?
1 Agile Estimating and Planning October, 2013 Technion, Israel Prof. Fabio Kon University of Sao Paulo, Brazil
Agile Methodologies for Project Management By – Komal Mehta.
Trusted IT Group. The challenge: 40 active, concurrent IT projects  Unsatisfactory Project Delivery.
Roles Managers Technical Team Leaders Programmers Customers Database Administrators Instructors.
© 2010 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property. Deeper Dive Into: User Stories.
Software Development Landscape
Agile Software Development Brian Link
What is Scrum Process? Where is it used? How is it better?
1 SCRUM 22/02/2009 By Siemen Bastiaens >>
Alcatel-Lucent CDC Workshop, Coaching & Knowledge Transfer Project Management.
Release and Iteration Planning September 13, 2008.
5. Planning.
Information Development Projects
1 Software Process Models-ii Presented By; Mehwish Shafiq.
Planning Game in Artifacts Tracker (AT) Project Michal Pilawski.
Agile Concepts - II “Agile” Estimating & Planning Nupul Kukreja 5 th November, 2014.
Agile Planning. The problem with documentation Argument: “Heavy” documentation too much for most business-style projects.
AP-1 5. Project Management. AP-2 Software Failure Software fails at a significant rate What is failure? Not delivering it on time is an estimation failure.
THE AGILE MENTALITY CHAPTER Topics  Why Use Agile and Scrum?  Agile Development –Manifesto for Agile Software Development  Scrum Methodology.
Dr. Nguyen Hai Quan.  Why SCRUM?  What is SCRUM?  Some terms  SCRUM Meetings  Sprint  Estimation  Product backlog  Sprint backlog  Whiteboard.
Basic Approach Development driven by time boxing May sacrifice requirements in order to keep schedule (time boxed) Steer project as you go based on user.
Chapter 7 The Practices: dX. 2 Outline Iterative Development Iterative Development Planning Planning Organizing the Iterations into Management Phases.
AP-1 4. Agile Processes. AP-2 Agile Processes Focus on creating a working system Different attitude on measuring progress XP Scrum.
What Is Agile? Agile is a group of software development methodologies Scrum Extreme Programming (XP) Lean Etc. Key Characteristics: Small increments Adaptive.
Requirements Engineering Requirements Engineering in Agile Methods Lecture-28.
Extreme programming (XP) Variant of agile Takes commonsense practices to extreme levels © 2012 by Václav Rajlich1.
SCRUM.
Planning Extreme programming
WHEN TITLE IS NOT A QUESTION N O ‘WE CAN’ CA Agile Vision Product Manager Michael Lester.
Agile 101. Feasibility Study SDLC – What is it? Systems Development Life Cycle: The most commonly used, and generally accepted, project management approach..
1 Introduction to eXtreme Programming Remko Popma Azzurri Ltd.
Introduction to Agile. Introduction Who is this guy?
#msdevcon Community Track IMPLEMENTATION OF SCRUM Bernardin Katić Insa Investment Software AG.
Managing Agile Software Development Teams Using Scrum AKA: Wrangling Developers for Fun and Profit!
Agile Methodology. -Dhanashree Kumkar -Plus91 Technologies.
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
The Scrum Framework Presented by Somnath Ghosh Scrum Practitioner 24 hours weeks.
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Appendix B Agile Methodologies
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Agile Scrum Management
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Mike Cohn - Agile Estimating and Planning
By: By: Agile Scrum Master Online Training.
Scrum MODULE 3 – Part 3.
Scrum - Plan a Sprint Great Video (but added release /sprint layer)
Appendix B Agile Methodologies
Software Development In Agile
Presentation transcript:

Copyright David Churchville - XP and Agile Planning David Churchville ExtremePlanner Software XP Fishbowl San Diego Code Camp San Diego Code Camp

Copyright David Churchville - Topics Why Plan? Release planning Iteration planning Daily planning Example Questions?

Copyright David Churchville - Why do we plan? To answer questions about a project –What will this system need to do? –What are the expected benefits? –When will it be available? –What will it take to build it? But mainly: Is it worth doing?

Copyright David Churchville - Why does planning fail? Pitfalls of Traditional Plans –Activity-based instead of feature-based “resource” allocation and 100% utilization –Work is not prioritized by value –Uncertainty in estimates is ignored –Estimates are treated as commitments

Copyright David Churchville - Why Agile Planning? The further we are from delivery, the less accurate the plan To reduce risk, we need to learn more by delivering working software quickly Feedback (product and technical) is used to improve the accuracy of the plan

Copyright David Churchville - Agile Planning Levels Daily Planning (stand-up meetings)

Copyright David Churchville - Agile Planning Levels Release Planning –Primary goals: overall vision, external communication –Feature level planning –Big picture thinking –Driven by the customer/product owner

Copyright David Churchville - Agile Planning Levels Iteration Planning –Primary goals: internal communication –Task level planning –Development team drives this from priority and risk viewpoint

Copyright David Churchville - Agile Planning Levels Daily Planning (standup meeting) –Primary goals: internal communication –Individual planning and coordination –Avoids duplicated effort –Difficult to “go dark”

Copyright David Churchville - Release Planning Steps Brainstorm a set of user stories Estimate relative size of stories Choose release criteria (date or feature set) Prioritize stories for release Choose a set of features

Copyright David Churchville - Release Planning Steps Brainstorm a set of user stories –Roles and goals –As a __ I can __ so that __ –Involve the entire product team –Review as a team to normalize –OK if we don’t capture everything

Copyright David Churchville - Release Planning Steps Estimate size of stories –Use points or ideal time –Suggest S,M,L or 1,2,4,8,16 –Educated guess or “planning poker” –Goal is to help customer prioritize

Copyright David Churchville - Release Planning Steps Choose Release Criteria –Fixed Deadline (we need it by Q2!) –Fixed Scope (when can we have it??) Issues –Can’t pick both scope and deadline! –Either scope or duration is fuzzy

Copyright David Churchville - Release Planning Steps Prioritize Stories for Release –Force rank stories ( …N) or… –“Buy” stories Let each person pick top N Or give each person limited points to spend Allow small budget for infrastructure

Copyright David Churchville - Release Planning Steps Choose stories for release –For date-driven releases, calculate capacity FTEs * Workdays * EffectiveHrsPerDay 4 FTE * 30 days * 5 hours per day = 120 ideal hours –Select stories based on what fits (convert size to duration) –Note which stories are “must have”, “should have”, and “nice to have” in case of scope cuts

Copyright David Churchville - Iteration Planning Steps Re-prioritize work (after first) Select stories for the iteration –Determine iteration capacity –Priority-based or risk-based?

Copyright David Churchville - Iteration Planning Steps Break stories into tasks –Estimate task durations (not size) –Split or merge stories as needed –Reality check for commitments No need to assign tasks.

Copyright David Churchville - Daily Planning Steps Standup meeting –What did I accomplish yesterday? –What do I plan to accomplish today? –What are the obstacles blocking me? Keep it short!

Copyright David Churchville - Daily Planning Steps Add any new tasks Sign up for tasks Update estimates and status Update “information radiators”

Copyright David Churchville - Resources - Books Agile Estimating and Planning (Cohn) Planning Extreme Programming (Beck, Fowler) Agile Project Management with Scrum (Schwaber)

Copyright David Churchville - Resources - Tools For small, co-located teams –Index cards, whiteboards –Excel spreadsheets For distributed teams/larger teams –ExtremePlanner (extremeplanner.com) –Version One (versionone.com) –XPlanner (xplanner.org)

Copyright David Churchville - Example Sudoku Discuss and prioritize stories for the day

Copyright David Churchville - Thank You For a copy of this presentation –