Agile ProjectManagement Ch By Jim Highsmith Presenter: Rachel Fult 7Speculate Phase Produces a release plan that directs feature goals, prioritizes the work load, and also includes enough flexibility to allow for future changes.
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.
Agile Development Life CycleEnvision Speculat Explore Adapt 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 a Release Plan
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
What’s 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*
What’s a feature-story card?Useful product based features written in user-centered language that ties developer goals tocustomer needs.
What’s in a feature-story card? The technical activities and relative time required to: Document BuildDesign Test Develop Deploy Deliver
A feature-story card exampleFeature 1: A investment banker (user) should beable to analyze stock XYZ. Story A: User sees a comprised investment firm list of opinions on XYZ. Story B: User can click a graph to see the performance history of XYZ. Story C: User can choose a category of breaking news link related to XYZ.*Feature 1 will take relatively twice as long asFeature 2.*Story A, B, & C are high value with low risks.
A poem on storiesSome are big to tackle Others are small Some are high risk Others not at all Some should come 1st Others we may not even bother The one redeeming virtue is they all offer $VALUE$
What’s 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.
How are priorities arranged?Foundational (must have) features High Value Low Risk Moderate Value Low Risk High Value High Risk Low Value Low Risk Low Value High
Where are all these priorities?They get put into Product backlog
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
What now?Use the release plan material (stories, prioritizedfeatures, backlog, etc.) to evaluate scope,iterations, and cost estimates. Then move ontothe next agile phase Evaluate