SlideShare a Scribd company logo
1 of 33
Story of User Story
Balaji Sathram, CSP, PMI-ACP.
Scrum master, Sabre.
Agenda
• User Story-History
• User Story - Brief
• User Story-Templates
• Writing good user stories
• Slicing user stories
• To maintain good user stories
• Additional Terms
• User Story - Prioritization
• User Story - Estimation
User Story-History
• Comes from XP (eXtreme Programming)
• 1999: Kent Beck coined the term user stories in Extreme
Programming Explained 1st Edition
• Documenting requirements to Explaining (Tell story about what you
want): Building a common and shared understanding.
• People started following it. But The sad part of the whole episode
is: instead of telling stories, people started writing stories.
• Organizations started documenting user stories:
"shared documents are not shared understanding"
User Story - Brief
What is User Story:
• A concise written description of a piece of functionality that will be
valuable to a user (or product owner) of the software.
• All about the user’s goals
• Carries the value stream to the user
• It contains:
• Value: Requirement of a customer
• Cost: an understanding of what it takes to build
• Validation: that you understand what is happening
User Story-Templates
As a <WHO|ROLE>
I want <WHAT|FEATURE>
So that <WHY|PURPOSE>
OR
Given [context]
When [event]
Then [outcome]
Story Inputs
XP Stories – Ron Jeffries – 3Cs
• In 2001
• Card: Write stories on a card. Just enough
to identify the requirement.
• Conversation: Most of the requirement is
communicated through a conversation.
Information can be stored elsewhere. The
story is a holder for these.
• Confirmation: “How will we know we’ve
done that.” We also need an acceptance
test.
User Story Description
• It is written down on a note card
(e.g. 3x5 inches or 8x13 cm)
• Start with a title.
• Add a concise description using the
templates.
• Add other relevant notes,
specifications, or sketches
• Before building software write
acceptance criteria (how do we know
when we’re done?)
Writing good user stories
• Independent – User Stories should be as independent as possible.
• Negotiable – A User Story is not a contract. It is not a detailed specification.
Story cards are short descriptions of functionality, the details of which are to
be negotiated in a conversation between the customer and the development
team
• Valuable – User Stories should be valuable to the user (or owner) of the
solution. They should be written in user language. They should be features,
not tasks.
• Estimable – User Stories need to be possible to estimate. They need to
provide enough information to estimate, without being too detailed.
• Small – User Stories should be small. Not too small and not too big. DONE in
one iteration
• Testable – User Stories need to be worded in a way that is testable, i.e. not
too subjective and to provide clear details of how the User Story will be
tested. if you can’t test it, you don’t know when you are done
Slicing user stories
• Breaking them down
Slicing User Stories
• Split by workflow steps
• Split by business rules
• Split by happy/unhappy flow
• Split by input options / platform
• Split by test data or data types or parameters
• Split by operations(CRUD)
• Split by test scenarios/test case
• Split by Roles
• Split by external dependencies
• Split based on Mock/Real services
• Split based on acceptance criteria
• Split based on Usability
Some Additional Useful Terms
• Definition of Ready
• Definition of Done
• Acceptance Criteria
• Theme and Epic
Definition of Ready
From Team to Product Owner
• No Open questions
• Test data collected
• No technical dependencies
• Workflow figured out
• Acceptance criteria understood
• Estimated
• Has some business value
• Sized appropriately
Definition of Done
From Team to the Team
• Architectural Review Complete
• Code Review Complete
• Unit Tested
• Test Scenarios Review with BA/PO/Team members
• QA tested
• PO/BA Acceptance
• No Priority 1 or Priority 2 bugs
• Integration
• Known deployment & Rollback plan
Acceptance Criteria
From Product Owner to the Team
• Agreement between the team and the PO on when the story is
accepted
Theme and Epic
PRIORITIZATION
Prioritization
• High-Medium-Low
• MoSCoW
• Kano Analysis
• 1-2-3-4-5
• Stacked Ranking
• Impact Analysis
MoSCoW
• A method to prioritize requirements popularized in the DSDM
(Dynamic systems development method) community is MoSCoW
• Must Have, Should Have, Could Have and Won’t Have
Kano Analysis
• Kano Analysis is a quality measurement tool used to prioritize customer
requirements based on their impact to customer satisfaction.
According to the Kano Model (developed by Dr Noriaki Kano in
the 1980s), a product or service can have three types of
attribute (or property):
• Musts: Which customers expect to be present in a product.
• Satisfiers: Which are not absolutely necessary, but which are
known about and increase the customer's enjoyment of the
product.
• Delighters: Which customers don't even know they want,
but are delighted when they find them.
Impact Analysis
• For every user story, give impact points based on below questions
• What is the impact it is creating if it is implemented
• What is the impact it is creating if it is not implemented
• Multiply both the values which will result in impact score for the user
story
• Higher the score higher the impact
ESTIMATION
Estimation
User Story - What do we Estimate?
Complexity
Uncertainty
Effort
Story Points
• Story Points are the unit of measurement for expressing the overall size of a user story,
feature, or other piece of work.
• The number of story points associated with a story represents the overall size of the story.
• Either Doubles OR Fibonacci Series
Non Linear Scale - Fibonacci Series [1,2,3,5, and 8]
Non Linear Scale - Doubles [1,2,4, and 8]
Estimation Techniques
• Agile Relative Sizing
• Ideal Days
• Planning Poker
• Wideband Delphi
• Affinity Estimating
Relative Estimation
Ideal Days
How long something would take if
• It’s all you worked on
• you had no interruptions
• and everything you need is available
Factors Affecting Ideal Time:
Training, Email, Reviews, Interviewing, Demonstrations, Meetings, Sick Time,
Phone, Bug Fixing, Management review
Planning Poker
An iterative approach to estimating
Steps:
• Each estimator is given a deck of cards, each card has a valid estimate
written on it
• Customer/product owner reads a story and it’s discussed briefly
• Each estimator selects a card that’s his or her estimate
• Cards are turned over so all can see them
• Discuss differences (especially outliers)
• Re-estimate until estimates converge
Wideband Delphi
Is a process that the team can use to generate an estimate
Process:
• Choose the team
• Kick off meeting
• Individual preparation
• Estimation session
• Assemble tasks
• Review results
Affinity Estimation (Lowell Lindstrom)
Affinity estimating is a technique many teams use to quickly and easily
estimate (in story points) a large number of user stories.
• Product backlog is provided by the product owner
• Team members are expected to size each item relative to other items
on the wall considering the effort involved in implementation
• Stories are arranged horizontally
Story of user story
Thank you

More Related Content

What's hot

User Story Workshop
User Story WorkshopUser Story Workshop
User Story WorkshopPeter Antman
 
How to Break the Requirements into User Stories
How to Break the Requirements into User StoriesHow to Break the Requirements into User Stories
How to Break the Requirements into User StoriesShriKant Vashishtha
 
Workshop - Writing Good User Stories
Workshop - Writing Good User Stories Workshop - Writing Good User Stories
Workshop - Writing Good User Stories Easy Agile
 
Agile User Stories
Agile User StoriesAgile User Stories
Agile User Storieskahgeh75
 
Strategies to split user stories
Strategies to split user storiesStrategies to split user stories
Strategies to split user storiescpolc
 
Product Backlog - Refinement and Prioritization Techniques
Product Backlog - Refinement and Prioritization TechniquesProduct Backlog - Refinement and Prioritization Techniques
Product Backlog - Refinement and Prioritization TechniquesVikash Karuna
 
User story splitting techniques
User story splitting techniquesUser story splitting techniques
User story splitting techniquesAshutosh Rai
 
Invest In Good User Stories
Invest In Good User StoriesInvest In Good User Stories
Invest In Good User StoriesCraig Brown
 
IIT Academy: 204 User stories and acceptance criteria
IIT Academy: 204 User stories and acceptance criteriaIIT Academy: 204 User stories and acceptance criteria
IIT Academy: 204 User stories and acceptance criteriaSteven HK Ma | 馬國豪
 
User story and splitting workshop
User story and splitting workshopUser story and splitting workshop
User story and splitting workshopBrian Sjoberg
 
User Story Splitting
User Story SplittingUser Story Splitting
User Story Splittingtrishly
 
Agile stories, estimating and planning
Agile stories, estimating and planningAgile stories, estimating and planning
Agile stories, estimating and planningDimitri Ponomareff
 

What's hot (20)

User Story Workshop
User Story WorkshopUser Story Workshop
User Story Workshop
 
How to Break the Requirements into User Stories
How to Break the Requirements into User StoriesHow to Break the Requirements into User Stories
How to Break the Requirements into User Stories
 
Effective user stories for your agile or Scrum team
Effective user stories for your agile or Scrum teamEffective user stories for your agile or Scrum team
Effective user stories for your agile or Scrum team
 
Workshop - Writing Good User Stories
Workshop - Writing Good User Stories Workshop - Writing Good User Stories
Workshop - Writing Good User Stories
 
Agile User Stories
Agile User StoriesAgile User Stories
Agile User Stories
 
Strategies to split user stories
Strategies to split user storiesStrategies to split user stories
Strategies to split user stories
 
User Stories
User StoriesUser Stories
User Stories
 
Epics and User Stories
Epics and User StoriesEpics and User Stories
Epics and User Stories
 
Scrum - Product Backlog
Scrum - Product BacklogScrum - Product Backlog
Scrum - Product Backlog
 
Product Backlog - Refinement and Prioritization Techniques
Product Backlog - Refinement and Prioritization TechniquesProduct Backlog - Refinement and Prioritization Techniques
Product Backlog - Refinement and Prioritization Techniques
 
User story splitting techniques
User story splitting techniquesUser story splitting techniques
User story splitting techniques
 
Invest In Good User Stories
Invest In Good User StoriesInvest In Good User Stories
Invest In Good User Stories
 
Product Backlog Management
Product Backlog ManagementProduct Backlog Management
Product Backlog Management
 
User Stories Fundamentals
User Stories FundamentalsUser Stories Fundamentals
User Stories Fundamentals
 
Agile Scrum Estimation
Agile   Scrum EstimationAgile   Scrum Estimation
Agile Scrum Estimation
 
IIT Academy: 204 User stories and acceptance criteria
IIT Academy: 204 User stories and acceptance criteriaIIT Academy: 204 User stories and acceptance criteria
IIT Academy: 204 User stories and acceptance criteria
 
User story and splitting workshop
User story and splitting workshopUser story and splitting workshop
User story and splitting workshop
 
User Story Splitting
User Story SplittingUser Story Splitting
User Story Splitting
 
User Story
User StoryUser Story
User Story
 
Agile stories, estimating and planning
Agile stories, estimating and planningAgile stories, estimating and planning
Agile stories, estimating and planning
 

Similar to Story of user story

Agile development and project management
Agile development and project managementAgile development and project management
Agile development and project managementVishal Bardoloi
 
Agile Network India | Effective User story writing and story mapping approach...
Agile Network India | Effective User story writing and story mapping approach...Agile Network India | Effective User story writing and story mapping approach...
Agile Network India | Effective User story writing and story mapping approach...AgileNetwork
 
Agile Network India | Effective User story writing and story mapping approach...
Agile Network India | Effective User story writing and story mapping approach...Agile Network India | Effective User story writing and story mapping approach...
Agile Network India | Effective User story writing and story mapping approach...AgileNetwork
 
Untangling Agile Estimation - PMI Houston 2019 Symposium
Untangling Agile Estimation - PMI Houston 2019 SymposiumUntangling Agile Estimation - PMI Houston 2019 Symposium
Untangling Agile Estimation - PMI Houston 2019 SymposiumJami Anderson
 
Agile Network India | Effective User story writing and story mapping approach
Agile Network India | Effective User story writing and story mapping approachAgile Network India | Effective User story writing and story mapping approach
Agile Network India | Effective User story writing and story mapping approachAgileNetwork
 
User Story Writing & Estimation For Testers By Mahesh Varadharajan
User Story Writing & Estimation For Testers By Mahesh VaradharajanUser Story Writing & Estimation For Testers By Mahesh Varadharajan
User Story Writing & Estimation For Testers By Mahesh VaradharajanAgile Testing Alliance
 
7-Epic, Story and Bug Reporting(updated).pptx
7-Epic, Story and Bug Reporting(updated).pptx7-Epic, Story and Bug Reporting(updated).pptx
7-Epic, Story and Bug Reporting(updated).pptxBishalKarki33
 
Agile.pptx
Agile.pptxAgile.pptx
Agile.pptxRafeeq T
 
Agile User Stories
Agile User StoriesAgile User Stories
Agile User StoriesSunil-QA
 
Agile for product owners v12
Agile for product owners  v12Agile for product owners  v12
Agile for product owners v12Ravi Tadwalkar
 
Agile User Stories
Agile  User StoriesAgile  User Stories
Agile User StoriesSunil-QA
 
Agile - User Stories
Agile - User StoriesAgile - User Stories
Agile - User StoriesSunil-QA
 
Agile Education: PO Basics
Agile Education: PO BasicsAgile Education: PO Basics
Agile Education: PO BasicsBharti Rupani
 
Software Product Engineering
Software Product EngineeringSoftware Product Engineering
Software Product EngineeringSagittarius
 
Acceptance criteria
Acceptance criteriaAcceptance criteria
Acceptance criteriaDataArt
 
Successful Business Sponsorship of Agile IT Projects
Successful Business Sponsorship of Agile IT ProjectsSuccessful Business Sponsorship of Agile IT Projects
Successful Business Sponsorship of Agile IT ProjectsChris Mundy
 

Similar to Story of user story (20)

Agile development and project management
Agile development and project managementAgile development and project management
Agile development and project management
 
Agile Network India | Effective User story writing and story mapping approach...
Agile Network India | Effective User story writing and story mapping approach...Agile Network India | Effective User story writing and story mapping approach...
Agile Network India | Effective User story writing and story mapping approach...
 
Agile Network India | Effective User story writing and story mapping approach...
Agile Network India | Effective User story writing and story mapping approach...Agile Network India | Effective User story writing and story mapping approach...
Agile Network India | Effective User story writing and story mapping approach...
 
Untangling Agile Estimation - PMI Houston 2019 Symposium
Untangling Agile Estimation - PMI Houston 2019 SymposiumUntangling Agile Estimation - PMI Houston 2019 Symposium
Untangling Agile Estimation - PMI Houston 2019 Symposium
 
Agile Network India | Effective User story writing and story mapping approach
Agile Network India | Effective User story writing and story mapping approachAgile Network India | Effective User story writing and story mapping approach
Agile Network India | Effective User story writing and story mapping approach
 
User Story Writing & Estimation For Testers By Mahesh Varadharajan
User Story Writing & Estimation For Testers By Mahesh VaradharajanUser Story Writing & Estimation For Testers By Mahesh Varadharajan
User Story Writing & Estimation For Testers By Mahesh Varadharajan
 
Story Cards
Story CardsStory Cards
Story Cards
 
The Scrum Guide
The Scrum GuideThe Scrum Guide
The Scrum Guide
 
User Stories Training
User Stories TrainingUser Stories Training
User Stories Training
 
7-Epic, Story and Bug Reporting(updated).pptx
7-Epic, Story and Bug Reporting(updated).pptx7-Epic, Story and Bug Reporting(updated).pptx
7-Epic, Story and Bug Reporting(updated).pptx
 
Agile.pptx
Agile.pptxAgile.pptx
Agile.pptx
 
Defining tasks for User Stories
Defining tasks for User StoriesDefining tasks for User Stories
Defining tasks for User Stories
 
Agile User Stories
Agile User StoriesAgile User Stories
Agile User Stories
 
Agile for product owners v12
Agile for product owners  v12Agile for product owners  v12
Agile for product owners v12
 
Agile User Stories
Agile  User StoriesAgile  User Stories
Agile User Stories
 
Agile - User Stories
Agile - User StoriesAgile - User Stories
Agile - User Stories
 
Agile Education: PO Basics
Agile Education: PO BasicsAgile Education: PO Basics
Agile Education: PO Basics
 
Software Product Engineering
Software Product EngineeringSoftware Product Engineering
Software Product Engineering
 
Acceptance criteria
Acceptance criteriaAcceptance criteria
Acceptance criteria
 
Successful Business Sponsorship of Agile IT Projects
Successful Business Sponsorship of Agile IT ProjectsSuccessful Business Sponsorship of Agile IT Projects
Successful Business Sponsorship of Agile IT Projects
 

More from Balaji Sathram

Coaching stance and icf core competencies
Coaching stance and icf core competenciesCoaching stance and icf core competencies
Coaching stance and icf core competenciesBalaji Sathram
 
Agile practices: start with "WHY"
Agile practices: start with "WHY"Agile practices: start with "WHY"
Agile practices: start with "WHY"Balaji Sathram
 
Agile ceremonies in detail ipo
Agile ceremonies in detail ipoAgile ceremonies in detail ipo
Agile ceremonies in detail ipoBalaji Sathram
 
Scrum master challenges
Scrum master challengesScrum master challenges
Scrum master challengesBalaji Sathram
 
Change management models
Change management modelsChange management models
Change management modelsBalaji Sathram
 
Coaching Basics and Coaching Models
Coaching Basics and Coaching ModelsCoaching Basics and Coaching Models
Coaching Basics and Coaching ModelsBalaji Sathram
 
Team Coaching - Starbursting
Team Coaching - StarburstingTeam Coaching - Starbursting
Team Coaching - StarburstingBalaji Sathram
 
Team Coaching - Sprint Retrospection
Team Coaching - Sprint RetrospectionTeam Coaching - Sprint Retrospection
Team Coaching - Sprint RetrospectionBalaji Sathram
 
Team coaching-behavioral basics
Team coaching-behavioral basicsTeam coaching-behavioral basics
Team coaching-behavioral basicsBalaji Sathram
 
Lean Software Development: Values and Principles
Lean Software Development: Values and PrinciplesLean Software Development: Values and Principles
Lean Software Development: Values and PrinciplesBalaji Sathram
 
Agile-overview: Agile Manifesto, Agile principles and Agile Methodologies
Agile-overview: Agile Manifesto, Agile principles and Agile MethodologiesAgile-overview: Agile Manifesto, Agile principles and Agile Methodologies
Agile-overview: Agile Manifesto, Agile principles and Agile MethodologiesBalaji Sathram
 

More from Balaji Sathram (16)

Thinking questions
Thinking questionsThinking questions
Thinking questions
 
Coaching stance and icf core competencies
Coaching stance and icf core competenciesCoaching stance and icf core competencies
Coaching stance and icf core competencies
 
Agile practices: start with "WHY"
Agile practices: start with "WHY"Agile practices: start with "WHY"
Agile practices: start with "WHY"
 
Agile ceremonies in detail ipo
Agile ceremonies in detail ipoAgile ceremonies in detail ipo
Agile ceremonies in detail ipo
 
Scrum master challenges
Scrum master challengesScrum master challenges
Scrum master challenges
 
Change management models
Change management modelsChange management models
Change management models
 
Coaching Basics and Coaching Models
Coaching Basics and Coaching ModelsCoaching Basics and Coaching Models
Coaching Basics and Coaching Models
 
Team Facilitator
Team FacilitatorTeam Facilitator
Team Facilitator
 
Coaching Leadership
Coaching LeadershipCoaching Leadership
Coaching Leadership
 
Team Coaching - Starbursting
Team Coaching - StarburstingTeam Coaching - Starbursting
Team Coaching - Starbursting
 
Team Coaching - Sprint Retrospection
Team Coaching - Sprint RetrospectionTeam Coaching - Sprint Retrospection
Team Coaching - Sprint Retrospection
 
NLP in Team Coaching
NLP in Team CoachingNLP in Team Coaching
NLP in Team Coaching
 
Team coaching-behavioral basics
Team coaching-behavioral basicsTeam coaching-behavioral basics
Team coaching-behavioral basics
 
Lean Software Development: Values and Principles
Lean Software Development: Values and PrinciplesLean Software Development: Values and Principles
Lean Software Development: Values and Principles
 
Scrum
ScrumScrum
Scrum
 
Agile-overview: Agile Manifesto, Agile principles and Agile Methodologies
Agile-overview: Agile Manifesto, Agile principles and Agile MethodologiesAgile-overview: Agile Manifesto, Agile principles and Agile Methodologies
Agile-overview: Agile Manifesto, Agile principles and Agile Methodologies
 

Recently uploaded

An Important Step Toward Process Improvement
An Important Step Toward Process ImprovementAn Important Step Toward Process Improvement
An Important Step Toward Process ImprovementCIToolkit
 
ANIn Coimbatore March 2024 | Agile & AI in Project Management by Dhilipkumar ...
ANIn Coimbatore March 2024 | Agile & AI in Project Management by Dhilipkumar ...ANIn Coimbatore March 2024 | Agile & AI in Project Management by Dhilipkumar ...
ANIn Coimbatore March 2024 | Agile & AI in Project Management by Dhilipkumar ...AgileNetwork
 
Empowering Resilience & Strategic Growth: Insights for Emerging Leaders
Empowering Resilience & Strategic Growth: Insights for Emerging LeadersEmpowering Resilience & Strategic Growth: Insights for Emerging Leaders
Empowering Resilience & Strategic Growth: Insights for Emerging LeadersMahmoud Rabie
 
Test_document_upload_SQL_minimum_fourteen
Test_document_upload_SQL_minimum_fourteenTest_document_upload_SQL_minimum_fourteen
Test_document_upload_SQL_minimum_fourteenolgaz9
 
Forget Fiverr : Fractional Employment the ins and outs
Forget Fiverr : Fractional Employment the ins and outsForget Fiverr : Fractional Employment the ins and outs
Forget Fiverr : Fractional Employment the ins and outsStephan Koning
 
HR for Non HR_Learning and Development.
HR for Non HR_Learning  and Development.HR for Non HR_Learning  and Development.
HR for Non HR_Learning and Development.azischin
 
Applying the PDCA Cycle: A Blueprint for Continuous Improvement
Applying the PDCA Cycle: A Blueprint for Continuous ImprovementApplying the PDCA Cycle: A Blueprint for Continuous Improvement
Applying the PDCA Cycle: A Blueprint for Continuous ImprovementCIToolkit
 
What is 5S principles of trainers for training institutions.pdf
What is 5S principles of trainers for training institutions.pdfWhat is 5S principles of trainers for training institutions.pdf
What is 5S principles of trainers for training institutions.pdfBALASUNDARESAN M
 
Roadway to GDSC- Session 1 Powerpoint Presentation
Roadway to GDSC- Session 1 Powerpoint PresentationRoadway to GDSC- Session 1 Powerpoint Presentation
Roadway to GDSC- Session 1 Powerpoint Presentationgdscghrcem
 
Organizations in a Future with Generative AI
Organizations in a Future with Generative AIOrganizations in a Future with Generative AI
Organizations in a Future with Generative AIKye Andersson
 
Making Sense of Multiple Ideas with Affinity Diagrams
Making Sense of Multiple Ideas with Affinity DiagramsMaking Sense of Multiple Ideas with Affinity Diagrams
Making Sense of Multiple Ideas with Affinity DiagramsCIToolkit
 
A3 Thinking: A Structured Approach to Problem Solving
A3 Thinking: A Structured Approach to Problem SolvingA3 Thinking: A Structured Approach to Problem Solving
A3 Thinking: A Structured Approach to Problem SolvingCIToolkit
 
Analyzing and Monitoring Processes through Time Value Mapping
Analyzing and Monitoring Processes through Time Value MappingAnalyzing and Monitoring Processes through Time Value Mapping
Analyzing and Monitoring Processes through Time Value MappingCIToolkit
 
Tackling Fake Agility w/ Johanna Rothman
Tackling Fake Agility w/ Johanna RothmanTackling Fake Agility w/ Johanna Rothman
Tackling Fake Agility w/ Johanna RothmanStefan Wolpers
 
Value Stream Map: A Visual Approach to Process Optimization
Value Stream Map: A Visual Approach to Process OptimizationValue Stream Map: A Visual Approach to Process Optimization
Value Stream Map: A Visual Approach to Process OptimizationCIToolkit
 
The Role of Fishbone Diagram in Analyzing Cause and Effect
The Role of Fishbone Diagram in Analyzing Cause and EffectThe Role of Fishbone Diagram in Analyzing Cause and Effect
The Role of Fishbone Diagram in Analyzing Cause and EffectCIToolkit
 
How the Heck do you Teach Level Design? Educating in the Studio
How the Heck do you Teach Level Design? Educating in the StudioHow the Heck do you Teach Level Design? Educating in the Studio
How the Heck do you Teach Level Design? Educating in the StudioChristopher Totten
 
From Command Line to Reporting Line: The Diary of a First-Time EM
From Command Line to Reporting Line: The Diary of a First-Time EMFrom Command Line to Reporting Line: The Diary of a First-Time EM
From Command Line to Reporting Line: The Diary of a First-Time EMGloria Chow
 
Performance Management Notes for MBA Students
Performance Management Notes for MBA StudentsPerformance Management Notes for MBA Students
Performance Management Notes for MBA StudentsManickam Gajapathy
 

Recently uploaded (20)

An Important Step Toward Process Improvement
An Important Step Toward Process ImprovementAn Important Step Toward Process Improvement
An Important Step Toward Process Improvement
 
ANIn Coimbatore March 2024 | Agile & AI in Project Management by Dhilipkumar ...
ANIn Coimbatore March 2024 | Agile & AI in Project Management by Dhilipkumar ...ANIn Coimbatore March 2024 | Agile & AI in Project Management by Dhilipkumar ...
ANIn Coimbatore March 2024 | Agile & AI in Project Management by Dhilipkumar ...
 
Empowering Resilience & Strategic Growth: Insights for Emerging Leaders
Empowering Resilience & Strategic Growth: Insights for Emerging LeadersEmpowering Resilience & Strategic Growth: Insights for Emerging Leaders
Empowering Resilience & Strategic Growth: Insights for Emerging Leaders
 
Test_document_upload_SQL_minimum_fourteen
Test_document_upload_SQL_minimum_fourteenTest_document_upload_SQL_minimum_fourteen
Test_document_upload_SQL_minimum_fourteen
 
Forget Fiverr : Fractional Employment the ins and outs
Forget Fiverr : Fractional Employment the ins and outsForget Fiverr : Fractional Employment the ins and outs
Forget Fiverr : Fractional Employment the ins and outs
 
HR for Non HR_Learning and Development.
HR for Non HR_Learning  and Development.HR for Non HR_Learning  and Development.
HR for Non HR_Learning and Development.
 
Applying the PDCA Cycle: A Blueprint for Continuous Improvement
Applying the PDCA Cycle: A Blueprint for Continuous ImprovementApplying the PDCA Cycle: A Blueprint for Continuous Improvement
Applying the PDCA Cycle: A Blueprint for Continuous Improvement
 
What is 5S principles of trainers for training institutions.pdf
What is 5S principles of trainers for training institutions.pdfWhat is 5S principles of trainers for training institutions.pdf
What is 5S principles of trainers for training institutions.pdf
 
Roadway to GDSC- Session 1 Powerpoint Presentation
Roadway to GDSC- Session 1 Powerpoint PresentationRoadway to GDSC- Session 1 Powerpoint Presentation
Roadway to GDSC- Session 1 Powerpoint Presentation
 
Organizations in a Future with Generative AI
Organizations in a Future with Generative AIOrganizations in a Future with Generative AI
Organizations in a Future with Generative AI
 
Making Sense of Multiple Ideas with Affinity Diagrams
Making Sense of Multiple Ideas with Affinity DiagramsMaking Sense of Multiple Ideas with Affinity Diagrams
Making Sense of Multiple Ideas with Affinity Diagrams
 
A3 Thinking: A Structured Approach to Problem Solving
A3 Thinking: A Structured Approach to Problem SolvingA3 Thinking: A Structured Approach to Problem Solving
A3 Thinking: A Structured Approach to Problem Solving
 
Analyzing and Monitoring Processes through Time Value Mapping
Analyzing and Monitoring Processes through Time Value MappingAnalyzing and Monitoring Processes through Time Value Mapping
Analyzing and Monitoring Processes through Time Value Mapping
 
Tackling Fake Agility w/ Johanna Rothman
Tackling Fake Agility w/ Johanna RothmanTackling Fake Agility w/ Johanna Rothman
Tackling Fake Agility w/ Johanna Rothman
 
Value Stream Map: A Visual Approach to Process Optimization
Value Stream Map: A Visual Approach to Process OptimizationValue Stream Map: A Visual Approach to Process Optimization
Value Stream Map: A Visual Approach to Process Optimization
 
The Role of Fishbone Diagram in Analyzing Cause and Effect
The Role of Fishbone Diagram in Analyzing Cause and EffectThe Role of Fishbone Diagram in Analyzing Cause and Effect
The Role of Fishbone Diagram in Analyzing Cause and Effect
 
How the Heck do you Teach Level Design? Educating in the Studio
How the Heck do you Teach Level Design? Educating in the StudioHow the Heck do you Teach Level Design? Educating in the Studio
How the Heck do you Teach Level Design? Educating in the Studio
 
From Command Line to Reporting Line: The Diary of a First-Time EM
From Command Line to Reporting Line: The Diary of a First-Time EMFrom Command Line to Reporting Line: The Diary of a First-Time EM
From Command Line to Reporting Line: The Diary of a First-Time EM
 
Performance Management Notes for MBA Students
Performance Management Notes for MBA StudentsPerformance Management Notes for MBA Students
Performance Management Notes for MBA Students
 
Capacity2 - Briefing and Facilitation training slides
Capacity2 - Briefing and Facilitation training slidesCapacity2 - Briefing and Facilitation training slides
Capacity2 - Briefing and Facilitation training slides
 

Story of user story

  • 1. Story of User Story Balaji Sathram, CSP, PMI-ACP. Scrum master, Sabre.
  • 2. Agenda • User Story-History • User Story - Brief • User Story-Templates • Writing good user stories • Slicing user stories • To maintain good user stories • Additional Terms • User Story - Prioritization • User Story - Estimation
  • 3. User Story-History • Comes from XP (eXtreme Programming) • 1999: Kent Beck coined the term user stories in Extreme Programming Explained 1st Edition • Documenting requirements to Explaining (Tell story about what you want): Building a common and shared understanding. • People started following it. But The sad part of the whole episode is: instead of telling stories, people started writing stories. • Organizations started documenting user stories: "shared documents are not shared understanding"
  • 4. User Story - Brief What is User Story: • A concise written description of a piece of functionality that will be valuable to a user (or product owner) of the software. • All about the user’s goals • Carries the value stream to the user • It contains: • Value: Requirement of a customer • Cost: an understanding of what it takes to build • Validation: that you understand what is happening
  • 5. User Story-Templates As a <WHO|ROLE> I want <WHAT|FEATURE> So that <WHY|PURPOSE> OR Given [context] When [event] Then [outcome]
  • 7. XP Stories – Ron Jeffries – 3Cs • In 2001 • Card: Write stories on a card. Just enough to identify the requirement. • Conversation: Most of the requirement is communicated through a conversation. Information can be stored elsewhere. The story is a holder for these. • Confirmation: “How will we know we’ve done that.” We also need an acceptance test.
  • 8. User Story Description • It is written down on a note card (e.g. 3x5 inches or 8x13 cm) • Start with a title. • Add a concise description using the templates. • Add other relevant notes, specifications, or sketches • Before building software write acceptance criteria (how do we know when we’re done?)
  • 9. Writing good user stories • Independent – User Stories should be as independent as possible. • Negotiable – A User Story is not a contract. It is not a detailed specification. Story cards are short descriptions of functionality, the details of which are to be negotiated in a conversation between the customer and the development team • Valuable – User Stories should be valuable to the user (or owner) of the solution. They should be written in user language. They should be features, not tasks. • Estimable – User Stories need to be possible to estimate. They need to provide enough information to estimate, without being too detailed. • Small – User Stories should be small. Not too small and not too big. DONE in one iteration • Testable – User Stories need to be worded in a way that is testable, i.e. not too subjective and to provide clear details of how the User Story will be tested. if you can’t test it, you don’t know when you are done
  • 10. Slicing user stories • Breaking them down
  • 11. Slicing User Stories • Split by workflow steps • Split by business rules • Split by happy/unhappy flow • Split by input options / platform • Split by test data or data types or parameters • Split by operations(CRUD) • Split by test scenarios/test case • Split by Roles • Split by external dependencies • Split based on Mock/Real services • Split based on acceptance criteria • Split based on Usability
  • 12. Some Additional Useful Terms • Definition of Ready • Definition of Done • Acceptance Criteria • Theme and Epic
  • 13. Definition of Ready From Team to Product Owner • No Open questions • Test data collected • No technical dependencies • Workflow figured out • Acceptance criteria understood • Estimated • Has some business value • Sized appropriately
  • 14. Definition of Done From Team to the Team • Architectural Review Complete • Code Review Complete • Unit Tested • Test Scenarios Review with BA/PO/Team members • QA tested • PO/BA Acceptance • No Priority 1 or Priority 2 bugs • Integration • Known deployment & Rollback plan
  • 15. Acceptance Criteria From Product Owner to the Team • Agreement between the team and the PO on when the story is accepted
  • 18. Prioritization • High-Medium-Low • MoSCoW • Kano Analysis • 1-2-3-4-5 • Stacked Ranking • Impact Analysis
  • 19. MoSCoW • A method to prioritize requirements popularized in the DSDM (Dynamic systems development method) community is MoSCoW • Must Have, Should Have, Could Have and Won’t Have
  • 20. Kano Analysis • Kano Analysis is a quality measurement tool used to prioritize customer requirements based on their impact to customer satisfaction. According to the Kano Model (developed by Dr Noriaki Kano in the 1980s), a product or service can have three types of attribute (or property): • Musts: Which customers expect to be present in a product. • Satisfiers: Which are not absolutely necessary, but which are known about and increase the customer's enjoyment of the product. • Delighters: Which customers don't even know they want, but are delighted when they find them.
  • 21. Impact Analysis • For every user story, give impact points based on below questions • What is the impact it is creating if it is implemented • What is the impact it is creating if it is not implemented • Multiply both the values which will result in impact score for the user story • Higher the score higher the impact
  • 24. User Story - What do we Estimate? Complexity Uncertainty Effort
  • 25. Story Points • Story Points are the unit of measurement for expressing the overall size of a user story, feature, or other piece of work. • The number of story points associated with a story represents the overall size of the story. • Either Doubles OR Fibonacci Series Non Linear Scale - Fibonacci Series [1,2,3,5, and 8] Non Linear Scale - Doubles [1,2,4, and 8]
  • 26. Estimation Techniques • Agile Relative Sizing • Ideal Days • Planning Poker • Wideband Delphi • Affinity Estimating
  • 28. Ideal Days How long something would take if • It’s all you worked on • you had no interruptions • and everything you need is available Factors Affecting Ideal Time: Training, Email, Reviews, Interviewing, Demonstrations, Meetings, Sick Time, Phone, Bug Fixing, Management review
  • 29. Planning Poker An iterative approach to estimating Steps: • Each estimator is given a deck of cards, each card has a valid estimate written on it • Customer/product owner reads a story and it’s discussed briefly • Each estimator selects a card that’s his or her estimate • Cards are turned over so all can see them • Discuss differences (especially outliers) • Re-estimate until estimates converge
  • 30. Wideband Delphi Is a process that the team can use to generate an estimate Process: • Choose the team • Kick off meeting • Individual preparation • Estimation session • Assemble tasks • Review results
  • 31. Affinity Estimation (Lowell Lindstrom) Affinity estimating is a technique many teams use to quickly and easily estimate (in story points) a large number of user stories. • Product backlog is provided by the product owner • Team members are expected to size each item relative to other items on the wall considering the effort involved in implementation • Stories are arranged horizontally