1. © 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 Backlog Retrospectives

2. 2 © 2010 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property. User Stories  User stories are Agile product requirements  Describes features to be implemented  Covers additional detail than a typical requirement in IT UP  Who is the beneficiary of the user story?  What needs to be implemented?  What will it take for this user story to pass testing?  How does this user story fit into the bigger picture? What is a User Story? Example  Example requirement in IT UP  The walls of the bedroom will be painted red.  Translated into an Agile user story  As the owner of the house, I want to have the walls of my bedroom painted red so that they match my bed spread and paintings I intend to hang on the wall.  To be accepted all walls must be painted red from floor to ceiling such that no white shines through.

3. 3 © 2010 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property. User Stories  Product Owners or Product Owner Delegates:  Creation  Prioritization  Answer any questions and guide the vision for the Delivery Team  Delivery Teams:  Estimate  Commit to delivery within an iteration  Break into tasks  Work is pulled by the team, not assigned  Track progress Roles and Responsibilities

4. 4 © 2010 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property. User Stories  As a, I want to, so that  The additional information provides the delivery team additional context it changes are needed on the fly Acceptance Criteria  Functionality required to confirm successful completion of a user story  Provides a clear target for development and test  Gives insight into how the customer will use the functionality  Drives test driven development  Defines done/done  Explains what will be demoed during a sprint review Format of a User Story

5. 5 © 2010 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property. User Stories  Independent – a user story in an iteration should not have to wait for another user story to be completed before it can be worked  Negotiable – small stories are straight forward and well defined, large stories have more flexibility to change  Valuable – each story adds some piece of functionality  Estimable – stories contain enough information to gauge effort  Small – stories should be accepted iteratively, they should be broken down as small as possible to drive iterative delivery  Testable – acceptance criteria must be clearly defined Making a Great User Story

6. 6 © 2010 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property. User Stories  Define the relative effort of a user story compared to other user stories of the same product in the same Scrum team  Do not individually correlate to a number of hours to complete the work  Are evaluated as a Scrum team  Allow for imprecision in estimates  Are added together to create story point estimates for epics Task Estimates  Individuals break out user stories into tasks and take ownership  Task estimates represent an individuals amount of effort to get the piece of work done in hours  User stories can and will have multiple tasks delivered by different members of the Scrum team Story Points

7. 7 © 2010 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property. User Stories  US13253 - Modify the current SPAM button & Response Message – iPhone  As a user of mark the spot application I want to view spam button label as Report Spam Text Message & when I submit spam text message I want to see the response message to display the following verbiage Please forward SPAM Text Message to 7726 (SPAM) with OK button  Acceptance Criteria  Modify the current SPAM button. Remove the word ‘SMS’ and change it to ‘Report Spam Text'  Message Modify the response message from ‘Please forward the SPAM SMS to SPAM (7726)’ to ‘Please forward SPAM Text Message to 7726 (SPAM)’.  Parent User Story  US4968: Project: AT&T Mark the Spot - iPhone/iPad (Consumer) - Version 3.0  Planned Estimate  1 story point  Owner  Pulp Fiction scrum team  Tasks  Modify label of button – 1 hour – Marshall Margenau  Test to ensure label has correct verbiage – 1 hour – Mallika Kopparapu Example

8. 8 © 2010 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property. Backlog  A list of all user stories not completed and not in the current iteration  It should consist of at least 2 future iterations worth of work that has been estimated  Can be used if the Delivery Team is ahead of schedule to pull in additional work to the iteration to increase velocity  Prioritized by business value  Serves as an up to date product implementation timeline  Can be reprioritized every iteration by the Product Owner What is a Backlog?

9. 9 © 2010 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property. Backlog  Prioritization of user stories requiring implementation  Estimate the user stories as they are prioritized to the top if they are not already estimated  Ensure well formed user stories  Break up epics into smaller, deliverable user stories  Occur at least once per iteration  Delivery Team discusses user stories to ensure understanding  Everyone who could benefit from discussion should attend  Product Owner, Scrum team, outside SMEs, Project Manager  Expect changes to the backlog each iteration Grooming Sessions Use these as an opportunity to provide feedback to the client/customer, make suggestions on how to improve the product, and build customer satisfaction

10. 10 © 2010 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property. Backlog The Product Iceberg Priority Sprint Release Future Releases The higher on the pyramid, the higher the priority, the sooner the user story is worked

11. 11 © 2010 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property. Retrospectives  The team’s way of analyzing what is working and what is not, and quickly make process improvements to drive overall efficiencies to delivery  Retrospectives are the primary means the Scrum team has to make themselves better What is a Retrospective? Example  Painting the bedrooms red  Painting side to side is taking too long, let’s try up and down  These paint brushes are too thin, let’s get bigger ones  We ran out of red paint this iteration and it cost us a day, let’s ensure we have enough next time

12. 12 © 2010 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property. Retrospectives  Scrum Masters facilitate the discussion  The Delivery Team discusses:  What is working and we should continue?  What is not working and should be discontinued?  What are some new ideas to drive efficiencies that we should start doing?  Only the committed team members should join  All participants must be open to discuss Roles and Responsibilities  Identify What and Why, not Who  Encourage and foster open discussions  Promote active participation  Track process improvements in a retrospective log  Steal ideas from other Scrum teams Making Retrospectives Work