Application Modernization

Fall leaves

Agile User Story Splitting by Data Variations and Boundaries

Data is another great way to approach splitting User Stories. Variations in data would be something like different options for language or location. Stories based on data boundaries are those that have different attributes for the same entity. Data Variations Let’s revisit my fictional Recipe app. If you recall, we added the ability to view suggested adult beverage …

Agile User Story Splitting by Data Variations and Boundaries Read More »

Water Channel

Agile User Story Splitting by Device, Platform, and Channel

As I think we all know by now, there are countless possible combinations of devices, platforms, and channels that we could end up designing and developing solutions for. I once worked at a retail organization, and they had different Channels like web, mobile, kiosk, and physical stores. Within these, the web team had to contend with the infinite …

Agile User Story Splitting by Device, Platform, and Channel Read More »

Split in ground

Agile User Story Splitting by Business Rules

Before I dig into this story splitting technique, let me give you a quick primer on what a Business Rule is. According to the BABOK®, a Business Rule is defined as: “A specific, predictable, testable directive that is under the control of the business and that serves as a criterion for guiding behavior, shaping judgments, …

Agile User Story Splitting by Business Rules Read More »

Software testing

Agile User Story Splitting by Acceptance Criteria & Test Cases

As I mentioned in one of my previous blogs in this series, when you are writing Acceptance Criteria for a User Story and the list keeps growing and growing (or there are multiple scenarios), then it might be a clue that it’s time to split that story into smaller ones. The same thing applies if you’re writing …

Agile User Story Splitting by Acceptance Criteria & Test Cases Read More »

Remote work

20 Ways to Adapt Agile Best Practices to Remote Work

With COVID-19 disrupting nearly every aspect of daily life, organizations across the United States (and the world) are scrambling to figure out how to handle remote working. I’ve been a consultant for many years, and I’ve almost never worked on a team that didn’t have some sort of remote component to it. In this blog, …

20 Ways to Adapt Agile Best Practices to Remote Work Read More »

looking up at buildings

Microsoft Bot Framework: How to Develop a Bot in Docker Container

Docker image for developing chat bots using Microsoft Bot Framework v4 SDK. This developer base image for BotBuilder V4 should make life easier to isolate the development environment when you shuffle between multiple projects and its dependencies. OVERVIEW In this post, I’ll be sharing about two key things: How to create a new bot in …

Microsoft Bot Framework: How to Develop a Bot in Docker Container Read More »

users on devices

Agile User Story Splitting by User Roles

Different users of your system may have different needs and be able to do different things. This is yet another logical way to try to split stories. First, though, you need to identify the different types of users of your app. In my fictional Recipe app, I’ve already identified a few potential roles through the …

Agile User Story Splitting by User Roles Read More »

path through field

Agile User Story Splitting by Happy / Unhappy Paths & Operations (CRUD)

Good user stories and acceptance criteria will address both happy and unhappy paths of the story. The Happy Path represents the perfect situation where there are few (or no options) and nothing ever goes wrong.
team writing backlog stories

Agile User Story Splitting: Capabilities / User Goals & Workflow Steps

Capabilities/User Goals This seems to be the most obvious approach to story splitting. If you’re just starting out with a vision or big ideas, then you need to figure out a way to make them smaller and more approachable so you can further decompose them into user stories that can be completed within a sprint. What …

Agile User Story Splitting: Capabilities / User Goals & Workflow Steps Read More »

team collaborating on whiteboard

How to Identify Good and Bad Agile User Stories

What Makes a Good User Story? The most common checklist that is applied to identify a GOOD user story was coined by Bill Wake, and it is the acronym INVEST. It stands for: I – independentN – negotiableV – valuableE- estimableS – smallT – testable Let me briefly explain each of these, and how it relates to the …

How to Identify Good and Bad Agile User Stories Read More »

X