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: 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 Presentation

Transcript: User Persona Presented by JT Travis Toilet Paper Dispensor Personal Info A1 Age: 25-80 years old Gender: All genders Marital Status: N/A Location: Anywhere! Income: Middle/Upper Class Education: N/A Professional Info Professional Info Job Title: N/A Company/Industry: Hotels, Hospitals, Schools, Arenas, high traffic bathroom facilities. Company Size: Large What tools: Ability to use basic tools Are they successful: Not important to own this product Do they manage others: Not important to own this product, although this is important for some of the target audience. Values and Fears Values and Fears What do they value: Sustainability and affordability What is important to our customer: Having the opportunity to save on money while also saving the environment we live in. This product is also an innovative solution to human waste. What objections might they have: Our customers may be concerned with the failure of the technology in something that is manual and normally has no errors. What drives there decision making process: Our customers tend to buy our product knowing the goal of sustainability is the goal of this product. Goals and Challenges Goals and Challenges What are there personal/career goals: Three major areas of goals are customers are looking to satisfy is efficiency, hygiene, and customer satisfaction. How do they prioritize these goals: The priority of these goals may vary depending on the specific needs and preferences of the customer. For example, maintaining hygiene and customer satisfaction may be higher priorities for a customer in a restaurant or hotel setting, while efficiency and cost-effectiveness may be higher priorities for a customer in a commercial or industrial setting What challenges impact these goals: Stock management, maintenance/repairs, and budget constraints How could you help: We can offer many different promotions and deals to help make a more efficient purchase. What questions typically come up: How often should I check and refill the toilet paper dispenser? How can I troubleshoot a paper jam or dispenser malfunction? What are some budget-friendly options for toilet paper dispensers? What are they? The code for the topic. What are they? How do they get information: Online research, manufacturer or supplier websites, and industry publications. How do they communicate: Email or online inquiries, phone calls, in-person communication. What media do they consume: Any social media may market the toilet paper dispenser at any time! Do they belong to any associations: Possibly, facility management, janitorial services, or hygiene. Do they have relevant hobbies: The relevance of hobbies may vary depending on the specific customer and their interests. However, customers who are involved in facility management, janitorial services, or hygiene-related roles may have hobbies or interests related to interior design, cleaning and maintenance, sustainability, or technology, which could be relevant to their use and selection of toilet paper dispensers. Negative Info Negative Info Are there consumers you don’t want: We want those who care about the environment, innovation, and saving money. Too difficult: Customers who have unique or complex requirements, or who may require extensive customization, installation, or maintenance of the toilet paper dispenser may be more challenging to serve or support. Too expensive to support: Customers who require significant ongoing support, customer service, or maintenance for the toilet paper dispenser, but do not generate enough revenue or profit margins to justify the costs of servicing them, may not be a cost-effective target audience. Not enough budget: Customers who may not have sufficient budget or spending power to afford the toilet paper dispenser or its associated costs, such as installation, consumables, or ongoing maintenance, may not be a viable target audience. Wrong industry: Customers who do not belong to the industry or market segment that the toilet paper dispenser idea is targeting may not be relevant for the product.

User Story

Transcript: Epic/User Story 9/20/2018 © 2009-2018 CRM Web Solutions, LLC. All Rights Reserved. Scrum Master Presented By: Time-Box By Scrum Master 15 Minutes Agenda Agenda 1. What is Epic? 2. What is a user story? 3. Who writes user stories? 4. Template of user story 5. Benefits of user stories Epic An Epic can be defined as a big chunk of work that has one common objective. It could be a feature, customer request or business requirement. In backlog, it is a placeholder for a required feature with few lines of description. It tells compactly about final output of user needs. In the beginning, it may not contain all the details that team needs to work on. These details are defined in User Stories. An epic usually takes more than one sprint to complete. The Epics we are working today has the duration of 6 months. Epic Epic The Basic unit of work defined in Scrum is user story. But very often, when Product Owner/Stakeholders writes a user story for a feature or against customer request, that looks simple in the beginning. But, while covering all related work and scenarios, same user story expands so much that it can not fit either in a week or a sprint time-frame. It is the time to consider this big user story as epic and start slicing it in smaller user stories. "Think of epic as a book and user stories are its’ chapters". Epic Example Future Single Center Success As a single center owner, I wear many hats which means I do not have time in the middle of the day to implement a new system nor do I have the time to sit through trainings. Because I need this system, I want an ‘out of the box’ solution that just works and that doesn’t involve a lot of interaction on my part so that I can spend more time running my business, working with my staff, the families and most importantly – the kids. Given how busy I am during my workday and dealing with limited resources, when I sign up for ChildCareCRM I will then have a seamless on-boarding experience that I can execute on my own. Acceptance Criteria: • Ability to self-onboard from signup to billing • Comprehensive training videos and user guides available • Customer success already knows how to assist me when I may need help • Ability to pay for ChildCareCRM to deploy my system for me Example Example Center-Based User Experience (Epic 1) Future Single Center Success (Epic 2) Partnerships for the User's Benefit (Epic 3) User Story User Story A short, simple description of a feature told from the perspective of the person who desires the new capability, usually a user or customer of the system. All user stories include a written sentence or two and, more importantly, a series of conversations about the desired functionality or outcomes. Slim and High-Level Requirements A good way to think about a user story is that it is a reminder to have a conversation with your customer (in Scrum project stakeholders are called customers). User story is just-in-time analysis. In short, user stories are very slim and high-level requirements. A user story represents a small piece of business value that a team can deliver in an iteration. Who writes user stories? Anyone can write user stories. It's the product owner's responsibility to make sure a product backlog of agile user stories is there. Also, note that who writes a user story is far less important than who is involved in the discussions of it. When are user stories written? User stories are written throughout the Scrum project. Usually a Story-writing workshop is held near the start of the Sprint. Everyone on the team participates with the goal of creating a product backlog that fully describes the functionality to be added over the course of the project or a three to six-month release cycle within it. How to Write Good User Stories User’s requirements written from that end user’s perspective. A user story is not a context less feature, written is “dev” speak. User story can be written in simple words. You don't need to use any technical language. Describe user story in your own words. How is detail added to user stories? Detail can be added to user stories in two ways: By splitting a user story into multiple, smaller user stories. By adding “Conditions of Satisfaction/Acceptance Criteria ” Acceptance Criteria Goals To clarify what the team should build before they start work To ensure everyone has a common understanding of the problem/need of the customer To help team members know when the story is complete To help verify the story via automated tests User Story Template They typically follow a simple template: As a <type of user/persona>, I want <some feature> so that <some reason> Let’s break this down one step further; As a <type of user/persona> — this is the WHO. Who are we building this for? Who is the user? I want <some feature> — this is the WHAT. What are we building? What is the intention? So that <some reason> — this is they WHY. Why are we building it? What is the value for the customer? “As a [persona], I [want to], [so that].”

User Story

Transcript: EAS Steering Committe 21.06.2018 Showcases New European Atlas of the Seas A user story Professional users of EAS Looking for pre-existing information for a marine installation assesment What? 1 The Atlas of the seas offers a wide variety of marine and coastal information grouped by thematic area Key marine information available more than 100 layers divided in 22 thematic areas The goal is to perform the best possible characterization of the marine and coastal AoI (Area of Interest) facing the planification of a marine installation project. Information by thematic area The professionals of the marine sector look for multidisplinar information on the field in order to assist their project planning - Geophysical and oceanographic conditions - Environmental constraints - Potential coastal impact How? 2 Marine installations previously present in the AOI (Area of Interest) Geophysical characterisitics of the sea surface and marine seabed Environmental constraints, marine spatial planning information Socio economic information from the coastal stakeholder area Information Selection by thematic area Side menu for layer management Visual localization of relevant features On click interaction for feature data access Information Selection by thematic area Results 3 Exportable information with professional interest from EAS The main aim of a professional user of the EAS will be to get usable sources for reporting and assesing Exported Map Exported graphs Embebed url Visualization of areas to be avoided or apects to have into account for taking the project in place Usability of EAS outputs Reference of the data providers for each type of information Common Challenges Assets of the new EAS Challenge 1 Challenge 1 Challenge 2 Challenge 2 Challenge 3 Challenge 3 Solutions Suistainable project Solution 1 Solution 1 Solution 2 2 Solution Solution 3 3 Solution Solution 4 Solution 4 Working together Next steps Technical developments Tech Dev Tier 3 Look & feel Tier 3 Functions Pricing Content Standard Standard Premium Premium

Now you can make any subject more engaging and memorable