The document discusses 21 patterns for splitting user stories into multiple stories. Some common patterns include splitting based on workflow steps, use case scenarios, different data types or operations on an entity, core functionality versus enhancements, and manual versus automated processes. The goals of splitting are to prioritize work, create smaller stories, and reduce dependencies between stories. The document provides descriptions and examples of when to use each pattern.
Writing Good User Stories (Hint: It's not about writing)one80
User stories are typically the foundation of the Product Backlog. However, the original purpose has been lost. This is from a presentation that was given to help remind everyone of what User Stories are, and what they aren't. The purpose of User Stories is to drive conversations, not to hand "requirements" from one group to the next.
Creating a backlog of user stories is pretty straight forward but it doesn't help you when it comes to decisions like what to build first, how to prioritize and groom the backlog, how to scope and plan the project, and how to visualize progress. The traditional backlog is simply too flat and often too long to help you see the bigger picture and make good decisions. User Story Mapping helps simplify all of these common project issues. By adding a third dimension to your backlog, your team will make better decisions about priorities, scope, and planning while improving your ability to visualize progress.
In this practical session I’ll cover the basics of user story mapping before walking you through case studies of how our teams are using this approach and the results we are achieving. I'll show you the before, during, and after pictures from several projects so that you can understand how our maps progress during the projects and how we use them to influence iterative development, promote good decision making, and visualize priorities, plans, scope and progress.
Writing Good User Stories (Hint: It's not about writing)one80
User stories are typically the foundation of the Product Backlog. However, the original purpose has been lost. This is from a presentation that was given to help remind everyone of what User Stories are, and what they aren't. The purpose of User Stories is to drive conversations, not to hand "requirements" from one group to the next.
Creating a backlog of user stories is pretty straight forward but it doesn't help you when it comes to decisions like what to build first, how to prioritize and groom the backlog, how to scope and plan the project, and how to visualize progress. The traditional backlog is simply too flat and often too long to help you see the bigger picture and make good decisions. User Story Mapping helps simplify all of these common project issues. By adding a third dimension to your backlog, your team will make better decisions about priorities, scope, and planning while improving your ability to visualize progress.
In this practical session I’ll cover the basics of user story mapping before walking you through case studies of how our teams are using this approach and the results we are achieving. I'll show you the before, during, and after pictures from several projects so that you can understand how our maps progress during the projects and how we use them to influence iterative development, promote good decision making, and visualize priorities, plans, scope and progress.
How to slice user stories, using concepts like low/high fidelity solutions, iterative vs incremental delivery, and hunting for small bits of value rather than breaking down work in technical chunks.
Re-uploading my User Story Splitting workshop; it seems to have gone missing.
This is a slide deck I have used for helping people learn various user story splitting techniques.
User story can be described as functional increment and it is a key element in agile environment. This presentation introduces fundamentals about user stories that can be used to educate teams or simply to review the basics.
Do you want to write great User Stories that provide the vehicle for conversation and confirmation that we build the right thing? Do you struggle with splitting stories so that they still provide business value but can be accomplished within a fraction of your iteration? We will do a quick refresher on User Story formatting to include Acceptance Criteria. Additionally we will learn techniques for splitting stories in this interactive workshop.
What are User Stories? How should we write them? How to write them well?
Effective User Stories allow your team to be effective (deliver want the User needs) and efficient (Deliver it quickly and importantly don't deliver unneeded features).
User Stories Writing - Codemotion 2013Fabio Armani
Stefano Leli (Freelance) - Fabio Armani (OpenWare)
Scrivere user stories dovrebbe essere facile...almeno in teoria. In realtà nella pratica ci troviamo troppo spesso a combattere con storie vaghe o troppo tecniche, storie che non possono essere testate o addirittura che non portano alcun valore. In questo workshop cercheremo assieme di comprendere la differenza tra requisiti funzionali e User Story, tra User Story e Use Case, mediante dei case study.
The Product Backlog Refinement refers to activities that help us keeping the product backlog in optimal form. This overview presents all important aspects of this important analysis activity in SCRUM.
Overview
- What is a User Story?
- User Story template
- examples of User Stories
- User Story Checklist
- Why not tasks?
- What is Acceptance Criteria?
- Examples of Acceptance Criteria
- Acceptance Criteria checklist
This presentation discusses how you can leverage the innovation strategy and the product lifecycle to get your product strategy right and achieve product success; how to make your product stand out from the crowd; and how you can effectively capture your product strategy.
Analysis In Agile: It's More than Just User StoriesKent McDonald
A common question asked by teams adopting agile is "what does business analysis look like in agile?" The common answer is "writing user stories".
WRONG!
Okay, maybe not wrong, but certainly not the whole story (pardon the pun). Business analysis in agile is concerned with understanding the problem and possible solutions in order to ensure the team is building the right thing. User stories can be helpful, but are certainly not sufficient for doing that.
In this session, Kent McDonald describes how you can perform just enough business analysis to discover the right things to build. This includes how to really use value to decide what to build first, why process flows, data models, and mockups are still extremely helpful, and why the function of user stories is more important than their form.
Along the way, Kent shares examples from a system replacement project he is working on and suggests ways you can apply these techniques to your own projects.
How to slice user stories, using concepts like low/high fidelity solutions, iterative vs incremental delivery, and hunting for small bits of value rather than breaking down work in technical chunks.
Re-uploading my User Story Splitting workshop; it seems to have gone missing.
This is a slide deck I have used for helping people learn various user story splitting techniques.
User story can be described as functional increment and it is a key element in agile environment. This presentation introduces fundamentals about user stories that can be used to educate teams or simply to review the basics.
Do you want to write great User Stories that provide the vehicle for conversation and confirmation that we build the right thing? Do you struggle with splitting stories so that they still provide business value but can be accomplished within a fraction of your iteration? We will do a quick refresher on User Story formatting to include Acceptance Criteria. Additionally we will learn techniques for splitting stories in this interactive workshop.
What are User Stories? How should we write them? How to write them well?
Effective User Stories allow your team to be effective (deliver want the User needs) and efficient (Deliver it quickly and importantly don't deliver unneeded features).
User Stories Writing - Codemotion 2013Fabio Armani
Stefano Leli (Freelance) - Fabio Armani (OpenWare)
Scrivere user stories dovrebbe essere facile...almeno in teoria. In realtà nella pratica ci troviamo troppo spesso a combattere con storie vaghe o troppo tecniche, storie che non possono essere testate o addirittura che non portano alcun valore. In questo workshop cercheremo assieme di comprendere la differenza tra requisiti funzionali e User Story, tra User Story e Use Case, mediante dei case study.
The Product Backlog Refinement refers to activities that help us keeping the product backlog in optimal form. This overview presents all important aspects of this important analysis activity in SCRUM.
Overview
- What is a User Story?
- User Story template
- examples of User Stories
- User Story Checklist
- Why not tasks?
- What is Acceptance Criteria?
- Examples of Acceptance Criteria
- Acceptance Criteria checklist
This presentation discusses how you can leverage the innovation strategy and the product lifecycle to get your product strategy right and achieve product success; how to make your product stand out from the crowd; and how you can effectively capture your product strategy.
Analysis In Agile: It's More than Just User StoriesKent McDonald
A common question asked by teams adopting agile is "what does business analysis look like in agile?" The common answer is "writing user stories".
WRONG!
Okay, maybe not wrong, but certainly not the whole story (pardon the pun). Business analysis in agile is concerned with understanding the problem and possible solutions in order to ensure the team is building the right thing. User stories can be helpful, but are certainly not sufficient for doing that.
In this session, Kent McDonald describes how you can perform just enough business analysis to discover the right things to build. This includes how to really use value to decide what to build first, why process flows, data models, and mockups are still extremely helpful, and why the function of user stories is more important than their form.
Along the way, Kent shares examples from a system replacement project he is working on and suggests ways you can apply these techniques to your own projects.
Agile Team Working agreements, also known as team norms, are guidelines developed by the teams as to how they must work together to create a positive, productive process.
This tutorial teaches you how to employ the Product Canvas, an agile UX tool that helps you create a product with a great user experience and the right features. Download the Product Canvas at: http://www.romanpichler.com/tools/product-canvas/
Some teams think they can be agile by using a defined process or set of practices as defined by one of the agile approaches. This is just “doing Agile.” Other teams are agile in name only – the team says it’s “doing Agile” but ends up using the same old practices and achieving the same results. Teams adopt agile for a variety of reasons, but it’s not the process or set of practices they select that produces the results they seek. Teams are most successful when they adopt a particular mindset in order to “be agile”. Join Kent McDonald as he describes this mindset through 7 key ideas based on how people and organizations work best. We’ll discuss some specific techniques you can use to adopt the mindset on your project, how the project manager role changes along with the mindset, and how to help your team move from “doing Agile” to actually “being agile”.
Agile Leadership: Accelerating Business Agility - ContextKent McDonald
The "one size fits all" approach to Project Leadership is inherently flawed. Practitioners have found that the two primary attributes of uncertainty and complexity of a project provide guidance to effective project leadership and governance. Complexity includes project composition such as team size and criticality, while uncertainty includes both market and technical uncertainty. The approach and leadership style required for a simple, stable project is quite different than what is required for highly uncertain, highly complex projects. This session demonstrates how to use the Context Leadership Model to determine the appropriate approach and leadership style for a project based on its uncertainty and complexity.
Key Learning Points
How to assess the complexity and uncertainty characteristics of a project
How to tailor the project approach based on those characteristics
How to determine the appropriate leadership style for a project based on its characteristics
How to find the real need with socratic questioningKent McDonald
A common piece of advice is that your team should discover the true need of your project. Unfortunately advice on how to make that happen isn't as prevalent. In this session you'll have a chance to practice a simple technique to get to the core of what your stakeholders need that has been around for over 2000 years - Socratic questioning.
Join Kent McDonald as he walks you through a technique aimed at uncovering the (not intentionally) hidden need that your stakeholders are trying to satisfy, without asking "why?" five times in a row. Kent describes the questions, why they work and in what context they work based on his experience with IT organizations and the Agile Alliance. You'll then have a chance to practice them out to find out about a real project.
The line of questioning was inspired by Brennan Dunn who uses them to understand the true needs of his web development consultants.
Come learn about and practice this technique so you can use it back at the office to drive toward the right outcome.
Techniques for Effectively Slicing User Stories by Naresh JainNaresh 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
GAFANOMICS Season 2: 4 superpowers to outperform in the Network EconomyFabernovel
FABERNOVEL identifies 4 superpowers to outperform in the Network Economy.
FABERNOVEL released a new study analyzing the strategic practices of the GAFA companies. The study, which presents actionable lessons for legacy industries looking to reshape their strategy for the New Economy, finds that the fastest-growing superpowers in the Network Economy position themselves as Magnet, Intimate, Real Time, or Infinite Enterprises.
FABERNOVEL’s 2014 report, GAFAnomics: New Economy, New Rules detailed how Google, Apple, Facebook, and Amazon – GAFA – are driven by a common vision of a borderless market and a customer culture which redefined their notions of value creation, core business, and talent management. FABERNOVEL’s 2015 study builds upon these findings to analyze how other companies are utilizing the infrastructure built by these 4 web giants to spur their own rapid growth.
****
FABERNOVEL vous invite à découvrir dans sa nouvelle étude 4 stratégies inspirées des GAFA pour transformer votre entreprise en champion de l'économie connectée. Venez comprendre comment devenir une entreprise "Magnétique", "Instantanée", "Intime" ou "Infinie" : 4 «super-pouvoirs» économiques inspirés du modèle des GAFA.
En 2014, dans la première étude GAFAnomics®, nous nous étions attachés à analyser les facteurs clés de succès des 4 géants du web. Cette année, notre étude du modèle des GAFA nous a permis d'identifier 4 modèles de performance dans la nouvelle économie, qui permettront à nos clients de repartir avec des stratégies rapides à mettre en oeuvre pour retrouver cette compétitivité dans la nouvelle économie.
Les précédentes études annuelles de FABERNOVEL ont rencontré 10 millions de lecteurs, nous avons hâte de partager cette nouvelle publication avec vous.
The Be-All, End-All List of Small Business Tax DeductionsWagepoint
Read the full article with even more details at https://blog.wagepoint.com/h/i/289427271-the-comprehensive-list-of-small-business-tax-deductions/185037
Class 1: Email Marketing Certification course: Email Marketing and Your BusinessHubSpot
*From HubSpot Academy*
Over the past few decades, people have radically changed the way they live, work and buy. This class will give you an overview of an adaptive, inbound approach to sending emails that provide value and drive growth for your business. It will also teach you about the four big themes of a modern email marketing program: segmentation, personalization, mobile, and optimization.
Why People Block Ads (And What It Means for Marketers and Advertisers) [New R...HubSpot
HubSpot Research shares new data on why people use ad blockers and what marketers and advertisers need to do to keep people from blocking out ads completely. Hint: it's stop using interruptive and annoying ads.
3 Proven Sales Email Templates Used by Successful CompaniesHubSpot
76% of emails never get opened. That makes life for salespeople very difficult. So we've partnered up with Breakthrough Email to bring you email templates that are proven to engage prospects and close more deals. Start using them today and grow your revenue.
The lack of visible female role models is pervasive in the tech industry, particularly on Wikipedia, where just under 17% of Wikipedia biographies were on women. That's why HubSpot wrote fourteen Wikipedia entries for remarkable women in tech to help inspire young women to reach positions at the highest levels of STEM.
How do you create user stories that get your developers excited about a certain feature? Here is a breakdown of all of the components of a solid user story is and how to tell the difference between a good one and a bad one.
If you want to attend any or all of our events in your area, check out our upcoming Product Management workshops here: http://www.eventbrite.com/o/product-school-7016750825
And to request a syllabus or apply to an upcoming course visit our website: https://www.productschool.com
I tried to do this assignment but I didn’t pass – here is the profNarcisaBrandenburg70
I tried to do this assignment but I didn’t pass – here is the professor feedback “Can you please submit all the scripts? I only see few tables created by you. Please create all the required tables and complete all the queries and then resubmit your work” So I need this assignment to be done from scratch. Thanks and see the details below.
Throughout this course, you will be working with a scenario in which some basic background information is provided about a retail store. This information could apply to any retail store in general. Your goal is to select a small-to-medium-sized retail store of your choice, making sure that it is in an industry that you are familiar with or perhaps want to know more about. Each assignment that you complete in this course will be based on the general retail store scenario that is provided and any additional information that you discover during your exploration and problem-solving process. Be sure to refer back to the Discussion Board in Unit 1 as you progress through the problem-based learning (PBL) process. Or, better still, write down the outline that is provided in the Unit 1 Discussion Board as a guide for you to follow throughout the course.
Problem-Based Learning Scenario
A retail store wants to offer its products online in response to numerous customers requesting to be able to purchase the company’s products electronically. The company is beginning to see some growth in spite of the recent economic downturn. The company strives to meet the needs of its customers, including giving them the perception that they are the company’s highest priority. Being a profitable operation has not always been the case, and the company has historically struggled with customer service issues, inventory-management problems, employee turnover, and poor productivity overall. Naturally, the stakeholders of the company began to lose faith in the viability of the company, and unfortunately, numerous stakeholders have dissolved their relationship with the retail store entirely.
Approximately 7 years ago, the company hired a freelance information technology (IT) organization to create a data-driven information system that would support customer records and order entry. The store manager convinced the owner of the company that this route was the way to go. After all, anything would be an improvement over what the company had at the time. The owner felt that because it was important to have an efficient way to track customers and orders, any computerized system would be sufficient. He was not too proud to share his lack of technological skills, and often deferred to others when it came to making decisions in this area. He often joked that perhaps some computer training would do him and his employees some good. He was never really assured that his data were backed up correctly or that his system was secure. And what if the system crashed or the data started to appear unusual? He also had never heard of any of his employees backing ...
This presentation has been successful to assist agile teams who have begun practicing and agile framework involving User Stories but may have developed some less than desirable habits.
The information contained will help those individuals reconsider some of the key elements that make User Stories effective.
Xp 2016 superchargeyourproductbacklogwithuserstories-suzannelazLaz Allen
Presented at xP2016 by Suzanne Morrison and Laz Allen.
Abstract: In this fun, interactive workshop you'll learn how manage your product backlog, write good user stories, split stories, add acceptance criteria and more.The workshop is a combination of theory and practice that alternates between teaching new concepts and techniques, practising them and then debriefing.
In this workshop you'll receive a list of home improvement requirements and you'll work in a group and in pairs to create user stories, critique user stories, use different patterns to split user stories and write acceptance criteria.
At the end of the session you'll have a clear understanding of how to keep your product backlog in good shape using user stories and other Agile techniques.
The workshop has been running at Skyscanner on a monthly basis for over a year and is attended by people in lots of different roles across the company including developers, testers, product owners, marketing managers and designers. Skyscanner is structured using a Spotify inspired squads and tribes model which we have adapted to work with our culture and values. We encourage our squads to self-organise in an agile way and use techniques as appropriate from Agile and Lean.
How to Define Tech Product Pricing Strategy by Salesforce Sr. PMProduct School
What is the importance of defining your product goal and vision and how pricing directly impacts the behavior of your customers? Learn from this presentation.
27 Revenue Model Options B2B (curated by @arnevbalen - Board of Innovation)Board of Innovation
How to find new ways to make money in a B2B context? Explore 27 trigger cards with different business model options and pricing tactics (B2B version). (By Board of Innovation)
Advanced Business Model Design - Pirate Summit 2013Founder-Centric
It's a fallacy that startups have innovative business models. Even when startups use business model innovation tools, they generally don't progress to a level where they are deploying and validating advantageous business model innovations. Here are some more advantanced techniques that work from our experience, working in-depth with 15 accelerators and 3 universities at foundercentric.com
Content prioritization: A method to inform what to tackle first so the user +...Sara Walsh
Learn a simple way to help you prioritize which content projects to work on first so that user needs -- and the content that supports them -- are considered in context of all your business objectives.
I originally presented this at the J. Boye Conference in Philadelphia May 2015; I co-presented it with Elizabeth Carpenter December 2015 at the Chicago Content Strategy Group.
Moving from Business Analyst to Product Owner to Product ManagerKent McDonald
Are you a business analyst who wonders how you can use your business analysis capabilities to be competitive in the job market for the next 3 to 5 years?
As I first noted back in 2017, product owner and product manager roles offer a viable career path for business analysts, especially those who currently work on custom software development projects.
Come to this session to learn about the similarities and differences between business analysis, product owner, and product manager roles. Then discover how you can apply your business analysis experience to becoming a product owner or product manager. Along the way, you’ll hear about the lessons I and others have learned from moving from business analysis through product owner to product management roles.
How to discover the right product to solve the right problemKent McDonald
Have you ever found yourself working as part of a large program with a lot of activity but not much progress? It could be rewriting a 20 year old system, customizing a COTS application, or building a data warehouse.
You may have been told that adopting agile approaches will help you deliver those types of efforts better, faster, and cheaper. You may have also found out that it’s not quite that simple. If you make your delivery process more efficient, you may just be delivering the wrong solution to the wrong problem faster.
Joint Kent McDonald to find out a practical and effective approach to discern if you’re solving the right problem,and discover the right product to address that problem. You’ll learn how to structure your next project to:
* Identify the problem you’re trying to solve
* Make sure the problem is worth solving
* Iteratively discover the right product to solve that problem.
Along the way you’ll learn about and practice a collection of simple techniques that you can use right away.
Learning Objectives:
1) How to use a problem statement to help your team understand the problem you’re trying to solve and determine if it’s worth solving
2) How to use decision filters and story maps to guide your efforts to discover the right product
3) How to use backlog refinement techniques to build a shared understanding of your product
How to Find the Real Need with Socratic QuestioningKent McDonald
A common piece of advice is that your team should discover the true need of your project. Unfortunately advice on how to make that happen isn’t as prevalent. In this session you’ll learn about a simple technique to get to the core of what your stakeholders need that has been around for over 2000 years – Socratic questioning.
Join Kent McDonald as he walks you through a technique aimed at uncovering the (not intentionally) hidden need that your stakeholders are trying to satisfy, without asking “why?” five times in a row. Kent describes the questions, why they work and in what context they work based on his experience with IT organizations and the Agile Alliance. You’ll then have a chance to consider how to use socratic question for a real life situation..
Come learn about this technique so you can use it back at the office to drive toward the right outcome.
Learning Objectives:
* Learn what socratic questioning is
* Learn how to identify your stakeholders needs using socratic questioning
* Determine when Socratic question is an appropriate technique to use
Ok, perhaps I should say that differently. The concept of a stakeholder is problematic.
Technically, a stakeholder is anyone who impacts or is impacted by an organization’s actions or products. That definition of a stakeholder isn’t very helpful if you’re trying to differentiate between customers, users, and those internal folks who have an interest in your product. To keep things straight, I apply the term stakeholders to that third group specifically. Stakeholders play a big part in internal products, so you can’t ignore your stakeholders and you can’t focus solely on them either.
Join Kent McDonald in this Ask Me Anything session focused on working with stakeholders. Kent has spent more years than he cares to admit working with all different types of stakeholders, and now he’d like to answer your questions and (hopefully) help you avoid some of the mistakes he’s made along the way.
So bring your questions about working with stakeholders and Kent will answer them. Anything he doesn’t get a chance to answer during the session he’ll follow up with answers after the session.
Learning Objectives:
Some questions we will most certainly address:
How to know if you’re dealing with a customer, a user, or stakeholder and why that’s important
How to identify the stakeholders you need to deal with and how you should deal with them
How to keep your stakeholders up to speed on what you’re up to.
How to build shared understanding with example mappingKent McDonald
One of the primary responsibilities of business analysts, product owners, and all other product people is to build and maintain a shared understanding of the outcome your team seeks to deliver. Conversations are an effective way to build that shared understanding.
You may find yourself wondering who should be included in those conversations, when do you have these conversations, what should you talk about, and how do you remember what you said?
Join Kent McDonald as he introduces example mapping, a technique that helps you structure your conversations and build a shared understanding.
You’ll learn how to determine the right people to include in your conversations, when the best time is to have those conversations, how to structure those conversations, and how to remember what you said.
How to build shared understanding with example mappingKent McDonald
One of the primary responsibilities of business analysts, product owners, and all other product people is to build and maintain a shared understanding of the outcome your team seeks to deliver. Conversations are an effective way to build that shared understanding.
You may find yourself wondering who should be included in those conversations, when do you have these conversations, what should you talk about, and how do you remember what you said?
Join Kent McDonald as he introduces example mapping, a technique that helps you structure your conversations and build a shared understanding.
You’ll learn how to determine the right people to include in your conversations, when the best time is to have those conversations, how to structure those conversations, and how to remember what you said.
As with everything else related to agile, the nature of the Product Owner role, and whether it is needed at all, depends a great deal on context. As teams discover this, it leads to some common questions:
What do Product Owners Really Do?
Do we even need Product Owners?
Join Kent to examine the Product Owner role and attempt to answer the above questions. He’ll share his experiences and give you a chance to share your perspectives with each other.
By the end of the session, you'll have more insight into the Product Owner role and how it applies (or not) to your situation. This includes an understanding of common organizational models for product owners (including what part of the organization they fit in), how to determine appropriate product ownership responsibilities for your situation, and whether you need Product Owners to have successful product ownership.
How to Find the Real Need with Socratic QuestioningKent McDonald
A common piece of advice is that your team should discover the true need of your project. Unfortunately advice on how to make that happen isn't as prevalent. In this session you'll have a chance to practice a simple technique to get to the core of what your stakeholders need that has been around for over 2000 years - Socratic questioning.
Kent McDonald and Heather Mylan-Mains walk you through a technique aimed at uncovering the (not intentionally) hidden need that your stakeholders are trying to satisfy, without asking "why?" five times in a row. Kent & Heather describes the questions, why they work and in what context they work based on their experience with IT organizations. You'll then have a chance to practice them out to find out about a real project.
The line of questioning was inspired by Brennan Dunn who uses them to understand the true needs of his web development consultants.
Come learn about and practice this technique so you can use it back at the office to drive toward the right outcome.
As with everything else related to agile, the nature of the Product Owner role, and whether it is needed at all, depends a great deal on context. As teams discover this, it leads to some common questions:
What do Product Owners Really Do?
Do we even need Product Owners?
Join Kent to examine the Product Owner role and attempt to answer the above questions. He’ll share his experiences and give you a chance to share your perspectives with each other.
By the end of the session, you'll have more insight into the Product Owner role and how it applies (or not) to your situation. This includes an understanding of common organizational models for product owners (including what part of the organization they fit in), how to determine appropriate product ownership responsibilities for your situation, and whether you need Product Owners to have successful product ownership.
Tis better to be effective than efficientKent McDonald
Better. Faster. Cheaper. Many IT organizations are constantly seeking the "best" practices that will deliver those characteristics, and the fact that they continue to search indicates they haven’t found them yet.
It could be they are looking in the wrong place. Most efforts around achieving better, faster, cheaper center around becoming ultra efficient.
Effectiveness may just be the better target.
Join Kent McDonald to explore the difference between efficiency and effectiveness and learn three simple, yet powerful, techniques that he has found can help teams be more effective. You’ll learn how to:
Build a shared understanding of the problem you are trying to solve
Establish clear guard rails for distributed decision making
Measure progress based on outcome, not output
Along the way he’ll share stories about how he has used these techniques and help you figure out when these techniques may work in your situation.
You may be able to get faster and cheaper with efficiency, but in order to get better outcomes, you need to be effective. Come to this session to learn how.
Do you work at an organization that is "scaling" agile or thinks they need to do "agile at scale"?
Do you find yourself asking these questions:
- What does scaling agile really mean, and is it necessary that we scale?
- If scaling means working with a large team, how do we make sure everyone is moving in the same direction?
- How do we deal with the complications that come with scaling, such as the dependencies that are inherently created?
Join Kent McDonald as he suggests answers to these questions in the form of 3D’s:
- Do "scaling" only when necessary
- Decision making in a complicated environment
- Dependencies and how to deal with them
As we examine these topics, Kent introduces simple, yet powerful techniques your teams can use to be more effective in an environment where scaling seems to be the right answer. You’ll walk away with ideas on how to apply these techniques in your own situation.
Learning Outcomes:
- Use the Context Leadership Model and the Cynefin model to determine if scaling is the right answer
- Encourage informed decision making through Purpose Based Alignment and decision filters
- Minimize dependencies through collaborative planning & consistent communication
What do Scrum Masters Really Do? And do we need them?Kent McDonald
The Scrum Master role is a foundational concept of Scrum, yet like everything else, the role and it’s value should not be fixed. As with everything else related to agile, the nature of the Scrum Master role, and whether it is needed or all, depends a great deal on context. As teams discover this, it leads to some common questions:
* What do Scrum Masters Really Do?
* Do we even need Scrum Masters?
Join Jodi and Kent as we examine the Scrum Master role and attempt to answer the above questions. We’ll share our experiences and give you a chance to share your perspectives with each other. By the end of the session, you'll have more insight into the Scrum Master role and how it applies (or not) to your situation.
After all, the only consistent answer to the above questions is “it depends”.
Have you ever found yourself in a conversation with stakeholders, development team, or both that was going no where? Do you find that the written word never quite conveys what you are trying to say? Are you a believer in the saying “a picture is worth a 1,000 words?” Are you always looking for the closest whiteboard and marker?
You may want to try collaborative modeling.
Collaborative modeling refers to the use of well-known requirements modeling techniques in a collaborative fashion to build and maintain a shared understanding of your problem space and potential solution(s).
Join Kent to explore how to use requirements models as collaborative elicitation and analysis techniques with your delivery team and stakeholders. We won’t necessarily cover how to do create every specific type of model, but we will talk about when specific techniques are the most helpful, and how to use them in a collaborative fashion.
Learning Objectives:
- When specific modeling techniques may be the most helpful
- How to model collaboratively
- Why collaborative modeling is effective
Analysis With an Agile Mindset WorkshopKent McDonald
Analysis is often portrayed as eliciting and documenting requirements, frequently in terms that sound a lot like asking people what they want and writing it down. Analysis is about understanding your stakeholders and their needs, identifying the best solution for satisfying those needs in your particular context, and then building a shared understanding of that solution. Requirements play a part in that work, especially around describing the need, but they are certainly not the end product.
In this session, Kent McDonald will guide you through an approach to analysis in an agile manner. You’ll see examples of techniques that will help you understand stakeholders, context, and needs and then determine and describe possible solutions. You’ll then get an opportunity to try those techniques out on a case study. Along the way you’ll find out how to use analysis to determine if you are doing the right thing and how to determine how much analysis is just enough.
Key takeaways:
- Identify and understand potential users with user modeling.
- Determine the appropriate design approach for your project using the Purpose Based Alignment Model.
- Use decision filters to clearly state the desired outcome of your project and provide team with information for decision making.
- Identify and describe backlog items in more detail using collaborative modeling.
Elicitation and requirements analysis are some business analysis skills that are extremely helpful in an agile setting especially for team members responsible for product ownership. Equally helpful, if not more so, are the skills that teams use to interact with stakeholders, make decisions, and react to actual situations as they arise. The best way to understand the relevance of these skills is to share stories of successful, and perhaps not so successful interactions on real projects and discuss what the team learned. Join Kent as he shares stories from his experiences as Submission System Product Owner and relates the things he learned to useful skills for all business analysts. You’ll get a chance to tell Kent where he went wrong and also consider how to apply the lessons learned in your own setting. Along the way you’ll hear about some techniques for addressing common project situations that work well as long as you get the nuances right.
You have been tapped for an exciting new project. A member of the executive team recognizes that the company needs to transform to meet the evolving needs of your dynamic marketplace. They know that Agile will be part of that transformation, they tap you to lead the effort, and now they think their work is done . While that is exciting and an honor for you, you still need the active engagement of the senior leadership team to create a culture where Agile practices can flourish. The support from the top is critical to drive the type of innovation and flexibility that will be required to successfully implement any new idea – but especially one as (positively) disruptive as Agile.
This session describes how senior leaders need to act differently in an enterprise transitioning to agile, and some helpful patterns individual contributors can use to leverage politics in a positive manner to lead up through influence and help senior leaders make the transition. These patterns are based on Heather and Kent’s experiences at a variety of organizations driving or helping to drive changes including, but not limited to adopting agile approaches. Along the way, we’ll give you a chance to share your thoughts and experiences using politics in a positive (or perhaps not so positive) way to help an enterprise transition to agile.
Anyone Can Write User Stories. It's the (Shared) Understanding That's ImportantKent McDonald
“Who should write user stories?”
“How can I write better user stories?”
When should we write user stories?”
All questions frequently asked. And all questions entirely missing the point.
Just as the *holding* is the most important part of the rental car reservation, the *shared understanding* is the most important part of the user story.
Join Kent to learn how user stories help you build shared understanding of the right solution with your team. Along the way, learn some techniques to address common issues that stand in the way of getting everyone telling the same story.
Learning Objectives:
* Start with value, then identify stories
* One way to stop solutioning
* Dealing with dependencies (that may not be there) within your backlog
* Ways to split user stories into a more manageable size
* Mapping your way to acceptance criteria
Decision Making Techniques for Not for ProfitsKent McDonald
Agile approaches emphasize delivering business value to stakeholders. The concept of business value is a difficult concept to get your arms around, doubly so if you are working in a Not for Profit.
One way to address the problem is to see the idea of business value for what it is – an aid for making decisions. In this talk Kent McDonald describes three simple techniques that you can use to make decisions in your Not For Profit.
Kent describes how to apply the idea of business value to not for profits and shows how you can use three techniques – Real Options, Decision Filters, and Purpose Based Alignment to make decisions in any kind of organization, even Not for Profits.
Estimating in Software Development: No Silver Bullets AllowedKent McDonald
What do poker, Greek oracles, an Italian mathematician from the Middle Ages, and the path of hurricanes have in common? Given the title of this presentation, chances are it has something to do with estimation, and you’ll have to attend this session to get the full connection. Kent McDonald explores the challenges and realities of trying to estimate software-related knowledge work—analysis, testing, development, and the entire project effort. A major challenge is that there are no guaranteed ways to arrive at perfectly accurate estimates, which not surprisingly is why they are called estimates. Kent introduces and gives you a chance to practice quick and practical estimating techniques that will work in different situations—guesstimating, break it down and add it up, and planning poker. Kent has found that these “lite” estimation techniques are almost always just as informative as the ones you just spent six weeks formulating.
Is It Worth It? Using A Business Value Model To Guide DecisionsKent McDonald
One trait of an effective business analyst is the ability to ask the right questions. One “right” question that applies to just about every projects can sometimes be difficult to ask, let alone answer: “Is it worth it?” This question is difficult to answer, because the answer will change as you proceed through the project and gain more knowledge about the purpose, considerations, costs, and benefits involved in a project.
In this session, we’ll explore a tool you can use to help organize the necessary information to answer the “is it worth it?” question on a regular basis. This interactive session will demonstrate how you can create a value model to make an initial decision about whether to pursue a project, and then utilize that model as your knowledge grows throughout the project to revisit the question and confirm whether the project is on the right course, or if changes need to be made.
Topics discussed during the session include:
Structuring your value model to make decisions about whether to do a project
How to deal with non-financial benefits in your Cost/Benefit discussion
Where measures such as NPV, ROI, TCO, IRR fit into the Cost/Benefit discussion.
The impact of timing of implementation on the Cost/Benefit discussion.
Your Digital Assistant.
Making complex approach simple. Straightforward process saves time. No more waiting to connect with people that matter to you. Safety first is not a cliché - Securely protect information in cloud storage to prevent any third party from accessing data.
Would you rather make your visitors feel burdened by making them wait? Or choose VizMan for a stress-free experience? VizMan is an automated visitor management system that works for any industries not limited to factories, societies, government institutes, and warehouses. A new age contactless way of logging information of visitors, employees, packages, and vehicles. VizMan is a digital logbook so it deters unnecessary use of paper or space since there is no requirement of bundles of registers that is left to collect dust in a corner of a room. Visitor’s essential details, helps in scheduling meetings for visitors and employees, and assists in supervising the attendance of the employees. With VizMan, visitors don’t need to wait for hours in long queues. VizMan handles visitors with the value they deserve because we know time is important to you.
Feasible Features
One Subscription, Four Modules – Admin, Employee, Receptionist, and Gatekeeper ensures confidentiality and prevents data from being manipulated
User Friendly – can be easily used on Android, iOS, and Web Interface
Multiple Accessibility – Log in through any device from any place at any time
One app for all industries – a Visitor Management System that works for any organisation.
Stress-free Sign-up
Visitor is registered and checked-in by the Receptionist
Host gets a notification, where they opt to Approve the meeting
Host notifies the Receptionist of the end of the meeting
Visitor is checked-out by the Receptionist
Host enters notes and remarks of the meeting
Customizable Components
Scheduling Meetings – Host can invite visitors for meetings and also approve, reject and reschedule meetings
Single/Bulk invites – Invitations can be sent individually to a visitor or collectively to many visitors
VIP Visitors – Additional security of data for VIP visitors to avoid misuse of information
Courier Management – Keeps a check on deliveries like commodities being delivered in and out of establishments
Alerts & Notifications – Get notified on SMS, email, and application
Parking Management – Manage availability of parking space
Individual log-in – Every user has their own log-in id
Visitor/Meeting Analytics – Evaluate notes and remarks of the meeting stored in the system
Visitor Management System is a secure and user friendly database manager that records, filters, tracks the visitors to your organization.
"Secure Your Premises with VizMan (VMS) – Get It Now"
Gamify Your Mind; The Secret Sauce to Delivering Success, Continuously Improv...Shahin Sheidaei
Games are powerful teaching tools, fostering hands-on engagement and fun. But they require careful consideration to succeed. Join me to explore factors in running and selecting games, ensuring they serve as effective teaching tools. Learn to maintain focus on learning objectives while playing, and how to measure the ROI of gaming in education. Discover strategies for pitching gaming to leadership. This session offers insights, tips, and examples for coaches, team leads, and enterprise leaders seeking to teach from simple to complex concepts.
Large Language Models and the End of ProgrammingMatt Welsh
Talk by Matt Welsh at Craft Conference 2024 on the impact that Large Language Models will have on the future of software development. In this talk, I discuss the ways in which LLMs will impact the software industry, from replacing human software developers with AI, to replacing conventional software with models that perform reasoning, computation, and problem-solving.
Globus Compute wth IRI Workflows - GlobusWorld 2024Globus
As part of the DOE Integrated Research Infrastructure (IRI) program, NERSC at Lawrence Berkeley National Lab and ALCF at Argonne National Lab are working closely with General Atomics on accelerating the computing requirements of the DIII-D experiment. As part of the work the team is investigating ways to speedup the time to solution for many different parts of the DIII-D workflow including how they run jobs on HPC systems. One of these routes is looking at Globus Compute as a way to replace the current method for managing tasks and we describe a brief proof of concept showing how Globus Compute could help to schedule jobs and be a tool to connect compute at different facilities.
How to Position Your Globus Data Portal for Success Ten Good PracticesGlobus
Science gateways allow science and engineering communities to access shared data, software, computing services, and instruments. Science gateways have gained a lot of traction in the last twenty years, as evidenced by projects such as the Science Gateways Community Institute (SGCI) and the Center of Excellence on Science Gateways (SGX3) in the US, The Australian Research Data Commons (ARDC) and its platforms in Australia, and the projects around Virtual Research Environments in Europe. A few mature frameworks have evolved with their different strengths and foci and have been taken up by a larger community such as the Globus Data Portal, Hubzero, Tapis, and Galaxy. However, even when gateways are built on successful frameworks, they continue to face the challenges of ongoing maintenance costs and how to meet the ever-expanding needs of the community they serve with enhanced features. It is not uncommon that gateways with compelling use cases are nonetheless unable to get past the prototype phase and become a full production service, or if they do, they don't survive more than a couple of years. While there is no guaranteed pathway to success, it seems likely that for any gateway there is a need for a strong community and/or solid funding streams to create and sustain its success. With over twenty years of examples to draw from, this presentation goes into detail for ten factors common to successful and enduring gateways that effectively serve as best practices for any new or developing gateway.
Into the Box Keynote Day 2: Unveiling amazing updates and announcements for modern CFML developers! Get ready for exciting releases and updates on Ortus tools and products. Stay tuned for cutting-edge innovations designed to boost your productivity.
Why React Native as a Strategic Advantage for Startup Innovation.pdfayushiqss
Do you know that React Native is being increasingly adopted by startups as well as big companies in the mobile app development industry? Big names like Facebook, Instagram, and Pinterest have already integrated this robust open-source framework.
In fact, according to a report by Statista, the number of React Native developers has been steadily increasing over the years, reaching an estimated 1.9 million by the end of 2024. This means that the demand for this framework in the job market has been growing making it a valuable skill.
But what makes React Native so popular for mobile application development? It offers excellent cross-platform capabilities among other benefits. This way, with React Native, developers can write code once and run it on both iOS and Android devices thus saving time and resources leading to shorter development cycles hence faster time-to-market for your app.
Let’s take the example of a startup, which wanted to release their app on both iOS and Android at once. Through the use of React Native they managed to create an app and bring it into the market within a very short period. This helped them gain an advantage over their competitors because they had access to a large user base who were able to generate revenue quickly for them.
How Does XfilesPro Ensure Security While Sharing Documents in Salesforce?XfilesPro
Worried about document security while sharing them in Salesforce? Fret no more! Here are the top-notch security standards XfilesPro upholds to ensure strong security for your Salesforce documents while sharing with internal or external people.
To learn more, read the blog: https://www.xfilespro.com/how-does-xfilespro-make-document-sharing-secure-and-seamless-in-salesforce/
Listen to the keynote address and hear about the latest developments from Rachana Ananthakrishnan and Ian Foster who review the updates to the Globus Platform and Service, and the relevance of Globus to the scientific community as an automation platform to accelerate scientific discovery.
Exploring Innovations in Data Repository Solutions - Insights from the U.S. G...Globus
The U.S. Geological Survey (USGS) has made substantial investments in meeting evolving scientific, technical, and policy driven demands on storing, managing, and delivering data. As these demands continue to grow in complexity and scale, the USGS must continue to explore innovative solutions to improve its management, curation, sharing, delivering, and preservation approaches for large-scale research data. Supporting these needs, the USGS has partnered with the University of Chicago-Globus to research and develop advanced repository components and workflows leveraging its current investment in Globus. The primary outcome of this partnership includes the development of a prototype enterprise repository, driven by USGS Data Release requirements, through exploration and implementation of the entire suite of the Globus platform offerings, including Globus Flow, Globus Auth, Globus Transfer, and Globus Search. This presentation will provide insights into this research partnership, introduce the unique requirements and challenges being addressed and provide relevant project progress.
Accelerate Enterprise Software Engineering with PlatformlessWSO2
Key takeaways:
Challenges of building platforms and the benefits of platformless.
Key principles of platformless, including API-first, cloud-native middleware, platform engineering, and developer experience.
How Choreo enables the platformless experience.
How key concepts like application architecture, domain-driven design, zero trust, and cell-based architecture are inherently a part of Choreo.
Demo of an end-to-end app built and deployed on Choreo.
SOCRadar Research Team: Latest Activities of IntelBrokerSOCRadar
The European Union Agency for Law Enforcement Cooperation (Europol) has suffered an alleged data breach after a notorious threat actor claimed to have exfiltrated data from its systems. Infamous data leaker IntelBroker posted on the even more infamous BreachForums hacking forum, saying that Europol suffered a data breach this month.
The alleged breach affected Europol agencies CCSE, EC3, Europol Platform for Experts, Law Enforcement Forum, and SIRIUS. Infiltration of these entities can disrupt ongoing investigations and compromise sensitive intelligence shared among international law enforcement agencies.
However, this is neither the first nor the last activity of IntekBroker. We have compiled for you what happened in the last few days. To track such hacker activities on dark web sources like hacker forums, private Telegram channels, and other hidden platforms where cyber threats often originate, you can check SOCRadar’s Dark Web News.
Stay Informed on Threat Actors’ Activity on the Dark Web with SOCRadar!
Cyaniclab : Software Development Agency Portfolio.pdfCyanic lab
CyanicLab, an offshore custom software development company based in Sweden,India, Finland, is your go-to partner for startup development and innovative web design solutions. Our expert team specializes in crafting cutting-edge software tailored to meet the unique needs of startups and established enterprises alike. From conceptualization to execution, we offer comprehensive services including web and mobile app development, UI/UX design, and ongoing software maintenance. Ready to elevate your business? Contact CyanicLab today and let us propel your vision to success with our top-notch IT solutions.
OpenFOAM solver for Helmholtz equation, helmholtzFoam / helmholtzBubbleFoamtakuyayamamoto1800
In this slide, we show the simulation example and the way to compile this solver.
In this solver, the Helmholtz equation can be solved by helmholtzFoam. Also, the Helmholtz equation with uniformly dispersed bubbles can be simulated by helmholtzBubbleFoam.
Multiple Your Crypto Portfolio with the Innovative Features of Advanced Crypt...Hivelance Technology
Cryptocurrency trading bots are computer programs designed to automate buying, selling, and managing cryptocurrency transactions. These bots utilize advanced algorithms and machine learning techniques to analyze market data, identify trading opportunities, and execute trades on behalf of their users. By automating the decision-making process, crypto trading bots can react to market changes faster than human traders
Hivelance, a leading provider of cryptocurrency trading bot development services, stands out as the premier choice for crypto traders and developers. Hivelance boasts a team of seasoned cryptocurrency experts and software engineers who deeply understand the crypto market and the latest trends in automated trading, Hivelance leverages the latest technologies and tools in the industry, including advanced AI and machine learning algorithms, to create highly efficient and adaptable crypto trading bots
Field Employee Tracking System| MiTrack App| Best Employee Tracking Solution|...informapgpstrackings
Keep tabs on your field staff effortlessly with Informap Technology Centre LLC. Real-time tracking, task assignment, and smart features for efficient management. Request a live demo today!
For more details, visit us : https://informapuae.com/field-staff-tracking/
Software Engineering, Software Consulting, Tech Lead.
Spring Boot, Spring Cloud, Spring Core, Spring JDBC, Spring Security,
Spring Transaction, Spring MVC,
Log4j, REST/SOAP WEB-SERVICES.
Prosigns: Transforming Business with Tailored Technology SolutionsProsigns
Unlocking Business Potential: Tailored Technology Solutions by Prosigns
Discover how Prosigns, a leading technology solutions provider, partners with businesses to drive innovation and success. Our presentation showcases our comprehensive range of services, including custom software development, web and mobile app development, AI & ML solutions, blockchain integration, DevOps services, and Microsoft Dynamics 365 support.
Custom Software Development: Prosigns specializes in creating bespoke software solutions that cater to your unique business needs. Our team of experts works closely with you to understand your requirements and deliver tailor-made software that enhances efficiency and drives growth.
Web and Mobile App Development: From responsive websites to intuitive mobile applications, Prosigns develops cutting-edge solutions that engage users and deliver seamless experiences across devices.
AI & ML Solutions: Harnessing the power of Artificial Intelligence and Machine Learning, Prosigns provides smart solutions that automate processes, provide valuable insights, and drive informed decision-making.
Blockchain Integration: Prosigns offers comprehensive blockchain solutions, including development, integration, and consulting services, enabling businesses to leverage blockchain technology for enhanced security, transparency, and efficiency.
DevOps Services: Prosigns' DevOps services streamline development and operations processes, ensuring faster and more reliable software delivery through automation and continuous integration.
Microsoft Dynamics 365 Support: Prosigns provides comprehensive support and maintenance services for Microsoft Dynamics 365, ensuring your system is always up-to-date, secure, and running smoothly.
Learn how our collaborative approach and dedication to excellence help businesses achieve their goals and stay ahead in today's digital landscape. From concept to deployment, Prosigns is your trusted partner for transforming ideas into reality and unlocking the full potential of your business.
Join us on a journey of innovation and growth. Let's partner for success with Prosigns.
Paketo Buildpacks : la meilleure façon de construire des images OCI? DevopsDa...Anthony Dahanne
Les Buildpacks existent depuis plus de 10 ans ! D’abord, ils étaient utilisés pour détecter et construire une application avant de la déployer sur certains PaaS. Ensuite, nous avons pu créer des images Docker (OCI) avec leur dernière génération, les Cloud Native Buildpacks (CNCF en incubation). Sont-ils une bonne alternative au Dockerfile ? Que sont les buildpacks Paketo ? Quelles communautés les soutiennent et comment ?
Venez le découvrir lors de cette session ignite
Providing Globus Services to Users of JASMIN for Environmental Data AnalysisGlobus
JASMIN is the UK’s high-performance data analysis platform for environmental science, operated by STFC on behalf of the UK Natural Environment Research Council (NERC). In addition to its role in hosting the CEDA Archive (NERC’s long-term repository for climate, atmospheric science & Earth observation data in the UK), JASMIN provides a collaborative platform to a community of around 2,000 scientists in the UK and beyond, providing nearly 400 environmental science projects with working space, compute resources and tools to facilitate their work. High-performance data transfer into and out of JASMIN has always been a key feature, with many scientists bringing model outputs from supercomputers elsewhere in the UK, to analyse against observational or other model data in the CEDA Archive. A growing number of JASMIN users are now realising the benefits of using the Globus service to provide reliable and efficient data movement and other tasks in this and other contexts. Further use cases involve long-distance (intercontinental) transfers to and from JASMIN, and collecting results from a mobile atmospheric radar system, pushing data to JASMIN via a lightweight Globus deployment. We provide details of how Globus fits into our current infrastructure, our experience of the recent migration to GCSv5.4, and of our interest in developing use of the wider ecosystem of Globus services for the benefit of our user community.
3. Split Conditions
What This Is
If a story has multiple items listed
in “what” make each a separate
story
When to Use it
Words such as “and” or “or”
appear
Helpful questions
Are all of these conditions
necessary (right now)?
As a Customer, I
want to create an
order and pay for
the order using a
credit card so that
I can get something
to eat
4. Workflow
What This Is
Identify the specific steps in a workflow.
Implement the workflow in stages,
creating multiple stories for the
incremental implementation
When to Use it
The initial story describes a workflow or
process.
Helpful questions
What steps does a user perform?
Are all steps necessary (right now)?
Can steps be simplified (for now)?
As a Customer, I
want to create an
order so that I can
get something to
eat
5. Use Case Scenarios
What This Is
Similar to the Workflow pattern, one
story represents the happy path,
different stories for alternate paths.
When to Use it
The initial story refers to an interaction
described by a use case
Helpful questions
What does the happy/alternate flow
look like?
Are all the alternate flows necessary
(right now)?
Can the alternate flows be simplified
(right now)?
As a Customer, I
want to create an
order so that I can
get something to
eat
6. Operations
What This Is
Splitting a story based on the different
operations done on an entity (Create,
Read, Update, Delete).
When to Use it
The story is about managing or
configuring something
Helpful questions
What operations does the story entail?
Are all the operations necessary (right
now)?
As a restaurant
owner I want to
manage my
restaurant profile
so that people can
order from my
restaurant
7. Zero > One > Many
What This Is
Splitting a story that deals with multiple
instances of an entity into stories that
deal with one instance, and then
multiple instances.
When to Use it
You are working with an entity where
multiple instances are allowed.
Helpful questions
Do we need to be able to handle
multiple instances, or is one instance
sufficient?
As a restaurant
owner, I want to
view a customer’s
order.
8. Core & Enhance
What This Is
Splitting a story to deal with the simple
core conditions and then enhancing the
functionality with additional user
stories.
When to Use it
When the story has a simple core that
provides most of the learning.
Helpful questions
What’s the simplest version of this?
What data types are supported?
What parameters are relevant?
As a customer I
want to see my past
orders so that I can
see what I have
eaten before.
9. Major Effort
What This Is
Splitting a story in a way that requires
substantial effort for the first story and
less effort for all subsequent stories.
When to Use it
When you apply the most obvious split,
any story you do first is the most
difficult.
Helpful questions
Can we create the necessary
infrastructure and deliver value at the
same time?
Does it make a difference which option
we do first?
As a customer I can
pay for my order
with Amex, MC,
Visa, or DC so that
I don’t have to deal
with cash..
10. As a customer
I want to
create an
order with an
item not in
stock
Acceptance Criteria
What This Is
Split a user story into multiple stories to
handle different scenarios in the
Acceptance Criteria.
When to Use it
When the team identifies multiple
scenarios for a story, or accurate, but not
entirely relevant acceptance criteria
identified.
Helpful questions
What tests are used to verify this story?
What acceptance criteria apply?
What scenarios are relevant?
Are all test scenarios necessary (right now?)
As a customer I
want to create an
order so that I can
have something to
eat.
As a customer
I want to
create an
order with an
in stock item.
11. As a customer
I want to view
the menu in
Swahili
Variations in Data
What This Is
The story does the same thing to different
types of data. Create a story for each
option.
When to Use it
When a solution has to support multiple
options.
Helpful questions
Are these options necessary right now?
What is the most common option we need
to care for right away?
As a customer I
want to view the
menu in my native
language so I can
decide what I want
to eat.
12. As a customer
I want to view
pictures of
dish.
Data Boundaries
What This Is
Splitting a story dealing with several
attributes of the same entity.
Support a few key elements first and
introduce remaining data elements later via
additional stories.
When to Use it
When a story is dealing with several
different pieces of data.
Helpful questions
What are the essential data elements we
need to have?
What data elements are not necessary
right now?
As a customer I
want to view menu
item information so
I can decide what I
want to eat.
13. Interface Variations
What This Is
Splitting a story dealing with a complex
interface with addition stories to
incrementally add in complexity.
When to Use it
When the user story deals with a complex
user interface where a simpler one will
work in the meantime
Helpful questions
What is the simplest user interface we can
use?
As a customer I can
view the menu so I
can select what I
want to eat.
14. Platform Options
What This Is
Split a story adding a new user interface by
the various platforms that are applicable.
When to Use it
When adding a new user interface that may
be accessed by multiple different platforms.
Helpful questions
Which platforms are supported?
Are all platforms required (right now)?
Are some platforms more difficult to
support than others?
As a customer I
want to create an
order so that I can
get something to
eat.
15. Business Rules
What This Is
Split a user story so that complex business
rules are handled by separate business
rules.
A special case of this is deferring input
validation to a later story.
When to Use it
When a story has a variety of business
rules, often identified by a large number of
examples.
Helpful questions
What rules apply to this story?
Are all of those rules necessary (right now)?
Can simpler rules suffice (for now)?
As a customer I can
use a credit card to
pay for my order.
16. Role
What This Is
Split a story so that the functionality is
implemented at different times for different
roles.
When to Use it
When a story impacts multiple roles and
the impact is different for each role.
Helpful questions
What roles are involved in this story?
Are any roles necessary now?
As a customer I
want to create an
order so I can get
something to eat.
17. Defer System Qualities
What This Is
Split the story to deliver the necessary
functionality first, then add additional
stories to improve performance, scalability,
usability or precision
When to Use it
When the base functionality does not exist
at all, initial implementation is not that
difficult, the team can learn a lot from it,
and the hard work is in making it better.
Helpful questions
Is it necessary for this to have optimal
performance (right now)?
As a customer I
want to know that
the restaurant
received my order
so that I’m sure I’ll
get some food.
18. Spikes
What This Is
Split the story to allow for some research
and investigation on functionality before
implementing it.
When to Use it
When the team finds they are uncertain
about the implementation of a story and
they need to do some research.
Helpful questions
What are the 1 – 3 questions you have
about the story?
As a customer I
want to see the
menu in the
language of my
choice so that I can
pick something I
want.
19. Low Fidelity/High Fidelity
What This Is
Split the story into a gradual increase of
quality.
When to Use it
When getting to the optimal level of quality
or usability is too expensive to deliver a
solution immediately.
Helpful questions
What is good enough for this
functionality?
As a customer I
would like a
recommendation of
what food to order
so that I can know
I’m getting a good
dish.
20. Transient then Persistent
What This Is
Split stories based on actions to pass data
along and those necessary to save data.
When to Use it
When the story deals with functionality
that includes storing data, but does not
require storing data.
Helpful questions
Do we have to store this data (right now)?
As a customer I
want to use a credit
card to pay for my
order so that I
don’t have to carry
cash.
21. Dummy then Dynamic Data
What This Is
Split stories to first use static data and then
add stories to make the data dynamic.
When to Use it
When the story covers parameters where
the values differ depending on conditions.
Helpful questions
Does the data need to be dynamic (right
now)?
As a customer I
want to search for
menu items.
22. Manual then Automated
What This Is
Split stories that utilize an existing manual
process. Implement the functionality that
does not exist.
When to Use it
When functionality you are developing
interacts with an existing manual process,
develop the functionality but in the short
term, do not automate the manual process.
Helpful questions
Is it necessary to automate the manual
process right now?
As a customer I
want to use multiple
credit cards to pay
for my order.
*Use manual process to
deal with multiple cards
23. Defer Error Handling or Logging
What This Is
Split story so that you focus on functionality
first, then go back and provide functionality
to log errors and handle them.
When to Use it
When you need to gain feedback on
functionality quickly to determine whether
to keep it.
Helpful questions
Is it necessary to deal with exceptions for
this functionality (right now)?
As a restaurant
owner I want to
authorize the
customer’s credit
card payment..
24. Which Pattern to Use
Since there are multiple patterns that can be used
to split the same story, here are three rules of
thumb to guide your selection:
1. Choose the split that lets you deprioritize or
throw away a story.
2. Choose the split that gets you more equally
sized small stories.
3. Chose the split that eliminates or at least
reduces dependencies
http://www.agileforall.com/2009/10/patterns-for-
splitting-user-stories/
25. Additional References
• Splitting User Stories Presentation http://www.slideshare.net/arsenalist/splitting-
userstories
• Splitting User Stories Cheat sheet
https://twitter.com/chrisverwijs/status/335109871802384385
• Breaking Down Larger Stories
http://agileinaflash.blogspot.com/2009/02/breaking-down-larger-stories.html
• Ways to Split User Stories: http://lassekoskela.com/thoughts/7/ways-to-split-user-
stories/
• User Story Hamburger technique http://gojko.net/2012/01/23/splitting-user-
stories-the-hamburger-method/
• Features to User Stories http://idiacomputing.com/pub/UserStories.pdf
• Patterns for Splitting User Stories http://www.agileforall.com/2009/10/patterns-
for-splitting-user-stories/
• Twenty Ways to Split Stories http://xp123.com/articles/twenty-ways-to-split-
stories/
Editor's Notes
Splitting user stories is an analysis technique that produces small vertically sliced user stories.
Smaller user stories are easier to understand
The smaller stories are less complicated, so there is less chance for misunderstanding of what is/is not included in the story.
May find some parts of big story are not needed
If a team splits a story appropriately, the team may find that some of the smaller stories are not essential to delivering the outcome expected from the larger story. For example, if a story was split along different scenarios, some scenarios may not be as relevant, or even happen. Team can save time by not realizing those scenarios.
Smaller stories provide a faster feedback loop
Smaller stories can be delivered sooner, which means the team can get feedback sooner, and if they took a wrong path, they were “wrong for less time.”
Smaller stories help increase progress
The Smaller stories take less time to finish, which means it’s sooner to see progress.
References:
http://blogs.adobe.com/agile/2013/09/27/splitting-stories-into-small-vertical-slices/
Notes:
First increment should implement the first and last steps with future increments adding steps in the middle.
Each increment should meet INVEST criteria.
Notes:
First increment should implement the first and last steps with future increments adding steps in the middle.
Each increment should meet INVEST criteria.
A Second example:
Original Story:
As a customer I want to delete a menu item from an order so that I don’t get food I don’t want.
Split:
As a customer I want to delete a single menu item from my order.
As a customer I want to delete multiple menu items from my order.
Also known as:
Simple to complex
Datatypes & Parameters
Examples of when to use:
Displaying information and then providing filtering/ordering capabilities
Searches to identify searching by different criteria.
Note:
These splits create dependencies, but the way the stories are written makes the dependencies explicit.
Note:
Similar to Core & Enhance.
User story text may be the same but acceptance criteria may differ.
Scenarios Identified:
Credit card is approved
Credit card is declined
Restaurant has item in stock
Restaurant does not have item in stock.
Common examples include localization challenges such as currency and language.
Depending on the nature of the interface, the following options exist from simplest to most complex.
API Only
Character or Script User Interface
Graphical User Interface (Generic)
Graphical User Interface (Custom)
As a customer I want to know that the restaurant received my order – make it work.
As a customer I want to know that the restaurant received my order within 5 seconds – make it fast.
Potential acceptance criteria:
Help team determine if we can do the translation automatically or if we need a separate copy of the menu in several different languages.
This describes the question to be answered by the Spike. This is important to prevent aimless research.
Note:
Also, If a manual process exists for exceptions defer automating those.