This document discusses user stories and how they can help software development teams understand user needs better than traditional requirements specifications. It provides examples of proper user stories, outlines key principles of writing effective stories, and explains how stories evolve through collaborative conversations between business stakeholders and developers. The document cautions that while documents are not abandoned, less documentation is preferable to reduce overhead and allow stories to change shape based on feedback.
Design 101 : Beyond ideation - Transforming Ideas to Software RequirementsHawkman Academy
Most people with an idea ‘know’ they’ve got a market for a product but they usually have limited UX/design capabilities and will not probably develop something that users don’t really want. They also need to move fast as they probably have a limited (or zero) budget. This presentation will give you some insights on how you can achieve this in a light weight way.
User stories writing - Codemotion 2013Stefano Leli
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.
Palestra realizada em 17/02/2010 baseada no livro "Implementing Lean Software Development: From Concept to Cash" de Mary e Tom Poppendieck.
Esta apresentação faz parte do Bluesoft Labs.
Design 101 : Beyond ideation - Transforming Ideas to Software RequirementsHawkman Academy
Most people with an idea ‘know’ they’ve got a market for a product but they usually have limited UX/design capabilities and will not probably develop something that users don’t really want. They also need to move fast as they probably have a limited (or zero) budget. This presentation will give you some insights on how you can achieve this in a light weight way.
User stories writing - Codemotion 2013Stefano Leli
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.
Palestra realizada em 17/02/2010 baseada no livro "Implementing Lean Software Development: From Concept to Cash" de Mary e Tom Poppendieck.
Esta apresentação faz parte do Bluesoft Labs.
Real World Effective/Agile Requirements - IBM Innovate 2010 -sally elattaSally Elatta
This is the presentation I offered at the IBM 2010 conference around real world techniques and best practices for effective requirements gathering and release planning. Enjoy!
The practical value of this presentation is to help business analysts to adapt to agile and use appropriate techniques to achieve better requirements. The key take aways;
-Understand the difference between a traditional way of dealing with requirements and the agile way.
-Describe core agile requirements practices
-Understand challenges with agile requirements
-Learn sty a high level the User story concepts and Describe where they fit in the life cycle
-Understand how Acceptance tests extend User Stories
-Understand the evolution of user stories and their and elaboration throughout the life cycle
Gathering and defining software requirements is difficult.
One Agile technique to help address this challenge is writing user stories, which are short descriptions of functions that an end-user would want.
While user stories help convert concepts into functions, writing good user stories is easier said than done.
Agile Software Development in practice: Experience, Tips and Tools from the T...Valerie Puffet-Michel
In the Division of Student Affairs at the University of Connecticut, the Applications Development team has been developing and delivering custom software using agile methods for over four years. In this session, we'll share our experiences and give you a behind the scenes look at how agile software development really works by walking you through how we translate the unique business needs of our clients into deployed software.
Gathering and defining software requirements is difficult. One Agile technique to help address this challenge is writing user stories, which are short descriptions of functions that an end-user would want. While user stories help convert concepts into functions, writing good user stories is easier said than done.
What you’ll learn in this presentation:
• The basics of user stories.
• How user stories fit into the overall Agile planning process.
• How to write a user story.
Practicing What We Preach: designing usage centered deliverablesAviva Rosenstein
Slides and worksheets from a workshop presented at the IA Summit, 2011
During any product development process, interaction designers and researchers must communicate with internal and external team members and decision makers. All too often we talk the UX talk but we forget to walk the UX walk: we send out deliverables without thinking about our needs, the needs of the recipients and what we want to achieve.
Creating design deliverables that address the needs, goals and constraints of those team members will enhance your credibility as a design expert while improving the overall effectiveness of your organization.
This presentation includes a lean framework for understanding users' needs and goals that can help you design the right deliverable (or interface) at the right time for any working environment.
User Story Writing & Estimation For Testers By Mahesh VaradharajanAgile Testing Alliance
This session aims to introduce the critical aspects of user story formulation like INVEST principle, requirements hierarchy in Agile - with focus on aspects related to Agile Testing, such that it fits into the overall theme of the event. Through an exercise, with Lego blocks, the session will address the following aspects: Testability of user stories and importance of acceptance criteria. Handling NFRs - either as part of acceptance criteria or a new user stories. DoD and accommodating testing efforts as part of user story estimation; Defects as user stories. Dependency management between user stories via story maps.
Talk including Demo for the learning objectives outlined above
Real World Effective/Agile Requirements - IBM Innovate 2010 -sally elattaSally Elatta
This is the presentation I offered at the IBM 2010 conference around real world techniques and best practices for effective requirements gathering and release planning. Enjoy!
The practical value of this presentation is to help business analysts to adapt to agile and use appropriate techniques to achieve better requirements. The key take aways;
-Understand the difference between a traditional way of dealing with requirements and the agile way.
-Describe core agile requirements practices
-Understand challenges with agile requirements
-Learn sty a high level the User story concepts and Describe where they fit in the life cycle
-Understand how Acceptance tests extend User Stories
-Understand the evolution of user stories and their and elaboration throughout the life cycle
Gathering and defining software requirements is difficult.
One Agile technique to help address this challenge is writing user stories, which are short descriptions of functions that an end-user would want.
While user stories help convert concepts into functions, writing good user stories is easier said than done.
Agile Software Development in practice: Experience, Tips and Tools from the T...Valerie Puffet-Michel
In the Division of Student Affairs at the University of Connecticut, the Applications Development team has been developing and delivering custom software using agile methods for over four years. In this session, we'll share our experiences and give you a behind the scenes look at how agile software development really works by walking you through how we translate the unique business needs of our clients into deployed software.
Gathering and defining software requirements is difficult. One Agile technique to help address this challenge is writing user stories, which are short descriptions of functions that an end-user would want. While user stories help convert concepts into functions, writing good user stories is easier said than done.
What you’ll learn in this presentation:
• The basics of user stories.
• How user stories fit into the overall Agile planning process.
• How to write a user story.
Practicing What We Preach: designing usage centered deliverablesAviva Rosenstein
Slides and worksheets from a workshop presented at the IA Summit, 2011
During any product development process, interaction designers and researchers must communicate with internal and external team members and decision makers. All too often we talk the UX talk but we forget to walk the UX walk: we send out deliverables without thinking about our needs, the needs of the recipients and what we want to achieve.
Creating design deliverables that address the needs, goals and constraints of those team members will enhance your credibility as a design expert while improving the overall effectiveness of your organization.
This presentation includes a lean framework for understanding users' needs and goals that can help you design the right deliverable (or interface) at the right time for any working environment.
User Story Writing & Estimation For Testers By Mahesh VaradharajanAgile Testing Alliance
This session aims to introduce the critical aspects of user story formulation like INVEST principle, requirements hierarchy in Agile - with focus on aspects related to Agile Testing, such that it fits into the overall theme of the event. Through an exercise, with Lego blocks, the session will address the following aspects: Testability of user stories and importance of acceptance criteria. Handling NFRs - either as part of acceptance criteria or a new user stories. DoD and accommodating testing efforts as part of user story estimation; Defects as user stories. Dependency management between user stories via story maps.
Talk including Demo for the learning objectives outlined above
Understanding User Needs and Satisfying ThemAggregage
https://www.productmanagementtoday.com/frs/26903918/understanding-user-needs-and-satisfying-them
We know we want to create products which our customers find to be valuable. Whether we label it as customer-centric or product-led depends on how long we've been doing product management. There are three challenges we face when doing this. The obvious challenge is figuring out what our users need; the non-obvious challenges are in creating a shared understanding of those needs and in sensing if what we're doing is meeting those needs.
In this webinar, we won't focus on the research methods for discovering user-needs. We will focus on synthesis of the needs we discover, communication and alignment tools, and how we operationalize addressing those needs.
Industry expert Scott Sehlhorst will:
• Introduce a taxonomy for user goals with real world examples
• Present the Onion Diagram, a tool for contextualizing task-level goals
• Illustrate how customer journey maps capture activity-level and task-level goals
• Demonstrate the best approach to selection and prioritization of user-goals to address
• Highlight the crucial benchmarks, observable changes, in ensuring fulfillment of customer needs
Buy Verified PayPal Account | Buy Google 5 Star Reviewsusawebmarket
Buy Verified PayPal Account
Looking to buy verified PayPal accounts? Discover 7 expert tips for safely purchasing a verified PayPal account in 2024. Ensure security and reliability for your transactions.
PayPal Services Features-
🟢 Email Access
🟢 Bank Added
🟢 Card Verified
🟢 Full SSN Provided
🟢 Phone Number Access
🟢 Driving License Copy
🟢 Fasted Delivery
Client Satisfaction is Our First priority. Our services is very appropriate to buy. We assume that the first-rate way to purchase our offerings is to order on the website. If you have any worry in our cooperation usually You can order us on Skype or Telegram.
24/7 Hours Reply/Please Contact
usawebmarketEmail: support@usawebmarket.com
Skype: usawebmarket
Telegram: @usawebmarket
WhatsApp: +1(218) 203-5951
USA WEB MARKET is the Best Verified PayPal, Payoneer, Cash App, Skrill, Neteller, Stripe Account and SEO, SMM Service provider.100%Satisfection granted.100% replacement Granted.
B2B payments are rapidly changing. Find out the 5 key questions you need to be asking yourself to be sure you are mastering B2B payments today. Learn more at www.BlueSnap.com.
LA HUG - Video Testimonials with Chynna Morgan - June 2024Lital Barkan
Have you ever heard that user-generated content or video testimonials can take your brand to the next level? We will explore how you can effectively use video testimonials to leverage and boost your sales, content strategy, and increase your CRM data.🤯
We will dig deeper into:
1. How to capture video testimonials that convert from your audience 🎥
2. How to leverage your testimonials to boost your sales 💲
3. How you can capture more CRM data to understand your audience better through video testimonials. 📊
Recruiting in the Digital Age: A Social Media MasterclassLuanWise
In this masterclass, presented at the Global HR Summit on 5th June 2024, Luan Wise explored the essential features of social media platforms that support talent acquisition, including LinkedIn, Facebook, Instagram, X (formerly Twitter) and TikTok.
The world of search engine optimization (SEO) is buzzing with discussions after Google confirmed that around 2,500 leaked internal documents related to its Search feature are indeed authentic. The revelation has sparked significant concerns within the SEO community. The leaked documents were initially reported by SEO experts Rand Fishkin and Mike King, igniting widespread analysis and discourse. For More Info:- https://news.arihantwebtech.com/search-disrupted-googles-leaked-documents-rock-the-seo-world/
Event Report - SAP Sapphire 2024 Orlando - lots of innovation and old challengesHolger Mueller
Holger Mueller of Constellation Research shares his key takeaways from SAP's Sapphire confernece, held in Orlando, June 3rd till 5th 2024, in the Orange Convention Center.
Digital Transformation and IT Strategy Toolkit and TemplatesAurelien Domont, MBA
This Digital Transformation and IT Strategy Toolkit was created by ex-McKinsey, Deloitte and BCG Management Consultants, after more than 5,000 hours of work. It is considered the world's best & most comprehensive Digital Transformation and IT Strategy Toolkit. It includes all the Frameworks, Best Practices & Templates required to successfully undertake the Digital Transformation of your organization and define a robust IT Strategy.
Editable Toolkit to help you reuse our content: 700 Powerpoint slides | 35 Excel sheets | 84 minutes of Video training
This PowerPoint presentation is only a small preview of our Toolkits. For more details, visit www.domontconsulting.com
The Influence of Marketing Strategy and Market Competition on Business Perfor...
User Stories Applied
1. Understanding
User Stories
Rachel Davies
rachel@agilexp.com
My Agile timeline
Board
Programmer Agile director Conference Author
on XP team Coach chair
2000 2003 2009
1
2. A few companies ..
About you ..
Does your team build
software from:
• requirements specs?
• from user stories?
• from something else?
2
3. Embrace Change!
• Agile projects focus on delivering value early
and often
• Scope changes allowed throughout the project
• Agile requires involvement of business
throughout the lifecycle to steer priorities and
explain their needs.
Agile Manifesto
• Shared values and principles
for better ways to develop
software (2001)
• www.agilemanifesto.org
3
5. Customer collaboration
over contract negotiation
Responding to change
over following a plan
5
6. Key Agile Principles
• The goal of Agile Development is to satisfy the
customer through early and continuous deliveryof
valuable software
• Business people and developers must work
together daily throughout the project
• Changing requirements are welcomed, even
late in development
• Focus on flow of value to help prioritize and plan
Traditional Requirements
• Are conveyed in
documents
• Written in impersonal
language
• Tangled together so it’s
hard to separate out
and prioritize
6
7. What other ways can we use to
understand what software to build?
Try User Stories
• User stories help us explore what the software
needs to do from a user perspective.
• Knowing who the user is and what problems
they are trying to solve helps us develop better
software.
7
8. Questions help find context
Ask questions to uncover the user stories..
• Who will use it?
• What problem are they trying to solve?
• What’s their goal?
• Why is this valuable to them?
Understand this before diving into solution
details
?
Time-boxed by definition
“One thing the customer wants the system to do.
Stories should be estimable at between one to
five ideal programming weeks. Stories should be
testable.”
“Stories need to be of a size that you can build a
few of them in an iteration”
“Stories don't have to represent business value to
the customer team, but they do have to
represent progress. Only the customer team
knows what it will consider progress, so they
have to do the slicing” Kent Beck
8
9. Three Cs to a user story
Card: user goal written on an index card
Conversation: team gets to ask questions
Confirmation: acceptance criteria
Ron Jeffries, Xprogramming.com
Team Planning with User Stories
~ 2000
9
10. As a .. I want .. template
(2001)
Story Example
Find a book by ISBN
As a book buyer,
I want to be able to find a book by
entering the ISBN number
so that I can find a specific book quickly
10
11. Example story card
As an operations engineer,
I want to be able to
reconfigure the timeout of a
specific service request
without needing to restart
the backend service process
from
Kerry Jones, BBC
Notice they are not
As a system”!
Acceptance Criteria
Elaborate user stories with examples to
define acceptance criteria
Focus in on demonstrable aspects that we
can use to confirm story is complete
11
12. But ..
Are these user stories?
• “As a user, I want ..X so I can have X
• “As a developer, I want ..
• “As a system, I want ..
Do these help us understand
• user context?
• business value?
Or are they a waste of time?
12
13. Fred’s user story template
• Doesn’t even print to a
single sheet of A4!
• Passed between BA,
Dev, Tester without
conversation
• Same problems as
traditional requirements
Remember this
13
14. Why User Stories Work
• User stories add conversations to the
development cycle
• These conversations do not mean that
documents are abandoned
• But you try to write down less where
possible because that reduces overhead of
maintaining documents
Stories Change Shape
User stories evolve thru conversation
14
15. Pinning down can kill the idea
Iterate software based on feedback
Beware of Epics
Sometimes a story is too large to be implemented in a single iteration, we
call these Epics.
Such stories will need to be broken down for reliable estimates.
15
16. What about non-functional
requirements?
Any Questions?
Contact info:
Email: rachel@agilexp.com
Twitter: rachelcdavies
Blog: http://agilecoach.typepad.com/
16