You're about to create your best presentation ever

User Story Presentation Template

Create your presentation by reusing one of our great community templates.

User story

Transcript: Measure. Analyze. Share. Learn. 6 months 18 months Measure. ...years? Analyze. Predict... Measure. A User Story

User Story

Transcript: www.your-website.com A Good User Story Insert some text here March 2017 Story should be from user point of view Definition of User Story A user story is a tool used in Agile software development to capture a description of a software feature from an end-user perspective. A Little Video Insert your own text here. Talk about something related to your first topic or just put some placeholder text here. A Little Video... INVEST Invest is the way to go! 3 C's of User Story INVEST For a good user story: What comprises of a good user story Some examples of Good user story Some examples of Good user story GROWTH-597 As a User, I want to be taken to a landing page upon clicking on the unsubscribe link at the bottom on the email alert email so that I can see the confirmation that I have been unsubscribed. TPS-653 As a Marketing manager, I would like to provide correct information regards to the Auction Type to the buyers looking at a TPS Online asset on the native app so that I am not at any legal risk and not misrepresenting an online foreclosure sale. TPS-639 Automation Scripts from sprint 16 TPS-614 We need to create the flag to support old and new version of emails. TPS-512 REO PDP | Instrumentation | Page Load and initial items TPS-393 ADC RTK 2.0 Upgrade - TPS PDP REO-4 API | Short Sales | Update Search API (we do not have "Short Sale" filter on UI yet) Bad Stories Bad Stories Suggestions: Suggestions: Story should only be created by Product (Not by Dev, QA) Story should be a user story (Follow INVEST) API support / FE support/ Instrumentation should not be a story by themselves. They should be a sub task to a story Automation ticket should be a Task linked to the story (not a sub task. It should not block a story from being closed) How to manage features where backend work can start one sprint before the FE work? Open Questions Open Questions

User Story

Transcript: User Story ETEC Conego José Bento About the client Client The ETEC Conego José Bento school has difficulty in contacting the secretariat with students. With Connection failures, delayed delivery of documents and lack of equipment repair. Data survey This project is based on a survey carried out after the visit with professionals trained to carry out the improvement; these being part of the physical structure, cabling of the institution and electronic equipment, such as: Computers, routers, cameras and computer peripherals. Data Survey School Currently, the school is a debt between the secretariat, teachers, students and the education secretariat. Both departments are well located and aware of their functions for the better functioning of the institution. School Solution Solution The proposed project also preserves the use of structured cabling based on ANSI/TIA-568 and ANSI/TIA-569 standards. Being aware that such standards are necessary to increase the useful life of cables, better traffic and operation of the network, and so on. After the visit at the site, the lack of standardization of the cables throughout the institution was noticed, with cables hanging, tied, glued and released in a totally incorrect way.

User Story

Transcript: Ｕser Story Introduction A concise, written description of a piece of functionality that will be valuable to a user (or owner) of the software. Add as many notes as you need 3 parts Card Conversation Confirmation 3C User Story Template As a [ user role ] , I want to [ feature ] so that [ some business value ] Ｔemplate As a [ user role ] , I want to [ feature ] so that [ some business value ] User Story Template User Ｓtory Ｍapping Ｕser Story Ｍapping Step1. Step 1. User Tasks Step2. Step 2. Group Step3. Step 3. Name & Arrange Step4. Step 4. More Story Task 9 More text here Task 9

User Story Workshop

Transcript: Workshop User Story What/Why A user story should be small enough to fit into a sprint, descriptive enough to let the team know what is needed, but general enough to let the team find the best solution What Primary means of expressing needed functionality. They largely replace the traditional requirements specs. 'As a (user role), I want (activity) to, so that (business value) What Why User stories are broken down slices of larger projects. We want user stories to fit within a sprint and be the smallest piece of a project that can (hopefully) offer some value. Why Breakdown Epic Feature Feature User Story User Story User Story User Story User Story Epic = Project Timing of an epic can be anywhere from 3 months to 3 years Epic Elements of a good user story Elements Your title should be able to be read and understood by the stakeholder Meaningful titles Title It's important to state what you are looking for, but not direct the team how. Ex: I would like to be able to see all of my account information when I click on the 'me' button. A clear summary Summary Acceptance criteria provide the the information needed to ensure that the story is implemented correctly and covers the relevant functional and NFRs. Given, When, Then Acceptance Criteria Acceptance criteria It is more important to have a shared understanding "Individuals and Interactions over process and tools" Make it a conversation Conversation Feature breakdown Exercise In your smaller groups, break down a feature into user stories Ex:?? Story Mapping Story Splitting

User Story Mapping

Transcript: Reference Create your own user story map Create your own user story map Details and Release Form Groups Allows you to see "big picture" in backlog Tool for making decisions about grooming and prioritizing your backlog Visual alternative to traditional project plans Useful for discussion and managing scope Promotes silent brainstorming and a collaborative approach to generating user stories Form a group of 3-5 people Any less and you might miss ideas Any more then it slows the process User Story Mapping Create your own user story map Arrange the groups left to right in the order a user would typically complete the tasks You now having a skeleton of of your user story map Walk the skeleton to confirm you have not missed any major user tasks or activities You can now add more detailed user stories below each user task Break user story map into releases Create your own user story map In silence the team groups the post-its that are similar to each other Things that are dissimilar to each other should be moved farther apart Using another colour post-it, name each group and put the post-it on top of the group, these are called the user activities User Activities Google "user story mapping" or visit the website http://winnipegagilist.blogspot.ca www.cardboardit.com User Tasks Start by gathering the major user tasks of the project/application in silence - the "things people do" (ex. Compose E-mail, Create Contact, etc) Each person takes the same coloured post-it and silently writes down one user task per post-it Each person reads their post-it aloud and places them on the table in front of the group If there are duplicates, they should be removed at this point Benefits

User Story

Transcript: 1.0 Warranty Priority Field We create a Story You can see it in the Component field and Labels Target Project Should reflect the product we are affecting with the implementation Status CHAPI Research & Clarification? Errors and Issues? Ongoing backlog work? Requested by field tells us what is the source of the user story in regards of the original scope agreed. FlightOps Sizing Where are we? You can find it the Project Field Spikes and Defects are not estimated 3.0 ... How Advance is watched? SWABIZ Product Field Roadmap 17.10 Team Check Out JIRA, for additional details and user story explanation content Vision We create a Defect Story Points field is used to specify the size of an user story, the measure is not related to time, but effort, complexity and risk SelectFlights Reporter is the person creating the user story In a SWA Trip UI Mostly for bugs User stories shall have a size that makes them fit into one Sprint, otherwise a special treatment is needed. https://jira-tools.swacorp.com/browse/ECOM-6411 Reporter and Assignation Release The one artifact to be part of SWA 1.2 - 2.0 Reason field denotes the trigger to creating the new user story. Is used in combination with the Requested By field. User Story What are we going to do? Assignee is the person currently assigned to the user story We create a Spike And in the Identifier Type Field We'll have to look for better ways to handle backlog priority Fix Versions

User story Estimation

Transcript: low-tech and high-touch. dynamically reorganize cards schema-free markup reminders for much bigger ideas cards are extremely portable The requirement itself is communicated from customer to programmers through conversation: an exchange of thoughts, opinions, and feelings.The story text we write on cards is less important than the conversations we have. No matter how much discussion or how much documentation we produce, we can’t be as certain as we need to be about what is to be done. The third C in the user story’s key aspects adds confirmation that we sorely need. This component is the acceptance test. Is a collection of defining attributes that characterize a population of users and their intended interactions with the system We need Roles: For Usage Center Design To avoid missing Stories To Avoid Unused Stories For better business understanding Acceptance Criteria: Admin interface with ACL management demo the validation of the resource and resource operation Split Story Patterns As a role I want to goal so that motivation As a role I need feature so that business value As a user I need/want feature so that benefit In order to receive benefit as a role, I want goal/desire Story Decomposition Example: Estimation? Product vs Sprint Backlog User Story Format? 1.Workflow Steps 2. Business Rule Variations 3. Major Effort 4. Simple/Complex 5. Variations in Data 6. Data Entry Methods 7. Defer Performance 8. Operations (e.g. CRUD) 9. Break Out a Spike Share Your Pain? Independent Negotiable Valuable Estimable Sized appropriately or Small Testable What's wrong? Grooming vs Planning 'User story is User Story!' I N V E S T User Story As a PO, I want to have a unify ACL for different API (SOAP, REST) When to Split?

Explore our templates for more presentation inspiration

World Map - Antique

Description: Impactful presentations need stunning visuals and a meaningful metaphor to show high-level concepts and the smaller details. This customizable presentation template uses a classic world map visual to help you navigate complex information while staying grounded in your presentation’s core message.

Easy Globe Templates for Stunning Presentations | Prezi

Description: For grant requests, program proposals, or any other nonprofit or education presentation, this globe-themed creative Prezi template is the way to generate interest and momentum. Like all Prezi education templates and Prezi nonprofit templates, it’s easy to customize.

Resume

Description: How do you stand out from the stacks of resumes on your prospective employer’s desk? With a Prezi resume template, of course! Create your own “Prezume” and and impress them with your cutting-edge dynamism and cool. All Prezi presentation templates are easy to customize.

Top Lesson Plan Template for Teachers | Prezi

Description: This customizable, colorful Prezi presentation template makes creating and sharing lesson plans simple, clear, and engaging. The friendly, board game-inspired theme provides a clear path for organizing subjects, assignments, exams, and more.

Now you can make any subject more engaging and memorable

Get started with Prezi