This document provides an agenda for a seminar on effective user stories for agile requirements projects. The seminar will teach attendees how to identify and write good user stories, explore using user role modeling, and provide hands-on practice identifying user roles and writing stories. Attendees will learn the six attributes of a good story, techniques for gathering user stories, how much work to do upfront versus just-in-time, and additional guidelines like making stories independent, negotiable, valuable, estimatable, sized appropriately, and testable.
This document provides an agenda for a seminar on effective user stories for agile requirements projects. The seminar will teach attendees how to identify and write good user stories, explore using user role modeling, and provide hands-on practice identifying user roles and writing stories. Attendees will learn the six attributes of a good story, techniques for gathering user stories, how much work to do upfront versus just-in-time, and additional guidelines like making stories independent, negotiable, valuable, estimatable, sized appropriately, and testable.
This document provides an agenda for a seminar on effective user stories for agile requirements projects. The seminar will teach attendees how to identify and write good user stories, explore using user role modeling, and provide hands-on practice identifying user roles and writing stories. Attendees will learn the six attributes of a good story, techniques for gathering user stories, how much work to do upfront versus just-in-time, and additional guidelines like making stories independent, negotiable, valuable, estimatable, sized appropriately, and testable.
This document provides an agenda for a seminar on effective user stories for agile requirements projects. The seminar will teach attendees how to identify and write good user stories, explore using user role modeling, and provide hands-on practice identifying user roles and writing stories. Attendees will learn the six attributes of a good story, techniques for gathering user stories, how much work to do upfront versus just-in-time, and additional guidelines like making stories independent, negotiable, valuable, estimatable, sized appropriately, and testable.
Copyright:
Attribution Non-Commercial (BY-NC)
Available Formats
Download as PDF, TXT or read online from Scribd
Download as pdf or txt
You are on page 1of 1
Effective User Stories for Agenda
It’s a communication problem
Agile Requirements What user stories are
Card, conversation, confirmation Some examples Projects start with their requirements. How those requirements are documented or expressed has a Adding detail tremendous influence on the rest of the project. Capturing those requirements and making them clear to The product backlog iceberg all concerned is much easier with a technique called User Stories. Though the technique emerged from Augmenting user stories the agile processes, writing user stories is effective for all time-constrained projects, whether Agile or not. Users and user roles Proxy bias In this seminar, you will learn how to identify and write good user stories. You’ll discover the six attributes User roles all good stories must exhibit and be introduced to five additional guidelines for writing better stories. User role modeling Together, we will explore how to employ user role modeling when gathering a project’s initial stories. Personas During this hands-on seminar we will use multiple case studies to practice identifying user roles and Extreme characters writing stories. Gathering stories Questionnaires You Will Learn Observation User interviews • The six attributes of a good story and how to achieve them Story-writing workshops • A useful template for writing user stories INVEST in good stories • Practical techniques for gathering user stories • How much work to do up-front and how much to do just-in-time Independent Negotiable Valuable
About the Instructor Estimatable
Sized Appropriately Martin Kearns is one of the first three coaches to be certified in the world. Martin works Testable with Renewtek, an Australian information technology company which uses leading edge Additional guidelines tools and technologies. He consistently uses the Scrum Framework in conjunction with A tools interlude Agile methodologies where appropriate. Martin joined Renewtek in 2005 where he is responsible for designing training courses Created case studies around Scrum/Agile as well as leading the promotion of Agile principles within Renewtek Creating and selecting case studies and to their diverse client base. He offers consulting services to organisations on the Writing the product backlogs creation and implementation of Agile delivery. Lessons learned Martin conducts formal Scrum training to introduce concepts and core principles in a What user stories are not unique and creative way. He can also play a continuing mentoring role to assist with Use cases MOUNTAIN GOAT follow-up implementation and Agile Retrospectives at key project milestones. IEEE 830 Software Requirements Specs S O F T W A R E Why user stories Why not user stories