Are you lost in splitting your User Stories?


SPIDR: Unleashing the Power of User Story Splitting

Splitting user stories can be a challenge. Good thing there are different ways to split a user story and still deliver something valuable.

Enter the SPIDeR Technique. Don't worry. You don't need to be afraid of this spider. It just gives you a way to split user stories.

SPIDR Techniques:

๐Ÿ”Ž Spikes: Learn more about upcoming user stories so you can better split them in the future.

๐Ÿ›ค๏ธ Paths: Split stories on different paths a user can make.

๐Ÿ–ฅ๏ธ Interface: Split stories based on hardware or pieces of the interface.

๐Ÿ“Š Data: Focussing on one data type can help you split the user stories into small valuable increments.

โš™๏ธ Rules: Split your user stories based on business rules that are defined.

Happy splitting!

Jelmar Van Aert

Oostmalsebaan, 13, F, Brecht, Antwerpen 2960
โ€‹Unsubscribe ยท Preferencesโ€‹

Hi! I'm Jelmar a Scrum Master

I write about my Agile learning journey. Writing about the challenges I face and how I navigate this uncertain world showing that work can be different.

Read more from Hi! I'm Jelmar a Scrum Master

Hey Reader ๐Ÿ‘‹, No, not really, but you can apply concepts from PRINCE2 with your team to improve collaboration with stakeholders and freedom - yes, freedom - for your team. What is PRINCE2? First things first, for those who already know PRINCE2, feel free to continue. Else, here's a quick overview. PRINCE2 defines processes to effectively manage a project and stands for PRojects IN Controlled Environments. PRINCE2 is centered around people with their 7 Practices, 7 Principles, 7 Processes, and...

Hey Reader ๐ŸคŸ, Are you working Agile but hating it? Are you feeling fatigued? Agile fatigue is popping up left and right. So let's dive into this topic on what it is and how we can overcome it. What is Agile fatigue? First things first, let's define what I understand of Agile fatigue. โ€œ It's a mental and operational fatigue caused by prolonged exposure to agile processes without any tangible improvement. Symptoms Now that we are on the same line. Let's explore how to recognize the symptoms of...

Poker Planning: Have The Right Estimation Discussions What is poker planning? Poker Planning, also known as Scrum Poker, is an estimation and facilitation method for aligning a team on a user story. The practice is most commonly used in software development, where an estimation of the work has to be done. Why use poker planning estimation? I use planning poker for the following benefits. Usually, within the team, you have strong characters that could take the stage at any time. This is not a...