The document discusses planning and estimating user stories for software development. It provides guidance on writing user stories, estimating story points, determining team velocity, prioritizing stories, and planning iterations and releases. Key points include writing stories from the user's perspective using active voice, estimating stories as a team in story points rather than hours, using velocity from past iterations to plan future work, and prioritizing stories based on business value and risk.
This presentation describe
What is the need for user stories in Agile project?
What is a story?
Why story?
What is criteria for a good story?
What are not stories?
Prerequisite? Knowledge of Scrum and it’s terms
Overview
- What is a User Story?
- User Story template
- examples of User Stories
- User Story Checklist
- Why not tasks?
- What is Acceptance Criteria?
- Examples of Acceptance Criteria
- Acceptance Criteria checklist
This presentation describe
What is the need for user stories in Agile project?
What is a story?
Why story?
What is criteria for a good story?
What are not stories?
Prerequisite? Knowledge of Scrum and it’s terms
Overview
- What is a User Story?
- User Story template
- examples of User Stories
- User Story Checklist
- Why not tasks?
- What is Acceptance Criteria?
- Examples of Acceptance Criteria
- Acceptance Criteria checklist
Writing Good User Stories (Hint: It's not about writing)one80
User stories are typically the foundation of the Product Backlog. However, the original purpose has been lost. This is from a presentation that was given to help remind everyone of what User Stories are, and what they aren't. The purpose of User Stories is to drive conversations, not to hand "requirements" from one group to the next.
Learn to use the user story backlog as a way to describe user’s experience with your product.
Section 1: Importance of Product Owners Roll.
Identifying Scrum’s Product Owners roll.
Diagrammatic representation of PO Activities.
Diagrammatic representation of Product Feature Development tracks.
Section 2: User stories & Product Backlog Management.
Agile User Stories overview .
Acceptance Criteria.
Backlog Management.
Section 3: Project Scope, Product Backlog and Story Mapping.
User Story Mapping Steps.
Story Mapping example with valuable releases.
Benefits of User Story Mapping.
Do you want to write great User Stories that provide the vehicle for conversation and confirmation that we build the right thing? Do you struggle with splitting stories so that they still provide business value but can be accomplished within a fraction of your iteration? We will do a quick refresher on User Story formatting to include Acceptance Criteria. Additionally we will learn techniques for splitting stories in this interactive workshop.
User story can be described as functional increment and it is a key element in agile environment. This presentation introduces fundamentals about user stories that can be used to educate teams or simply to review the basics.
User Stories Writing - Codemotion 2013Fabio Armani
Stefano Leli (Freelance) - Fabio Armani (OpenWare)
Scrivere user stories dovrebbe essere facile...almeno in teoria. In realtà nella pratica ci troviamo troppo spesso a combattere con storie vaghe o troppo tecniche, storie che non possono essere testate o addirittura che non portano alcun valore. In questo workshop cercheremo assieme di comprendere la differenza tra requisiti funzionali e User Story, tra User Story e Use Case, mediante dei case study.
Lean Startup + Story Mapping = Awesome Products FasterBrad Swanson
To deliver the right outcomes, you need to learn your customers needs and validate your assumptions as early as possible. This means getting an early version of your product completed to start testing, validating and improving. This session will demonstrate how to combine Lean Startup and User Story Mapping techniques to determine where to start and how to learn early and often.
Participants will start with a partially completed Lean Canvas to flesh out and then define a product roadmap by building a Story Map. We will use Lean Startup concepts of Minimal Viable Product (MVP) and validated learning to focus on outcome over output.
Learning objectives:
Understand the importance of accelerated learning and techniques to achieve it
How a Lean Canvas can help shape your product vision and MVP
How to build a story map to create a product roadmap
How to use a story map to validate your users' journey
One of the biggest challenges of making things together is actually to communicate to other people what is our idea. Considering that humans are not so good at telepathy, the only tool we have is language. For years, people struggled on collect requirements in big books that no-one want read, until we discovered another way: telling stories. This talk is taking something very familiar to many, the "user story" format, and will explore it from an unusual point of view. We're going to see how to use it, how to avoid common pitfalls and how to get the real sense of "user stories".
Writing Good User Stories (Hint: It's not about writing)one80
User stories are typically the foundation of the Product Backlog. However, the original purpose has been lost. This is from a presentation that was given to help remind everyone of what User Stories are, and what they aren't. The purpose of User Stories is to drive conversations, not to hand "requirements" from one group to the next.
Learn to use the user story backlog as a way to describe user’s experience with your product.
Section 1: Importance of Product Owners Roll.
Identifying Scrum’s Product Owners roll.
Diagrammatic representation of PO Activities.
Diagrammatic representation of Product Feature Development tracks.
Section 2: User stories & Product Backlog Management.
Agile User Stories overview .
Acceptance Criteria.
Backlog Management.
Section 3: Project Scope, Product Backlog and Story Mapping.
User Story Mapping Steps.
Story Mapping example with valuable releases.
Benefits of User Story Mapping.
Do you want to write great User Stories that provide the vehicle for conversation and confirmation that we build the right thing? Do you struggle with splitting stories so that they still provide business value but can be accomplished within a fraction of your iteration? We will do a quick refresher on User Story formatting to include Acceptance Criteria. Additionally we will learn techniques for splitting stories in this interactive workshop.
User story can be described as functional increment and it is a key element in agile environment. This presentation introduces fundamentals about user stories that can be used to educate teams or simply to review the basics.
User Stories Writing - Codemotion 2013Fabio Armani
Stefano Leli (Freelance) - Fabio Armani (OpenWare)
Scrivere user stories dovrebbe essere facile...almeno in teoria. In realtà nella pratica ci troviamo troppo spesso a combattere con storie vaghe o troppo tecniche, storie che non possono essere testate o addirittura che non portano alcun valore. In questo workshop cercheremo assieme di comprendere la differenza tra requisiti funzionali e User Story, tra User Story e Use Case, mediante dei case study.
Lean Startup + Story Mapping = Awesome Products FasterBrad Swanson
To deliver the right outcomes, you need to learn your customers needs and validate your assumptions as early as possible. This means getting an early version of your product completed to start testing, validating and improving. This session will demonstrate how to combine Lean Startup and User Story Mapping techniques to determine where to start and how to learn early and often.
Participants will start with a partially completed Lean Canvas to flesh out and then define a product roadmap by building a Story Map. We will use Lean Startup concepts of Minimal Viable Product (MVP) and validated learning to focus on outcome over output.
Learning objectives:
Understand the importance of accelerated learning and techniques to achieve it
How a Lean Canvas can help shape your product vision and MVP
How to build a story map to create a product roadmap
How to use a story map to validate your users' journey
One of the biggest challenges of making things together is actually to communicate to other people what is our idea. Considering that humans are not so good at telepathy, the only tool we have is language. For years, people struggled on collect requirements in big books that no-one want read, until we discovered another way: telling stories. This talk is taking something very familiar to many, the "user story" format, and will explore it from an unusual point of view. We're going to see how to use it, how to avoid common pitfalls and how to get the real sense of "user stories".
Agile User Stories | The complete ReviewDavid Tzemach
The main sections of this presentation
1. Overview
2. Story Points vs. Time Estimations
3. The responsibilities
4. The benefits of using stories
5. How to write great stories
6. The mistake you can do when writing stories
7. A Template for writing stories
8. Key components of stories
User Story Mapping, Discover the whole storyJeff Patton
Variations of these slides have been used in a variety of talks.
These slides support discussions on why stories work, and when they don't. And, on story mapping, how and why it works.
Creating a backlog of user stories is pretty straight forward but it doesn't help you when it comes to decisions like what to build first, how to prioritize and groom the backlog, how to scope and plan the project, and how to visualize progress. The traditional backlog is simply too flat and often too long to help you see the bigger picture and make good decisions. User Story Mapping helps simplify all of these common project issues. By adding a third dimension to your backlog, your team will make better decisions about priorities, scope, and planning while improving your ability to visualize progress.
In this practical session I’ll cover the basics of user story mapping before walking you through case studies of how our teams are using this approach and the results we are achieving. I'll show you the before, during, and after pictures from several projects so that you can understand how our maps progress during the projects and how we use them to influence iterative development, promote good decision making, and visualize priorities, plans, scope and progress.
Introduce gathering stories technologies as user interview, questionnaires, observation & story-writing workshops.
Share some guidelines and real cases about to make good stories as size the story to the horizon & including user roles in the stories.
Join Jeff Rohrs, VP of Marketing Insights for the ExactTarget Marketing Cloud, for a discussion on how to make the most of the mobile moments along the customer journey. Learn how the smartphone is disrupting traditional marketing funnels and why marketing creativity is now as much about creating new “moments that matter” as it is optimizing existing ones.
Single window experience sharing workshop - CRIMSONLOGICAAEC_AFRICAN
Presentation made during the "Sharing Experience session" on 15 march 2017 - 8th General Assembly of the African Alliance for Electronic Commerce, held in Nairobi.
Increased reach and lowered CPA with DoubleClickMark Squires
THE GOALS
- Maximize every pound in the marketing budget
- Keep the CPA in balance while serving dynamic vouchering campaigns to a new audience on mobile devices
- Decrease the rate of costly, ineffective GIF backup images
THE APPROACH
- Experiment with a mixed-mode campaign created on Google Web Designer
- Use Flash backed up by HTML5 to ease the switch to HTML5-only campaigns
THE RESULTS
- Backup images have decreased from 7% to 0.5%
- HTML5 outperforms Flash so convincingly that marketers switched to an HTML5-only approach
- HTML5 campaigns increase reach by adding mobile inventory yet decrease overall eCPA by 12%
- Process 50% faster because designers can create ads without help from a developer
Portfolio Management in JIRA - Karen Branham and Scottie BrimmerAtlassian
As our company's use of JIRA increased, we sensed a need to track portfolio projects within JIRA. But we didn’t find any plugins that met our need, so we built our own process. Through a combination of custom issue types, fields, and workflows, our leaders and PMO can now see the entire portfolio of 60 projects.
Shared Experience: The What and Why of Sharing for Marketers (Graham Brown mo...Graham Brown
What do we share and why do we do it?
Graham Brown from mobileYouth offers some unique psychological and anthropological perspectives on this fundamentally human behavior
One of the biggest challenges of making things together is actually to communicate to other people what is our idea. Considering that humans are not so good at telepathy, the only tool we have is language. For years, people struggled on collect requirements in big books that no-one wants to read, until we tried in another way: telling stories. But even if the User Story format is something that may sound familiar to many, using it effectively isn’t that easy. This is not about the mantra-formula “as User…”. It’s a common-sense - sometimes opinionated - exploration on how we use user stories during the process of creating digital products. We’re going to see how to use it, how to avoid common pitfalls and how to get the real sense of “user stories”.
Using Programmatic to Reach People in the Moments that MatterIncubeta NMPi
Is programmatic the biggest buzz word in advertising? Yes, because it has some of the biggest opportunities. These slides look at where the real opportunity in programmatic advertising lies. From audience data to creative design here are the tips and tricks.
This presentation provides the who, what, why, how, and when for user stories. It shows you examples of good and bad stories, how to get them in the first place, and how they define done on agile projects.
How UXD Can Provide Leadership Skills for Complex Software Projects: A 4-Day ...Greg Laugero
This presentation was given at the Usability Professionals Association 2008 Conference. It is for UXD professionals who are ready to take their next career step and move into a leadership role for complex projects. We'll discuss practical techniques, along with hard-earned lessons, for bringing order to the often overwhelming chaos of difficult projects.
Through the webinar, she will give an introduction to the user story concept. How to create them? How they can help us build better products for our customers. Do's and Don'ts.
From Use to User Interface- This 3-4 hour tutorial describes a practical approach to translating the goals users would like to achieve and the tasks they wish to accomplish into user interface designs that effectively support those goals and tasks.
Art of Writing in Agile : STC Summit 2017Shikha Saxena
Please find enclosed the presentation on "Art of Writing in Agile" that I recently presented, during #STCSummit2017 #stc #stc2017 in Washington DC on 9th May, 2017.
Three experiments I have done with data science. Related to text analysis, integration. Focusing on the learning's rather than details on how it was done with source code. I feel it is important to see this subject in relation to business problems rather than as pure branch of Statistics. Focusing on what has to be done enabled me to find the right solution from a complicated and very interesting subject.
Life cycle of user story: Outside-in agile product management & testing, or...Ravi Tadwalkar
It has always been my pleasure and fun to facilitate workshops for PM (product management) community at and outside Cisco, although this was first time I did a BDD workshop with PMs alone. And I realized today how PayPal has been a really great venue for SVPMA annual product camp "unconference" for 1k+ PMs with 550 waitlisted this year! I look forward to this event every year now...huge success!
Abstract:
As Product Owners and Managers are driving innovation thru' those fuzzy ideas in terms of scenarios, testers have always been thinking about those in form of test cases which take form of acceptance criteria for those scenarios. When you talk about those scenarios to your teams or even peers, you see those diverging ideas converging to something concrete.
That's how BDD helps you shape that idea. That fuzzy scenario, when validated thru' an engineering "spike", can be useful for product management MRD/PRD/use-case-models/stories...whatever it is that you want to use to drive product development.
And this is where Agile Tester role begins! So instead of doing top-down or bottoms-up product management & testing, try this outside-in approach. Go for it!
My workshop on BDD is about what I term as "Outside-in agile product management". To understand what I really mean by that, here is my slideshare presentation used rarely when teaching from the back of the class during this hyper-interactive workshop.
![Customer Team ,[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)