Ways to split user stories
•Download as ODP, PDF•
2 likes•598 views
What makes a good user story and several ways to split them in order to fit in sprints and make sense.
Report
Share
Report
Share
Recommended
User Story Splitting
This document discusses techniques for splitting large user stories into smaller stories for an agile team. It provides examples of splitting stories by workflow, business rules, operations, data, performance, and interface. Some key techniques include focusing first on the happy path, starting with foundational capabilities like create/read, prioritizing the most important rules, and keeping the interface simple initially. Splitting stories properly allows teams to learn, adapt, and deliver working functionality in short iterations.
Acceptance criteria
Acceptance criteria define specific, measurable conditions that must be met for a user story or feature to be accepted. They help ensure stakeholders have a shared understanding of what needs to be delivered before development begins. Good acceptance criteria are independent of implementation, written from the user perspective, and use a format like Given, When, Then. They describe what is expected rather than how it will be implemented. Acceptance criteria should be defined before development starts to guide testing and determine when a user story is complete.
Quality tracking through JIRA
JIRA is great issue tracking tool through which quality process can be tracked within a given environment.
Failure Mode & Effect Analysis
Introduction of FMEA; Definition, Activities, important terms, factors, RPN; Process of FMEA; Steps of FMEA
Types of FMEA; FMEA Application; FMEA Related Tools:
Root Cause Analysis, Pareto Chart, Cause Effect Diagram
Mistake proofing for web
This document provides an overview of the concept of Poka-Yoke, which refers to mistake-proofing methods used for zero defect quality. It discusses key topics around Poka-Yoke including the introduction and purpose of Poka-Yoke, the three qualifiers of Poka-Yoke being simple/inexpensive, 100% inspection, and immediate feedback. It also covers different methods for implementing Poka-Yoke such as contact, counting, and motion-sequence methods as well as examples of Poka-Yoke systems and sensing devices. The overall document aims to explain the strategy and principles of using Poka-Yoke for performance excellence and zero errors.
Non confirming product according to food Authority
I’ve worked in Industry for many years, and I understand the pressures and difficulties associated with bringing and keeping a product on the market. I have done post market and compliance work at the FA. So, I understand the agency’s stance on safety and effectiveness. I hope to bring you a balanced perspective to my discussion on non-conformances and non-conforming product.
Contact:
nomanaleemft@gmail.com
00923084089243
defect tracking and management
The document discusses defect tracking and management. It provides details on defect identification, reporting, tracking, resolution and using defect information to improve processes. A recommended structure is given for defect reports, including title, description, steps to reproduce, actual and expected results. Examples of a defect report and tracking sheet in Excel are also shown. The defect management process involves executing tests, logging discrepancies, reviewing with developers, assigning defects, retesting after fixes, and closing defects when resolved.
An Introduction to kanban
Kanban is a visual project management system originally used in Toyota's manufacturing process. It uses cards or images on a board to visualize workflow from one stage to the next and limit work-in-progress to avoid bottlenecks and focus on continuous flow. The core principles are to visualize workflow, limit WIP, focus on flow, and drive continuous improvement. Kanban and Scrum are both agile methods but Kanban allows continuous workflow while Scrum uses sprints and fixed roles. Key benefits of Kanban include improved visibility, collaboration, and productivity through waste reduction.
Recommended
User Story Splitting
This document discusses techniques for splitting large user stories into smaller stories for an agile team. It provides examples of splitting stories by workflow, business rules, operations, data, performance, and interface. Some key techniques include focusing first on the happy path, starting with foundational capabilities like create/read, prioritizing the most important rules, and keeping the interface simple initially. Splitting stories properly allows teams to learn, adapt, and deliver working functionality in short iterations.
Acceptance criteria
Acceptance criteria define specific, measurable conditions that must be met for a user story or feature to be accepted. They help ensure stakeholders have a shared understanding of what needs to be delivered before development begins. Good acceptance criteria are independent of implementation, written from the user perspective, and use a format like Given, When, Then. They describe what is expected rather than how it will be implemented. Acceptance criteria should be defined before development starts to guide testing and determine when a user story is complete.
Quality tracking through JIRA
JIRA is great issue tracking tool through which quality process can be tracked within a given environment.
Failure Mode & Effect Analysis
Introduction of FMEA; Definition, Activities, important terms, factors, RPN; Process of FMEA; Steps of FMEA
Types of FMEA; FMEA Application; FMEA Related Tools:
Root Cause Analysis, Pareto Chart, Cause Effect Diagram
Mistake proofing for web
This document provides an overview of the concept of Poka-Yoke, which refers to mistake-proofing methods used for zero defect quality. It discusses key topics around Poka-Yoke including the introduction and purpose of Poka-Yoke, the three qualifiers of Poka-Yoke being simple/inexpensive, 100% inspection, and immediate feedback. It also covers different methods for implementing Poka-Yoke such as contact, counting, and motion-sequence methods as well as examples of Poka-Yoke systems and sensing devices. The overall document aims to explain the strategy and principles of using Poka-Yoke for performance excellence and zero errors.
Non confirming product according to food Authority
I’ve worked in Industry for many years, and I understand the pressures and difficulties associated with bringing and keeping a product on the market. I have done post market and compliance work at the FA. So, I understand the agency’s stance on safety and effectiveness. I hope to bring you a balanced perspective to my discussion on non-conformances and non-conforming product.
Contact:
nomanaleemft@gmail.com
00923084089243
defect tracking and management
The document discusses defect tracking and management. It provides details on defect identification, reporting, tracking, resolution and using defect information to improve processes. A recommended structure is given for defect reports, including title, description, steps to reproduce, actual and expected results. Examples of a defect report and tracking sheet in Excel are also shown. The defect management process involves executing tests, logging discrepancies, reviewing with developers, assigning defects, retesting after fixes, and closing defects when resolved.
An Introduction to kanban
Kanban is a visual project management system originally used in Toyota's manufacturing process. It uses cards or images on a board to visualize workflow from one stage to the next and limit work-in-progress to avoid bottlenecks and focus on continuous flow. The core principles are to visualize workflow, limit WIP, focus on flow, and drive continuous improvement. Kanban and Scrum are both agile methods but Kanban allows continuous workflow while Scrum uses sprints and fixed roles. Key benefits of Kanban include improved visibility, collaboration, and productivity through waste reduction.
SMART Requirements
The document discusses developing requirements that are SMART (Specific, Measurable, Attainable, Realistic, Time-Bound). It provides examples of weak requirements and improved versions that are SMART. Developing SMART requirements leads to budget/schedule benefits, quicker consensus, and less rework. Each element of SMART is defined, with clear descriptions and additional examples contrasting poor versus improved requirements.
Insight on Non Conformity in food industry- Benefits, Types, Process Flow for...
Insight on Non Conformity in food industry- Benefits, Types, Process Flow for...PMG Engineering Private Limited
The importance of quality and food safety cannot be neglected in the present business scenario
due to extreme competition in open market. Many food industrialists have understood the
importance of implementation of system that can eliminate non- conformance products, as these
may help the company in preventing negative consequences like economical losses and helps to
protect the reputation of brand. The design of food safety management system for managing
non- conformance in industry may either support or hinder the effectiveness of continuous
improvement policy.
A non-conformance is involved when a process or a system failsto comply with the rules or meet
the required specifications of an audit standard(ISO 22000, IRC, BRC, SQC etc.). A requirement is a need, expectation, or obligation. It can be stated or implied by an organization, its customers,
or other interested parties. There are many types of requirements. Some of these include food
safety requirements, quality requirements, process requirements, product requirements,
customer requirements, management systems requirements, and legal requirements. Whenever
your organization fails to meet one of these requirements, a nonconformity occurs, and it mostly
occurs in the production and manufacturing processes like Supply chain management, inventory,
and material management process etc. It mainly asks for a rework which requires the
involvement of various personnel from the respective departments.Kanban
This presentation is an introduction to Kanban. It should help teams understand what Kanban is, its principles and how to implement it.
Human Error Prevention
Find the way to prevent the human error in industries as well as 16 types of human errors for better identification and generating solution for given identified errors
Manufacturing Excellence - Visual Factory
Visual Factory is a concept focused on the visual perception.
Purpose = replace texts by communicating via “visual signals”:
- in work instructions and checklists (pictures of the equipment with control points)
- with local signage: tags, labels (what to measure, range, …), pictures
Benefits:
- quick and easy instructions
- reductions in injuries and strain
- increased efficiency and reactivity
- reduction of the variability and the non-conformity rate
- decreased training time…
PPT ON VISUAL FACTORY
The document discusses the benefits of meditation for reducing stress and anxiety. Regular meditation practice can help calm the mind and body by lowering heart rate and blood pressure. Studies have shown that meditating for just 10-20 minutes per day can have significant positive impacts on both mental and physical health over time.
Human Error Prevention
How can we prevent accidents caused by human error? This presentation deals with typical examples of severe accidents related to human errors, and shows methods to prevent them.
Technical stories v1.2
This document discusses technical stories and architecture work in agile software development. It defines technical stories as stories that focus on technical goals rather than user goals. It discusses why technical stories are important for managing technical debt, architecture, and educating the technical team. It provides examples of technical stories and best practices for writing, accepting, and tracking them. The document also discusses architecture, why it is important, and how to plan architecture work through technical stories, architectural runways, and feedback loops.
Class 11 - MAINTENANCE PLANNING AND SCHEDULING_Dr.Adel_.ppt
The document discusses maintenance planning and scheduling. It describes the objectives of planning and scheduling as minimizing idle time, maximizing efficient use of resources, and maintaining operating equipment. Planning involves determining job requirements in advance while scheduling matches jobs to resources over time. The document outlines classification of maintenance work, planning procedures and levels, and techniques for developing long, medium, and short-range schedules.
Test plan
This document provides a template for a test plan that includes sections for test plan identification, references, introduction/scope, test items, risks, features to be tested, approach/strategy, pass/fail criteria, deliverables, schedule, responsibilities, and approvals. The template can be used to create a test plan that outlines what will be tested, how it will be tested, and manages the test process.
Unit 9 implementing the reliability strategy
This document discusses implementing reliability strategies and engineering. It begins by explaining the importance of reliability in fields like aviation, defense, and energy where failure could lead to dangerous situations. It then discusses mechanical reliability and common failure modes. Reliability engineering is introduced as the study of reliability and life-cycle management. Several high-profile system failures are listed to emphasize the need for reliability in design. The document outlines various areas of reliability engineering and provides definitions of key terms. It gives examples of reliability calculations and discusses maintainability, availability, and quality. Analytical reliability techniques are also summarized, along with key points and steps to implement a reliability strategy.
Cafeteria management system in sanothimi campus(cms) suresh
This document presents a proposal for a Cafeteria Management System (CMS) for Sanothimi campus. The system would allow for menu management, ordering interfaces, and bill printing. It aims to increase efficiency and save time and money compared to the current non-computerized system. The proposal outlines the objectives, limitations, waterfall development methodology, data models, and timeline. The system would be a desktop application to manage food ordering and billing without home delivery capabilities. It is intended to reduce paperwork and provide efficient services to students and staff.
The Lean Game
After revolutionizing the automobile industry, Lean principles have been successfully applied to different knowledge areas including software development. This workshop is intended to master Lean concepts like Waste, Push&Pull systems, systems thinking,Kaizen etc.! In this interactive game, the participants will work in a small Lego production line, experiencing problems and applying Lean practices to overcome them.
Lean Daily Management System
A Lean Management System (a.k.a. Lean Daily Management System or Daily Management System) is the system that allows you to deliver customer value through proper support and leadership to those who are closest to the process (customers and process owners). These are practices and tools used to monitor, measure, and sustain the operation of Lean production operations. Lean management practices identify where actual performance fails to meet expected performance, and assigns and follows up improvement activities to bring actual in line with expected, or to raise the level of expected performance. The basic components of the Lean Management System are: Leader Standard Work, Visual Controls, Daily Accountability and Leadership Discipline.
The Lean Management System will help Lean leaders such as team leaders, supervisors, department managers, value stream managers and senior executives to improve leadership effectiveness based on Lean best practices.
As a daily management system, this is the most effective mechanism for managing employees not just in the shopfloor or office, but also those working in a flexible or work-from-home environments.
This Lean Management System PPT training presentation shows you how to implement a sustainable, successful transformation by developing a culture that has your stakeholders throughout the organizational chart involved and invested in the outcome. It teaches you how to implement the four key elements of the Lean Management System to enhance your effectiveness as a Lean transformation leader.
LEARNING OBJECTIVES
1. Acquire knowledge on the four key elements of the Lean Management System
2. Acquire knowledge on the supporting elements of the Lean Management System
CONTENTS
1. Introduction to Lean Management System
2. Key Elements of a Lean Management System
3. Supporting Elements of a Lean Management System
To download this complete presentation, visit:
https://www.oeconsulting.com.sg/training-presentations
Vertical Slicing
An easy to understand representation of vertical slicing. This slide deck was customized for the ATG framework.
Lean management = Learn management par Klaus Beulker
A 27% reduction of the inventory level, doubled turns and improved on time delivery prove that Lean Management is able to provide outstanding results in less than 18 months! This is possible if an aligned team is learning what Lean is and how it has to be organized. Learning Lean ongoing and continuously is the key for sustainable results. In his presentation “Lean Management = Learn Management”, Klaus Beulker shows how this is done at a German Crane builder, who has implemented Lean management “wall to wall”, from Engineering and Sales to Procurement, Material Planning and Production.
Découvrez d'autres retours d'expérience sur notre site www.institut-lean-france.fr
A3 Report (A3 Problem Solving) Poster
The A3 Report poster describes the A3 problem solving process from problem identification to resolution in a fashion that fosters learning, collaboration, and personal development.
The poster comes in four themes: light, dark, color and monochrome. Formatted in PDF and in editable PPTX, the poster can be easily printed on an A3-sized paper from an office copier machine and displayed on employee workstations, or distributed together with your workshop handouts.
The A3 Report poster complements your A3 Problem Solving training presentation materials. It serves as a takeaway and summary of your process improvement presentation.
The A3 problem solving process structure includes eight elements:
1. Theme - Concise statement of what this A3 report is about.
2. Background - Relevant historical data and information.
3. Current Condition - Detailed description of the current situation (e.g. process flow, trend chart, Pareto analysis, gap identification and problem statement).
4. Goal Statement - Specific goal to address the gap or future state from the current state.
5. Analysis - Depiction of analytical techniques to uncover the root causes of the problem or factors that affect the problem in the current state.
6. Countermeasures - A summary of who will do what by when in order to resolve the problem situation or achieve the future state.
7. Check Results - Quantitative comparison of actual results versus your goal.
8. Follow Up - Summary of follow up action items (e.g. lessons learned, communication to other parties, training, standardization, or other areas).
List of required HACCP document
Global Manager Group provides list of HACCP documents which are required in documentation of HACCP Certification
OEE
Some days ago, I found a discussion about the difference between Efficiency and Productivity.
I tried to answer in that forum from my understanding. In that discussion i called OEE as Productivity.
Four Steps of Gemba Walk Poster
The Gemba Walk is a four-step process to drive process improvement: 1) Define the objective, scope, and stakeholders; 2) Understand the physical environment and processes; 3) Observe processes in action and identify inefficiencies; 4) Analyze observations, validate improvements, and implement changes. The goal is to involve all process stakeholders to comprehensively understand the situation and identify opportunities to eliminate waste and streamline workflows, thereby improving processes.
Techniques for Effectively Slicing User Stories by Naresh Jain
In order to achieve my goals, as a buyer of your product, I want awesome feature. AT: make sure your users stories don't get in the way.
Users Stories, the tool teams use to break big ideas into small demonstrable deliverable, are easy to describe and challenging to write effectively. In this hands-on workshop you'll learn how to write great user stories and acceptance criteria, that everyone on the team understands. We'll learn various techniques to slice your stories using the tracer-bullet approach. We will discuss what elements should be included in the stories, what criteria you should keep in mind while slicing stories; why the size of your user story is important and how to make them smaller and efficient.
Agenda:
What do you do to Large Stories? Spike, Split, Stub & Timebox (SSST) technique.
Core Slicing Techniques:
1. System Slice
1.a. Static vs. Dynamic
1.b. Real-time vs. Batch Processing
1.c. Build vs. Buy
1.d. Automated vs. Manual Steps
1.e. Defer certain roles
2. Behavioural Slice
2.a. Adjusting Sophistication - MVF (Minimum Viable Feature) or Walking Skeleton
2.a.1. Acceptance Criteria
2.b. By-pass certain steps in the workflow
2.c. Focus on Happy Path First (edge cases later)
2.d. No options - 1 option - Many options
3. Incrementally improve ‘Ilities' (Usability, Scalability, Reliability, etc.)
3.a. Simpler UI (even consider using a standard UI)
3.b. Minmal Data
3.c. Improve Performance Iteratively
Writing Effective User Stories
Intended as a presentation for scrum product owners and analysts. A crash course in writing good user stories
More Related Content
What's hot
SMART Requirements
The document discusses developing requirements that are SMART (Specific, Measurable, Attainable, Realistic, Time-Bound). It provides examples of weak requirements and improved versions that are SMART. Developing SMART requirements leads to budget/schedule benefits, quicker consensus, and less rework. Each element of SMART is defined, with clear descriptions and additional examples contrasting poor versus improved requirements.
Insight on Non Conformity in food industry- Benefits, Types, Process Flow for...
Insight on Non Conformity in food industry- Benefits, Types, Process Flow for...PMG Engineering Private Limited
The importance of quality and food safety cannot be neglected in the present business scenario
due to extreme competition in open market. Many food industrialists have understood the
importance of implementation of system that can eliminate non- conformance products, as these
may help the company in preventing negative consequences like economical losses and helps to
protect the reputation of brand. The design of food safety management system for managing
non- conformance in industry may either support or hinder the effectiveness of continuous
improvement policy.
A non-conformance is involved when a process or a system failsto comply with the rules or meet
the required specifications of an audit standard(ISO 22000, IRC, BRC, SQC etc.). A requirement is a need, expectation, or obligation. It can be stated or implied by an organization, its customers,
or other interested parties. There are many types of requirements. Some of these include food
safety requirements, quality requirements, process requirements, product requirements,
customer requirements, management systems requirements, and legal requirements. Whenever
your organization fails to meet one of these requirements, a nonconformity occurs, and it mostly
occurs in the production and manufacturing processes like Supply chain management, inventory,
and material management process etc. It mainly asks for a rework which requires the
involvement of various personnel from the respective departments.Kanban
This presentation is an introduction to Kanban. It should help teams understand what Kanban is, its principles and how to implement it.
Human Error Prevention
Find the way to prevent the human error in industries as well as 16 types of human errors for better identification and generating solution for given identified errors
Manufacturing Excellence - Visual Factory
Visual Factory is a concept focused on the visual perception.
Purpose = replace texts by communicating via “visual signals”:
- in work instructions and checklists (pictures of the equipment with control points)
- with local signage: tags, labels (what to measure, range, …), pictures
Benefits:
- quick and easy instructions
- reductions in injuries and strain
- increased efficiency and reactivity
- reduction of the variability and the non-conformity rate
- decreased training time…
PPT ON VISUAL FACTORY
The document discusses the benefits of meditation for reducing stress and anxiety. Regular meditation practice can help calm the mind and body by lowering heart rate and blood pressure. Studies have shown that meditating for just 10-20 minutes per day can have significant positive impacts on both mental and physical health over time.
Human Error Prevention
How can we prevent accidents caused by human error? This presentation deals with typical examples of severe accidents related to human errors, and shows methods to prevent them.
Technical stories v1.2
This document discusses technical stories and architecture work in agile software development. It defines technical stories as stories that focus on technical goals rather than user goals. It discusses why technical stories are important for managing technical debt, architecture, and educating the technical team. It provides examples of technical stories and best practices for writing, accepting, and tracking them. The document also discusses architecture, why it is important, and how to plan architecture work through technical stories, architectural runways, and feedback loops.
Class 11 - MAINTENANCE PLANNING AND SCHEDULING_Dr.Adel_.ppt
The document discusses maintenance planning and scheduling. It describes the objectives of planning and scheduling as minimizing idle time, maximizing efficient use of resources, and maintaining operating equipment. Planning involves determining job requirements in advance while scheduling matches jobs to resources over time. The document outlines classification of maintenance work, planning procedures and levels, and techniques for developing long, medium, and short-range schedules.
Test plan
This document provides a template for a test plan that includes sections for test plan identification, references, introduction/scope, test items, risks, features to be tested, approach/strategy, pass/fail criteria, deliverables, schedule, responsibilities, and approvals. The template can be used to create a test plan that outlines what will be tested, how it will be tested, and manages the test process.
Unit 9 implementing the reliability strategy
This document discusses implementing reliability strategies and engineering. It begins by explaining the importance of reliability in fields like aviation, defense, and energy where failure could lead to dangerous situations. It then discusses mechanical reliability and common failure modes. Reliability engineering is introduced as the study of reliability and life-cycle management. Several high-profile system failures are listed to emphasize the need for reliability in design. The document outlines various areas of reliability engineering and provides definitions of key terms. It gives examples of reliability calculations and discusses maintainability, availability, and quality. Analytical reliability techniques are also summarized, along with key points and steps to implement a reliability strategy.
Cafeteria management system in sanothimi campus(cms) suresh
This document presents a proposal for a Cafeteria Management System (CMS) for Sanothimi campus. The system would allow for menu management, ordering interfaces, and bill printing. It aims to increase efficiency and save time and money compared to the current non-computerized system. The proposal outlines the objectives, limitations, waterfall development methodology, data models, and timeline. The system would be a desktop application to manage food ordering and billing without home delivery capabilities. It is intended to reduce paperwork and provide efficient services to students and staff.
The Lean Game
After revolutionizing the automobile industry, Lean principles have been successfully applied to different knowledge areas including software development. This workshop is intended to master Lean concepts like Waste, Push&Pull systems, systems thinking,Kaizen etc.! In this interactive game, the participants will work in a small Lego production line, experiencing problems and applying Lean practices to overcome them.
Lean Daily Management System
A Lean Management System (a.k.a. Lean Daily Management System or Daily Management System) is the system that allows you to deliver customer value through proper support and leadership to those who are closest to the process (customers and process owners). These are practices and tools used to monitor, measure, and sustain the operation of Lean production operations. Lean management practices identify where actual performance fails to meet expected performance, and assigns and follows up improvement activities to bring actual in line with expected, or to raise the level of expected performance. The basic components of the Lean Management System are: Leader Standard Work, Visual Controls, Daily Accountability and Leadership Discipline.
The Lean Management System will help Lean leaders such as team leaders, supervisors, department managers, value stream managers and senior executives to improve leadership effectiveness based on Lean best practices.
As a daily management system, this is the most effective mechanism for managing employees not just in the shopfloor or office, but also those working in a flexible or work-from-home environments.
This Lean Management System PPT training presentation shows you how to implement a sustainable, successful transformation by developing a culture that has your stakeholders throughout the organizational chart involved and invested in the outcome. It teaches you how to implement the four key elements of the Lean Management System to enhance your effectiveness as a Lean transformation leader.
LEARNING OBJECTIVES
1. Acquire knowledge on the four key elements of the Lean Management System
2. Acquire knowledge on the supporting elements of the Lean Management System
CONTENTS
1. Introduction to Lean Management System
2. Key Elements of a Lean Management System
3. Supporting Elements of a Lean Management System
To download this complete presentation, visit:
https://www.oeconsulting.com.sg/training-presentations
Vertical Slicing
An easy to understand representation of vertical slicing. This slide deck was customized for the ATG framework.
Lean management = Learn management par Klaus Beulker
A 27% reduction of the inventory level, doubled turns and improved on time delivery prove that Lean Management is able to provide outstanding results in less than 18 months! This is possible if an aligned team is learning what Lean is and how it has to be organized. Learning Lean ongoing and continuously is the key for sustainable results. In his presentation “Lean Management = Learn Management”, Klaus Beulker shows how this is done at a German Crane builder, who has implemented Lean management “wall to wall”, from Engineering and Sales to Procurement, Material Planning and Production.
Découvrez d'autres retours d'expérience sur notre site www.institut-lean-france.fr
A3 Report (A3 Problem Solving) Poster
The A3 Report poster describes the A3 problem solving process from problem identification to resolution in a fashion that fosters learning, collaboration, and personal development.
The poster comes in four themes: light, dark, color and monochrome. Formatted in PDF and in editable PPTX, the poster can be easily printed on an A3-sized paper from an office copier machine and displayed on employee workstations, or distributed together with your workshop handouts.
The A3 Report poster complements your A3 Problem Solving training presentation materials. It serves as a takeaway and summary of your process improvement presentation.
The A3 problem solving process structure includes eight elements:
1. Theme - Concise statement of what this A3 report is about.
2. Background - Relevant historical data and information.
3. Current Condition - Detailed description of the current situation (e.g. process flow, trend chart, Pareto analysis, gap identification and problem statement).
4. Goal Statement - Specific goal to address the gap or future state from the current state.
5. Analysis - Depiction of analytical techniques to uncover the root causes of the problem or factors that affect the problem in the current state.
6. Countermeasures - A summary of who will do what by when in order to resolve the problem situation or achieve the future state.
7. Check Results - Quantitative comparison of actual results versus your goal.
8. Follow Up - Summary of follow up action items (e.g. lessons learned, communication to other parties, training, standardization, or other areas).
List of required HACCP document
Global Manager Group provides list of HACCP documents which are required in documentation of HACCP Certification
OEE
Some days ago, I found a discussion about the difference between Efficiency and Productivity.
I tried to answer in that forum from my understanding. In that discussion i called OEE as Productivity.
Four Steps of Gemba Walk Poster
The Gemba Walk is a four-step process to drive process improvement: 1) Define the objective, scope, and stakeholders; 2) Understand the physical environment and processes; 3) Observe processes in action and identify inefficiencies; 4) Analyze observations, validate improvements, and implement changes. The goal is to involve all process stakeholders to comprehensively understand the situation and identify opportunities to eliminate waste and streamline workflows, thereby improving processes.
What's hot (20)
Insight on Non Conformity in food industry- Benefits, Types, Process Flow for...
Insight on Non Conformity in food industry- Benefits, Types, Process Flow for...
Class 11 - MAINTENANCE PLANNING AND SCHEDULING_Dr.Adel_.ppt
Class 11 - MAINTENANCE PLANNING AND SCHEDULING_Dr.Adel_.ppt
Cafeteria management system in sanothimi campus(cms) suresh
Cafeteria management system in sanothimi campus(cms) suresh
Lean management = Learn management par Klaus Beulker
Lean management = Learn management par Klaus Beulker
Viewers also liked
Techniques for Effectively Slicing User Stories by Naresh Jain
In order to achieve my goals, as a buyer of your product, I want awesome feature. AT: make sure your users stories don't get in the way.
Users Stories, the tool teams use to break big ideas into small demonstrable deliverable, are easy to describe and challenging to write effectively. In this hands-on workshop you'll learn how to write great user stories and acceptance criteria, that everyone on the team understands. We'll learn various techniques to slice your stories using the tracer-bullet approach. We will discuss what elements should be included in the stories, what criteria you should keep in mind while slicing stories; why the size of your user story is important and how to make them smaller and efficient.
Agenda:
What do you do to Large Stories? Spike, Split, Stub & Timebox (SSST) technique.
Core Slicing Techniques:
1. System Slice
1.a. Static vs. Dynamic
1.b. Real-time vs. Batch Processing
1.c. Build vs. Buy
1.d. Automated vs. Manual Steps
1.e. Defer certain roles
2. Behavioural Slice
2.a. Adjusting Sophistication - MVF (Minimum Viable Feature) or Walking Skeleton
2.a.1. Acceptance Criteria
2.b. By-pass certain steps in the workflow
2.c. Focus on Happy Path First (edge cases later)
2.d. No options - 1 option - Many options
3. Incrementally improve ‘Ilities' (Usability, Scalability, Reliability, etc.)
3.a. Simpler UI (even consider using a standard UI)
3.b. Minmal Data
3.c. Improve Performance Iteratively
Writing Effective User Stories
Intended as a presentation for scrum product owners and analysts. A crash course in writing good user stories
User Stories for your Product Backlog
This is a general introduction into user stories, their advantages and a suggestion how to use them in scrum projects.
Agile and user story workshop Peter Saddington
The document provides an overview of Agile and Scrum frameworks and processes. It discusses key Scrum roles like Product Owner and Scrum Master. It also covers Scrum artifacts like user stories, product and sprint backlogs. The document emphasizes that user stories should be short, independent, negotiable, valuable, estimable, small, and testable (INVEST criteria). It provides examples of proper user story structure and components.
Production Supply with SAP EWM
This document provides an overview of production supply methods in SAP Extended Warehouse Management (EWM). It describes key concepts like production supply areas and material staging methods. Examples are provided of pick parts staging, release order parts staging, crate parts replenishment, and production supply with kanban to illustrate how materials are staged from main storage to production areas using different transactions and document flows in SAP EWM and ERP.
Kitting with SAP EWM
Functional overview of the kitting process in SAP EWM (Kit-to-Stock, Kit-to-Order and Reverse Kitting).
Viewers also liked (6)
Techniques for Effectively Slicing User Stories by Naresh Jain
Techniques for Effectively Slicing User Stories by Naresh Jain
Similar to Ways to split user stories
Stories, Backlog & Mapping
The goal of this presentation is to explore the most efficient way to manage the product backlog, using blitz planning, story maps (walking skeleton) and improving the quality of our stories by focusing on stronger acceptance criteria, as well as using personas. The benefit of having a better way to organize and visualize the product backlog is to improve our ability to conduct release and iteration planning, as well as produce a better product road map. By attending this session you will be better equipped to help your team and product owner work with the product backlog. As a project manager, you will be introduced to simple techniques that will help you better manage your Agile project and improve visibility to all the work.
Agile stories, estimating and planning
This document provides an overview of agile stories, estimating, and planning. It discusses what user stories are, how to write them, and techniques for estimating story sizes such as story points. It also covers different levels of planning including release planning, iteration planning, and daily planning. The document is intended to provide background information on using agile methods for requirements management and project planning.
Story Time - Writing Effective User Stories
Writing good user stories is an art and is essential for successful Scrum. In this presentation I talk about what user stories are, what makes them great, how to write them and how not to.
Some concepts are explained through animation which is best viewed by downloading and opening in PowerPoint.
UX Workshop: How to design a product with great user experience
Practical tips for Digital Designers - Corporate Innovation Summit Bangkok March 28-29 Centara Grand at Central World.
Agile Story Writing
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 User Stories and Goal Modeling
Agile User Stories and Goal Modeling.
Samedi Heng, Manuel Kolp, Yves Wautelet.
M. Kolp - LSINF 1210: Information Systems and Project Management, 2017-2018, UCLouvain
Xp 2016 superchargeyourproductbacklogwithuserstories-suzannelaz
This document summarizes a workshop on supercharging a product backlog with user stories. The workshop covers defining user stories, examples of user stories, splitting large stories into smaller ones, acceptance criteria, and product backlog refinement. Attendees participate in hands-on exercises to practice writing, critiquing, and splitting user stories. The document emphasizes that user stories should describe features from the perspective of users or stakeholders and focus on value and benefits.
Agile Story Writing
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.
All about User story
The document discusses user stories in agile development. It defines a user story, explaining that it is a short description of a feature from the perspective of a user. It provides an example user story template and examples. It also discusses what a good user story should contain, how to write acceptance criteria and test cases, and the INVEST principles for user stories. It explains who can write user stories, when they are written, and how to split large user stories into smaller ones. It distinguishes user stories from tasks and defines what "definition of ready" and "definition of done" mean for user stories.
User Stories explained
This document provides information on user stories in Agile software development. It defines what a user story is, how it should be written in the form of a short description of a requirement from the perspective of an end user, and includes elements like acceptance criteria. It also discusses best practices for user stories, such as keeping them small and focused on one goal, and how user stories are used to plan and track work in Sprints.
The information supernova
This document discusses technologies for analyzing large amounts of data from various sources on the internet and social media. It introduces Info Arab's Significs technology, which can analyze text streams and social media interactions to extract structured and meaningful data. Significs converts unstructured data into structured data and identifies indicators of content across many dimensions of analysis. It also discusses Fetch Technologies for gathering data from various online sources and providing APIs and platforms for accessing the analyzed information.
NYU Web Intensive - Week 3 Class 1
The document provides an overview of a web design intensive course. It includes objectives for the course, which focuses on usability assessment, building a portfolio, and the business aspects of web design. It outlines several workshops and topics that will be covered, including usability principles and testing, user-centered design, and Nielsen's 10 usability heuristics. Students are asked to complete tasks like analyzing websites and providing usability reviews for a blog.
Secure Developer Access at Decisiv
Learn how Decisiv provides secure access to developers and deals with compliance hurdles. Senior Engineer Hunter Madison will talk about how Decisiv needed to quickly solve the pain of scaling the engineering team, migrating to AWS, maintaining ISO 27002 compliance, and a few of his key learnings from his two-year journey using Teleport.
Sachin portfolio ux_service designer
I am trying to improve people's lives through meaningful UX design and innovation. I love creative techniques and design methodologies and have recently stuck my naked foot in the waters of UX Service Design.Trying to create an experiential world around the products.
www.sachinrathi.com
Life cycle of user story: Outside-in agile product management & testing, or...
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.
UX and VIMM @ LTUX (jul18)
The VIMM model provides a framework to optimize user experience across visual, intellectual, memory, and motor loads. It suggests minimizing each type of load, such as using visual hierarchy and emphasis to guide the eye and simplify decision-making. Following the model can improve usability by matching screen flows to tasks, using intuitive grouping and labeling, consistent controls, recognition over recall, and reducing unnecessary interactions.
Developing Information Architecture with Non-Technical Stakeholders
This document provides an overview of developing information architecture with non-technical stakeholders. It discusses identifying project stakeholders, conducting research such as stakeholder interviews and content analysis, organizing and labeling content, designing navigation and information models through methods like card sorting, and creating deliverables like wireframes. The goal is to facilitate stakeholder involvement in developing an effective information architecture for a website or software.
Api craft notes
The document discusses notes from the 2014 API Craft conference. Several topics are mentioned, including hypermedia, affordances, building hypermedia servers, documenting APIs, and the future of mobile APIs. Hypermedia is presented as a way to avoid hardcoding clients, reduce versioning problems, and make resource relations and states discoverable. Challenges with hypermedia include unclear definitions, payload size, and potential bad user experiences on mobile. The document also provides suggestions for how to work with APIs still in development and resources related to topics from the conference.
Effective Professional Writing The MemoAdapted from
Effective
Professional
Writing: The
Memo
Adapted from a presentation by Xavier de Souza Briggs,
Department of Urban Studies and Planning, MIT
I F S M 2 01
Licensing Information
This work “Effective Professional Writing: The Memo”, a derivative of Effective Professional Writing: The
Memo, by the Massachusetts Institute of Technology, is licensed under a Creative Commons Attribution-
NonCommercial-ShareAlike 4.0 International License. “Effective Professional Writing: The Memo” by
UMGC is licensed under a Creative Commons Attribution-NonCommercial-
ShareAlike 4.0 International License.
https://ocw.mit.edu/courses/urban-studies-and-planning/11-201-gateway-planning-action-fall-2007/communication/memo.pdf
https://creativecommons.org/licenses/by-nc-sa/4.0/
https://creativecommons.org/licenses/by-nc-sa/4.0/
https://creativecommons.org/licenses/by-nc-sa/4.0/
“To do our work, we all have to read a mass
of papers. Nearly all of them are far too long.
This wastes time, while energy has to be
spent in looking for the essential points.
I ask my colleagues and their staffs to see to
it that their Reports are shorter.”
- W I N STO N C H U R C H I L L , AU G U ST 9 , 19 4 0
- S O U RC E ( A O N E PAG E R E A D ) : C H U RC H I L L’ S “ B R E V I T Y ” M E M O
https://i.insider.com/592828b05a1d1b02b94fb302?width=700&format=jpeg&auto=webp
Writing Memos
The context of professional writing
Why write memos?
How to write them?
How to make them better?
3
The Context
The workplace or field:
◦ Time is precious.
◦ Information has substantive as well as political implications.
The decision-maker as reader:
◦ Busy and distracted (attention “spread thin”), not necessarily patient while you get to the point.
◦ Info needs are varied, unpredictable, fluid.
◦ Decision-maker sometimes offers vague instructions.
4
Academic vs. professional writing
Differences (when writing concisely)
◦ The academic reader often demands nuance and relevance to established lines of thinking, while the
professional reader wants the “so what’s” for their decision making emphasized (relevance to their
actions).
◦ An academic assignment assumes a small and benevolent audience, but professional documents can be
“leaked,” end up in the hands of unintended readers.
Similarities
◦ Strong essays and strong memos both start with your main ideas, but essays usually build toward
conclusion and synthesis. The memo’s conclusions are usually right up top.
◦ In both, persuasive argument = clear viewpoint + evidence
◦ In both, addressing counter-arguments tends to strengthen your case.
5
Top mistakes in memos
Content:
◦ off point or off task (major substantive
omissions, given the request);
◦ impolitic (risks political costs if leaked);
◦ inappropriate assumptions as to
background knowledge;
◦ no evidence.
Organization:
◦ important info “buried,”
◦ no summary up top, format confusing,
not “skim-able.”
◦ Sentences long and d ...
Resume
Mohd Imran has 3 years of experience designing and developing business applications using client server technologies and web technologies like PHP, MySQL, Java Script. He has expertise in application development, documentation, testing, and possesses strong communication skills.
Similar to Ways to split user stories (20)
UX Workshop: How to design a product with great user experience
UX Workshop: How to design a product with great user experience
Xp 2016 superchargeyourproductbacklogwithuserstories-suzannelaz
Xp 2016 superchargeyourproductbacklogwithuserstories-suzannelaz
Life cycle of user story: Outside-in agile product management & testing, or...
Life cycle of user story: Outside-in agile product management & testing, or...
Developing Information Architecture with Non-Technical Stakeholders
Developing Information Architecture with Non-Technical Stakeholders
Effective Professional Writing The MemoAdapted from
Effective Professional Writing The MemoAdapted from
Recently uploaded
ALGIT - Assembly Line for Green IT - Numbers, Data, Facts
Presentation from Ghazal Aakel and Eric Jochum at the GSD Community Stage Meetup on June 6th, 2024
Microservice Teams - How the cloud changes the way we work
A lot of technical challenges and complexity come with building a cloud-native and distributed architecture. The way we develop backend software has fundamentally changed in the last ten years. Managing a microservices architecture demands a lot of us to ensure observability and operational resiliency. But did you also change the way you run your development teams?
Sven will talk about Atlassian’s journey from a monolith to a multi-tenanted architecture and how it affected the way the engineering teams work. You will learn how we shifted to service ownership, moved to more autonomous teams (and its challenges), and established platform and enablement teams.
What is Master Data Management by PiLog Group
PiLog Group's Master Data Record Manager (MDRM) is a sophisticated enterprise solution designed to ensure data accuracy, consistency, and governance across various business functions. MDRM integrates advanced data management technologies to cleanse, classify, and standardize master data, thereby enhancing data quality and operational efficiency.
Automated software refactoring with OpenRewrite and Generative AI.pptx.pdf
https://2024.springio.net/sessions/automated-software-refactoring-with-openrewrite-and-generative-ai/
Webinar On-Demand: Using Flutter for Embedded
Flutter is a popular open source, cross-platform framework developed by Google. In this webinar we'll explore Flutter and its architecture, delve into the Flutter Embedder and Flutter’s Dart language, discover how to leverage Flutter for embedded device development, learn about Automotive Grade Linux (AGL) and its consortium and understand the rationale behind AGL's choice of Flutter for next-gen IVI systems. Don’t miss this opportunity to discover whether Flutter is right for your project.
Empowering Growth with Best Software Development Company in Noida - Deuglo
Do you want Software for your Business? Visit Deuglo
Deuglo has top Software Developers in India. They are experts in software development and help design and create custom Software solutions.
Deuglo follows seven steps methods for delivering their services to their customers. They called it the Software development life cycle process (SDLC).
Requirement — Collecting the Requirements is the first Phase in the SSLC process.
Feasibility Study — after completing the requirement process they move to the design phase.
Design — in this phase, they start designing the software.
Coding — when designing is completed, the developers start coding for the software.
Testing — in this phase when the coding of the software is done the testing team will start testing.
Installation — after completion of testing, the application opens to the live server and launches!
Maintenance — after completing the software development, customers start using the software.
DDS-Security 1.2 - What's New? Stronger security for long-running systems
DDS Security Version 1.2 was adopted in 2024. This revision strengthens support for long runnings systems adding new cryptographic algorithms, certificate revocation, and hardness against DoS attacks.
GreenCode-A-VSCode-Plugin--Dario-Jurisic
Presentation about a VSCode plugin from Dario Jurisic at the GSD Community Stage meetup
How to write a program in any programming language
How to write a program in any programming language
SWEBOK and Education at FUSE Okinawa 2024
Takashi Kobayashi and Hironori Washizaki, "SWEBOK Guide and Future of SE Education," First International Symposium on the Future of Software Engineering (FUSE), June 3-6, 2024, Okinawa, Japan
What is Augmented Reality Image Tracking
Augmented Reality (AR) Image Tracking is a technology that enables AR applications to recognize and track images in the real world, overlaying digital content onto them. This enhances the user's interaction with their environment by providing additional information and interactive elements directly tied to physical images.
Transform Your Communication with Cloud-Based IVR Solutions
Discover the power of Cloud-Based IVR Solutions to streamline communication processes. Embrace scalability and cost-efficiency while enhancing customer experiences with features like automated call routing and voice recognition. Accessible from anywhere, these solutions integrate seamlessly with existing systems, providing real-time analytics for continuous improvement. Revolutionize your communication strategy today with Cloud-Based IVR Solutions. Learn more at: https://thesmspoint.com/channel/cloud-telephony
Need for Speed: Removing speed bumps from your Symfony projects ⚡️
No one wants their application to drag like a car stuck in the slow lane! Yet it’s all too common to encounter bumpy, pothole-filled solutions that slow the speed of any application. Symfony apps are not an exception.
In this talk, I will take you for a spin around the performance racetrack. We’ll explore common pitfalls - those hidden potholes on your application that can cause unexpected slowdowns. Learn how to spot these performance bumps early, and more importantly, how to navigate around them to keep your application running at top speed.
We will focus in particular on tuning your engine at the application level, making the right adjustments to ensure that your system responds like a well-oiled, high-performance race car.
Artificia Intellicence and XPath Extension Functions
The purpose of this presentation is to provide an overview of how you can use AI from XSLT, XQuery, Schematron, or XML Refactoring operations, the potential benefits of using AI, and some of the challenges we face.
Energy consumption of Database Management - Florina Jonuzi
Presentation from Florina Jonuzi at the GSD Community Stage Meetup on June 06, 2024
Vitthal Shirke Java Microservices Resume.pdf
Software Engineering, Software Consulting, Tech Lead, Spring Boot, Spring Cloud, Spring Core, Spring JDBC, Spring Transaction, Spring MVC, OpenShift Cloud Platform, Kafka, REST, SOAP, LLD & HLD.
Graspan: A Big Data System for Big Code Analysis
We built a disk-based parallel graph system, Graspan, that uses a novel edge-pair centric computation model to compute dynamic transitive closures on very large program graphs.
We implement context-sensitive pointer/alias and dataflow analyses on Graspan. An evaluation of these analyses on large codebases such as Linux shows that their Graspan implementations scale to millions of lines of code and are much simpler than their original implementations.
These analyses were used to augment the existing checkers; these augmented checkers found 132 new NULL pointer bugs and 1308 unnecessary NULL tests in Linux 4.4.0-rc5, PostgreSQL 8.3.9, and Apache httpd 2.2.18.
- Accepted in ASPLOS ‘17, Xi’an, China.
- Featured in the tutorial, Systemized Program Analyses: A Big Data Perspective on Static Analysis Scalability, ASPLOS ‘17.
- Invited for presentation at SoCal PLS ‘16.
- Invited for poster presentation at PLDI SRC ‘16.
Revolutionizing Visual Effects Mastering AI Face Swaps.pdf
The quest for the best AI face swap solution is marked by an amalgamation of technological prowess and artistic finesse, where cutting-edge algorithms seamlessly replace faces in images or videos with striking realism. Leveraging advanced deep learning techniques, the best AI face swap tools meticulously analyze facial features, lighting conditions, and expressions to execute flawless transformations, ensuring natural-looking results that blur the line between reality and illusion, captivating users with their ingenuity and sophistication.
Web:- https://undressbaby.com/
KuberTENes Birthday Bash Guadalajara - Introducción a Argo CD
Charla impartida en el evento de "KuberTENes Birthday Bash Guadalajara" para celebrar el 10mo. aniversario de Kubernetes #kuberTENes #celebr8k8s #k8s
Recently uploaded (20)
ALGIT - Assembly Line for Green IT - Numbers, Data, Facts
ALGIT - Assembly Line for Green IT - Numbers, Data, Facts
Microservice Teams - How the cloud changes the way we work
Microservice Teams - How the cloud changes the way we work
Automated software refactoring with OpenRewrite and Generative AI.pptx.pdf
Automated software refactoring with OpenRewrite and Generative AI.pptx.pdf
Empowering Growth with Best Software Development Company in Noida - Deuglo
Empowering Growth with Best Software Development Company in Noida - Deuglo
DDS-Security 1.2 - What's New? Stronger security for long-running systems
DDS-Security 1.2 - What's New? Stronger security for long-running systems
How to write a program in any programming language
How to write a program in any programming language
Transform Your Communication with Cloud-Based IVR Solutions
Transform Your Communication with Cloud-Based IVR Solutions
Need for Speed: Removing speed bumps from your Symfony projects ⚡️
Need for Speed: Removing speed bumps from your Symfony projects ⚡️
Artificia Intellicence and XPath Extension Functions
Artificia Intellicence and XPath Extension Functions
Energy consumption of Database Management - Florina Jonuzi
Energy consumption of Database Management - Florina Jonuzi
Revolutionizing Visual Effects Mastering AI Face Swaps.pdf
Revolutionizing Visual Effects Mastering AI Face Swaps.pdf
KuberTENes Birthday Bash Guadalajara - Introducción a Argo CD
KuberTENes Birthday Bash Guadalajara - Introducción a Argo CD
Ways to split user stories
- 1. Ways to split user stories By Nikos Raptis nikolaos.raptis83@gmail.com
- 2. The INVEST model Good user stories follow Bill Wake’s INVEST model ➢ Of order of user story delivery ➢ Of internal and external dependencies ➢ Flexible scope ➢ None specific language ➢ Explain the intention, not the implementation ➢ Value is clear to everyone ➢ Persona matches Benefit & Goal will deliver the benefit ➢ Avoid technical / role specific language ➢ Clear and concise explanation ➢ Avoid technical / role specific language ➢ Easily fit into a Sprint ➢ Can be automated ➢ Avoid external testing / long test suites Independent Negotiable Valuable Estimable Small Testable
- 3. Patterns for splitting ● Workflow Steps ● Business Rule Variations ● Major Effort ● Simple / Complex ● Variations in Data ● Data Entry Methods ● Defer Performance ● Operation (e.g CRUD) ● Break out a spike Source: Richard Lawrence, http://agileforall.com/patterns-for-splitting-user-stories
- 4. Workflow Steps As a content manager, I can publish a news story to the corporate website. …I can publish a news story directly to the corporate website. …I can publish a news story with editor review. …I can publish a news story with legal review. …I can view a news story on a staging site. …I can publish a news story from the staging site to production. Initial User Story Potential User Stories Source: Richard Lawrence, http://agileforall.com/patterns-for-splitting-user-stories
- 5. Business Rule Variations As a user, I can search for flights with flexible dates. …as “n days between x and y.” …as “a weekend in December.” …as “± n days of x and y.” Initial User Story Potential derived User Stories Source: Richard Lawrence, http://agileforall.com/patterns-for-splitting-user-stories
- 6. Major Effort As a user, I can pay for my flight with VISA, MasterCard, Diners Club, or American Express. …I can pay with one credit card type (of VISA, MC, DC, AMEX). …I can pay with all four credit card types (VISA, MC, DC, AMEX) (given one card type already implemented). Initial User Story Potential derived User Stories Source: Richard Lawrence, http://agileforall.com/patterns-for-splitting-user-stories
- 7. Simple/Complex As a user, I can search for flights between two destinations. …specifying a max number of stops. …including nearby airports. …using flexible dates. Initial User Story Potential User Stories Source: Richard Lawrence, http://agileforall.com/patterns-for-splitting-user-stories
- 8. Variations in Data As a content manager, I can create news stories. …in English. …in Japanese. …in Arabic. Initial User Story Potential User Stories Source: Richard Lawrence, http://agileforall.com/patterns-for-splitting-user-stories
- 9. Defer Performance As a user, I can search for flights between two destinations. …(slow—just get it done, show a “searching” animation). …(in under 5 seconds). Initial User Story Potential User Stories Source: Richard Lawrence, http://agileforall.com/patterns-for-splitting-user-stories
- 10. Operations (e.g. CRUD) As a user, I can manage my account. …I can sign up for an account. …I can edit my account settings. …I can cancel my account. Initial User Story Potential User Stories Source: Richard Lawrence, http://agileforall.com/patterns-for-splitting-user-stories
- 11. Break Out a Spike As a user, I can pay by credit card. ...Investigate credit card processing. ...Implement credit card processing. Initial User Story Potential User Stories Source: Richard Lawrence, http://agileforall.com/patterns-for-splitting-user-stories
- 12. Tips ● Resist the temptation to split an overly large user story by architectural layers. ● Satisfy the INVEST model ● If PO doesn't know how to do it, SM should help him
- 13. Source: Richard Lawrence, http://agileforall.com/new-story-splitting-resource