You're about to create your best presentation ever

Get started with Prezi

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

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

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

User Story

Transcript: Assets Understanding User Stories Exploring the Essence of User-Centric Design Comment Definition and Purpose Importance in Agile Development A user story is a concise description of a feature told from the end-user's perspective. It explains what the user needs to achieve and why it is important. User stories are fundamental in Agile, enabling iterative development, collaboration, and a focus on delivering user value. They promote customer-centric design and drive product success. Understanding Actors and Goals in User Stories Writing Effective User Stories Understanding the INVEST Criteria and Acceptance Criteria are pivotal in crafting user stories that drive value and clarity in agile development. Story Mapping is a powerful technique for visualizing user needs and prioritizing tasks effectively. The actor or persona represents the user involved, while the action or goal defines the purpose of the story. These components are crucial for crafting effective user stories. INVEST Criteria Understanding User Stories The INVEST criteria are essential guidelines for creating effective user stories that are Independent, Negotiable, Valuable, Estimatable, Small, and Testable. This framework ensures stories are well-defined and ready for implementation. User stories define requirements from an end-user perspective, emphasizing their needs and goals. They outline 'who', 'what', and 'why' of a feature. Actor or Persona Visual Inspiration The actor or persona in a user story embodies the user role or character who will interact with the product or feature. Utilize visual aids to enhance understanding and engagement in user story workshops and planning sessions. Incorporating sketches, diagrams, and prototypes can streamline communication and improve collaboration among team members. Acceptance Criteria Acceptance criteria define the conditions that must be met to consider a user story complete and accepted by stakeholders. They are specific, measurable, and help validate that the functionality meets user expectations. Action or Goal Outcome or Benefit Story Mapping The action or goal refers to the specific task or objective that the user wants to accomplish when using the product or feature. The outcome or benefit describes the result or value that the user gains from completing the action or achieving the goal in the user story. Story Mapping is a visual way to organize user stories based on user flow, providing a big-picture view of the product backlog. It helps prioritize features, identify dependencies, and improve communication within the team. Payment Gateway Integration User Profile Management Task Breakdown and Assignments Facilitate secure and seamless online transactions by integrating reliable payment gateways that prioritize user data protection and transaction efficiency. Empower users with personalized experiences through robust user profile management systems that allow customization and easy access to account settings and preferences. User Story Acceptance and Sign-off Task breakdown involves the detailed analysis and division of project requirements into manageable assignments for team members. Efficient assignments ensure that each task contributes to the overall project goal, enhancing productivity and accountability. Product Search Functionality User Story Examples: Summary Sprint Planning Monitoring Progress Enhance user experience by implementing intuitive search functionality that enables users to find desired products quickly and accurately. Illustrative examples of user stories demonstrate the practical implementation and benefits of user-centric design in various aspects of product development and user experience. During sprint planning, the team collaborates to define tasks, set goals, and allocate resources effectively within the specified timeframe. This phase sets the pace for sprint execution and ensures alignment with project objectives. Continuous monitoring of progress involves tracking project milestones, identifying bottlenecks, and adapting strategies to ensure timely delivery and quality outcomes. Regular progress checks enhance transparency and facilitate proactive problem-solving. Effective collaboration ensures user stories align with requirements and meet expectations. Customer Registration Process Implementing User Stories Examples of User Stories Ensure seamless user onboarding with a streamlined registration process that captures essential user information efficiently. Sprint planning is a crucial phase in agile project management, ensuring a clear roadmap for development cycles. Task breakdown and assignments optimize team efficiency and collaboration. Monitoring progress allows for real-time adjustments and ensures project alignment with goals. Exploring practical applications of User Stories in real-world scenarios. Collaborative Review Process Feedback and Iterations Collaboration between stakeholders, developers, and testers to validate user stories. Continuous

Explore our templates for more presentation inspiration

Grant Proposal Presentation for NonProfit & Education | Prezi

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

Best Creative Resume Templates to Customize | Prezi

Description: Stand far above the stacks and stacks of flat, boring resumes on any hiring manager’s desk with a Prezi resume template. Just customize this Prezi presentation template to create your very own “Prezume” and impress them with your dynamism, coolness, and originality.

Best Executive Presentation Template to Customize | Prezi

Description: Show the big picture, zoom in on details, and explain clearly how it all relates with this Prezi executive brief or Prezi nonprofit template. The lively image and bold colors make it easy to create compelling, engaging executive brief or nonprofit presentations.

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.

Now you can make any subject more engaging and memorable

Get started with Prezi