Top 5 Techniques for Splitting a User Story

When splitting user stories, we should always split them vertically as if we are slicing a piece of cake. The whole cake is a cake and each vertical slice is a piece of cake with all it’s layers. A horizontal slice might just have the icing, or maybe just the filling, or just the crust and…

0 Comments

What’s the Right Size for a User Story

Product Backlog Items (PBIs) or user stories should be small. Small stories provide focus for the team and gives members the flexibility to adjust and adapt to changes. The larger the story, the higher the risk of team members getting lost in the details and creating bottlenecks as members are busy and unavailable to collaborate and…

1 Comment

Top 3 Reasons to Split a User Story

Here are the top 3 reasons to split a user story: Size – Large user stories need further refinement to break them down into more manageable pieces. Key indicators that a user story is too large are if the estimate is greater than the Sprint duration, or if the estimate is greater than the remaining time…

0 Comments

The 6 Attributes of Effective User Stories – INVEST

Bill Wake came up with the INVEST acronym to help us remember guidelines for writing effective user stories: Independent, Negotiable, Valuable, Estimatable, Small, and Testable. Independent: As much as possible, try to make sure that stories are not interdependent as this might lead to prioritization and planning problems. Independent is different from logical order of developing…

0 Comments

Top 5 Advantages of User Stories

Before we look at why use user stories, let’s first start by looking at other common requirement gathering techniques. 1st, there is the IEEE 830 with “The system shall… “, The system shall do this…, the system shall do that, and my favorite, the system shall be bug free 😊. We typically start out with an…

0 Comments

What is a User Story?

A user story is one way of representing requirements in a Product Backlog. Mike Cohn defines a user story as a simple, clear and short description of customer valued functionality. It is composed of 3 parts: a written description used for planning, conversation to flesh out the details, and tests to determine completeness. Similarly, Ron Jefferies…

0 Comments

10 Essentials for Success in Digital Service Delivery

This post summarizes the Digital Service Delivery blog series by focusing on 10 essentials for successfully using Lean Discovery practices, Agile Delivery techniques and a DevOps mindset to build solutions our customers love. Lean Discovery practices help us ensure that the solutions we are building are not only viable from a business perspective and feasible from…

0 Comments

A DevOps Mindset

To truly succeed in Lean Discovery and Agile Delivery practices and techniques, an organization must adopt an Agile and DevOps mindset. This is more than technical practices to automate our deployments. This requires a culture change aligned with Agile values and principles. This culture change is about focusing on continuously delivering high value working features on a…

0 Comments

Agile Delivery Practices

In the Lean Discovery blog we saw how these practices help us narrow our focus on an MVP and ensure we are building the right thing. Agile Delivery practices help us build the thing right. Moreover, nothing beats true validated learning than having a feature released to a subset of our user base and measuring specific…

0 Comments