Agile Planning & Design

Category: Education

Presentation Description

This tutorial is about the important part of the project while agile planning & design like detailed planning, user stories, release planning, iteration planning (sprint planning) etc.


Presentation Transcript

slide 1: Module 5: Agile Planning Module 6: Agile Design developer

slide 2: Planning • Important part of the project • Planning comprises • Just In Time Planning • Detailed Planning • User Stories • Release Planning • Iteration Planning Sprint Planning developer

slide 3: User Stories • Short description of a feature • Represents single unit of business value to the customer • It is told from user ’ s prospective • Format As a type of user I want some action so that business benefit Or In order for some reason as a user role I want some action • Typically recorded on indexed card during meeting with customer • Should always be in a language that customer understands. developer

slide 4: User Stories • Must be INVEST Independent Negotiable Valuable Estimable Sized Appropriately Testable • User story shifts focus from writing about features to discussing them. • Details can be added to user stories in 2 general ways i. By Splitting a user story into multiple smaller user stories ii. By Adding Conditions of satisfaction. developer

slide 5: User Stories • Who should write user story • Including product owner every one in the team because involvement of every one makes a big difference to refine each user story and its acceptance criteria • When are user stories written • Generally through out the agile project • Specifically story-writing workshop should be held near the start of the project / sprint developer

slide 6: User Stories Acceptance Criteria • Acceptance criteria should be captured during story generation • It can be captured on the reverse side of the user story card • It helps to find more details and identifying dependencies • Typically each story should have minimum 3 acceptance criteria. developer

slide 7: Types Of User Story • There are mainly 4 types of user stories • Baseline User Story • Normal User Story • Spike User Story • Epic User Story developer

slide 8: Baseline User Story • The team should start with a small and easy to size story to begin estimation which becomes a baseline user story. • Each user s t or y ’ s efforts estimate should be relative to this story • Baseline s t or y ’ s estimate must be accurate • If baseline story estimate is inaccurate then the whole estimation can be inaccurate. developer

slide 9: Spike User Story • Story is too difficult to estimate due to lack of technical knowledge – Create spike alternate story • Spike is created for the unfamiliar technology • Once spike is completed then development team can estimate the actual user story • Spike involves gaining enough technical knowledge to estimate user story e.g. Learning accelerometer gyroscope readings to develop motion sensing game developer

slide 10: Epic User Story – Story Division • Story that needs total more than one week of work is epic story • It is usually too big to estimate • Divide a story in smaller VERTICAL slices • The story should work through all layers of architecture because that provides immediate customer value. developer

slide 11: Estimating Stories – Planning Poker • Planning poker is a group estimation technique • Incorporates all team members – software developers analysts QA-tester security and infrastructure experts • Each team member brings different technical prospective • Customer is also involved only to give answer raised by the team while estimating. developer

slide 12: Planning Poker – How To Play • Product owner reads the story • The team discusses the feature with the customer to get more details • The team is free to ask the questions • Scrum maser asks the team to privately give a number to represent the complexity of the story. developer

slide 13: Planning Poker – How To Play • To prevent influence team members should not share their numbers with others • Once all has given number then Scrum Master asks everyone to reveal their number • If all team member decides the same number then it is assigned to that user story • If numbers does not match then the team member with lowest and highest number are asked to explain why they think so. developer

slide 14: Planning Poker – How To Play • After the discussion another round of poker is played • The process is repeated until the team has unanimously settled on a number • In general no more than 3 rounds will be taken • If the team is not on conclusion even after 3 rounds then the Scrum Master should take the middle number and move on to the next user story. developer

slide 15: Planning Poker – Advantage • Gives more accurate estimate because we are better in comparison • Gives different technical prospective from different team members so all possible loop holes can be identified • Helps the team to be on the same page. developer

slide 16: Release Planning • Release is made of enough stories to offer business value • Typically it is made of 4 iterations developer

slide 17: Iteration Planning • Iteration planning mainly involves 3 steps 1. Defining Acceptance Criteria 2. Splitting User Stories in to Tasks 3. Developer “ I n the Z o n e ”. developer

authorStream Live Help