Agile Project Management - Ch7

• 1. Agile ProjectManagementCh By Jim HighsmithPresenter: Rachel Fult7Speculate Phase Produces a release plan that directs feature goals, prioritizes the work load, and also includes enough flexibility to allow for future changes.

2. Operational DefinitionsCapabilities: High level valuable product function that iscomplete.Features: Lower level valuable functionalities made up ofdifferent small story pieces.Stories: Small separate functionalities that add up to makea feature.Iteration: Iterations are short accelerated developmentphases that increase quality assurance checking andcustomer need alignment through rapid development anddeployment.Feature based development: A visible collaborativefeature-based process plan between the product team,development engineers, and customer which describesfeatures in user-focused terms. 3. Agile Development LifeCycleEnvision Speculat ExploreAdapt ClosePhase e Phase Phase Phase PhaseThe speculate phase elaborates upon the information gathered andoutlined in the envision phase. Using that material in the speculatephase, the agile team produces aRelease Plan 4. Why create a release plan? Prioritizing features Coordinating activities Establishing cost & schedule information Keeps focus on customer needs, business objectives, & project goals Collaboration between product team, development engineers, & customer 5. Whats in a release plan?A list of iterations focused on deploying value based functionsto the customer. These iterations are:1. Maintained on feature-story cards2. Prioritized based by on feature risk and value3. Iterations and features are compiled into a product backlog *All features, stories, and product backlog information are written in customer oriented terms* 6. Whats the time-frame? 7. Whats a feature-story card?Useful product based features written in user-centered language that ties developer goals tocustomer needs. 8. Whats in a feature-storycard? The technical activities and relative time required to:DocumentBuildDesignTestDevelopDeployDeliver 9. A feature-story card exampleFeature 1: A investment banker (user) should beable to analyze stock XYZ.Story A: User sees a comprised investment firmlist of opinions on XYZ.Story B: User can click a graph to see theperformance history of XYZ.Story C: User can choose a category of breakingnews link related to XYZ.*Feature 1 will take relatively twice as long asFeature 2.*Story A, B, & C are high value with low risks. 10. A poem on storiesSome are big to tackleOthers are smallSome are high risk Others not at all Some should come 1st Others we may not even botherThe one redeeming virtue is they all offer$VALUE$ 11. How do you schedule stories?ValuRiske 12. Whats the priority?Customers decide what are the high valuefeatures and stories!Development teams decide upon thetechnological risk & related time frames forfeature-stories.Project and product managers take input fromboth sides to determine the ROI. 13. How are prioritiesarranged?Foundational (must have) featuresHigh Value LowRiskModerate Value LowRisk High Value High RiskLow Value LowRiskLow Value High 14. Where are all these priorities?They get put intoProduct backlog 15. What does the Product Backlog tell us?The backlog list contains capabilities, features, &stories that helps outline information to considerwhen: Planning iterations Assigning feature tasks to team members 16. What now?Use the release plan material (stories, prioritizedfeatures, backlog, etc.) to evaluate scope,iterations, and cost estimates. Then move ontothe next agile phaseEvaluate