Atomic Project Management Carl Erickson Atomic Object LLC July 2007 Atomic Object 1
Extreme Programming Cycle Two aspects you re never done it takes two to plan Time cycles/phases/scale Releases Iterations Standups Pairing July 2007 Atomic Object 2
July 2007 Atomic Object 3
Releases Pairing Standup Iteration Release hours days weeks months Driven by the business Time scale months Unit of work release features Means of organization release plan July 2007 Atomic Object 4
Release Planning Pairing Standup Iteration Release hours days weeks months Trade shows Strategic plan Competition Sales goals Business environment Economy July 2007 Atomic Object 5
July 2007 Atomic Object 6
Iterations Pairing Standup Iteration Release hours days weeks months Highest priority stories Goal: tested, working system whole, but not feature complete risk reduction Unit of work stories short enough to estimate Time scale weeks July 2007 Atomic Object 7
Start of iteration Pairing Standup Iteration Release hours days weeks months Story prioritization by the customer Estimation by the developers averaged across everybody done in story points July 2007 Atomic Object 8
End of iteration Pairing Standup Iteration Release hours days weeks months Acceptance tests by the customer Demo time! for customers for developers New stories July 2007 Atomic Object 9
July 2007 Atomic Object 10
Standups Pairing Standup Iteration Release hours days weeks months Sharing progress plan for the day roadblocks Time scale days Borg brain synch July 2007 Atomic Object 11
A day in the office July 2007 Atomic Object 12
Pairing Pairing Standup Iteration Release hours days weeks months In the trenches Time scale hours Unit of work the task Means of organization the task board, cards, facilities July 2007 Atomic Object 13
July 2007 Atomic Object 14
Information Radiators The usefulness of metrics shared knowledge emotional detachment XP approach sense a problem devise a metric display the results Watch for means/end inversion July 2007 Atomic Object 15
July 2007 Atomic Object 16
July 2007 Atomic Object 17
Project Tracking and Reporting Simple, small, on/off weak iteration ritual (phases only) cork board, cards, PunchIt, on-demand status reports BaseCamp for coordination Complex, large, long-running BaseCamp for coordination ExplainPMT, strac, spreadsheets for stories, velocity July 2007 Atomic Object 18
July 2007 Atomic Object 19
July 2007 Atomic Object 20
Large Projects At least 2 developers, at least 2 months One week iterations Often have an approved total budget developer land (points, hours) money land ($) July 2007 Atomic Object 21
Tracking Stories Tools can help track stories, the backlog, iterations, and velocity stories: unit of work, sized by points backlog: identified, but incomplete, stories iterations: set of stories done in a week velocity: points/iteration July 2007 Atomic Object 22
Bepco Dyno Host Dashboard Iterations Backlog Story Tree Milestones Team Features Charts Projects Users New Iteration Current Iteration Previous Iteration Completed Iterations: 9/23/2005 9/16/2005 9/9/2005 9/2/2005 8/26/2005 8/19/2005 8/12/2005 8/5/2005 7/29/2005 7/22/2005 7/18/2005 7/11/2005 7/5/2005 9/30/2005-10/6/2005 Summary Report Budget: Planned: Available: Story Cards 80 points 71 points 9 points Assign Story Cards Completed: Worked: Remaining: Time Remaining: 11 points 6 points 60 points 2 days Scid Title Points Worked Category Status Owner Prioritize SC129 SC123 SC118 SC124 SC136 SC137 Update Drive Curve Editor System Normal Stop Disconnect and Reconnect Controller Update Drive Curve Import Message Box Update Update to the Line Chart 8 5 Story Complete None (take) 16 0 Story Defined 4 0 Story Defined 8 0 Story Defined None (take) None (take) None (take) 2 1 Story Complete None (take) 4 0 Story Defined None (take) ( Edit ) ( Delete ) Edit Delete Edit Delete Edit Delete Edit Delete Edit Delete Edit Delete July 2007 Atomic Object 23 SC138 Decoding Display Widget 1 0 Story Complete None (take) Move Selected Story Cards to: Backlog Go Print All Tags Print Selected Stories Edit Delete
Burndown Chart A single, easily maintained indicator of project status Reveal the following scope change expected completion time July 2007 Atomic Object 24
Burn Down Chart 70 60 50 points 40 30 20 Total Work Completed Remaining Work Linear (Completed) Linear (Remaining Work) 10 0 0 5 10 15 20 25-10 iterations July 2007 Atomic Object 25
Burn Down Chart Generated on: December 22, 2005 explainpmt» Bepco Dyno Host» 10/04/2005 09:59 AM Logged in as Dave Crosby (Log-out) (Edit Profile) Bepco Dyno Host Dashboard Iterations Backlog Story Tree Milestones Team Features Charts Users Tags Projects Story Point Project Work Completed Story Points Remaining Work Project Velocity Project Completion Date Completion Date Uncertainty A small, well-defined task. Projects are generally composed of many stories. A unit of measure used by a developer to estimate the effort necessary to complete a story. The sum, in points, of all stories in the project. The sum of the points of all stories completed during the iteration. The total project work minus sum of points for all completed stories. The exponential weighted average of completed story points per iteration. A measure of the rate at which work on the project is being completed. The estimated completion iteration for the project. Calculated by dividing the remaining work by the project velocity. The expected range within which the project will be completed. The variance diminishes linearly as the project moves toward completion. explain Project Management Tool - 1.8.2 This software is licensed under the terms of the GPL. July 2007 Atomic Object 26