About The Epic Slicer
Purpose
This tool teaches software practitioners how to write effective user stories from epics using the Japanese martial arts learning methodology of Shu-Ha-Ri. The goal is to develop skills in creating user stories that deliver genuine business value while following proven structural patterns.
⚠️ Important Notices
Training Use Only: This tool is designed for learning and practice. Do not use it to create stories intended for production release.
No Personal Data: Do not enter personally identifiable information (PII) or sensitive data. All inputs may be logged for training analysis.
Data Collection: We log story attempts and feedback interactions to improve the tool. No identifying user information is collected.
How to Use This Tool
🎯 Stage 1: Shu (Show Good)
Study well-crafted user stories to understand structure, role specificity, and business value. Learn by observing examples that follow best practices.
🔧 Stage 2: Ha (Make Better)
Practice improving flawed user stories. Each story has specific issues to address - weak descriptions, poor acceptance criteria, or both. Edit and get feedback on your improvements.
✨ Stage 3: Ri (Create Your Own)
Create original user stories from scratch. Apply everything you've learned to write compelling stories that deliver clear business value. Validate your work using the INVEST criteria.
The Shu-Ha-Ri Learning Method
Shu-Ha-Ri (守破離) is a Japanese concept from martial arts that describes the stages of learning mastery:
- Shu (守) - "Protect/Obey": Learn by following the rules and imitating examples exactly
- Ha (破) - "Break": Begin to break the rules and find exceptions, modify and improve
- Ri (離) - "Leave/Separate": Transcend the rules and create your own way
This progression ensures deep understanding before creative innovation, making it ideal for learning complex skills like user story writing.
The INVEST Principle
User stories are evaluated using the INVEST criteria, developed by Bill Wake in 2003:
- Independent - Can be developed and tested separately
- Negotiable - Details can be discussed and refined
- Valuable - Delivers business value to users
- Estimable - Development effort can be reasonably estimated
- Small - Fits within a single iteration/sprint
- Testable - Clear criteria for testing completion
This tool focuses primarily on Value, Structure, and Testability aspects of user stories.
About the Creator
This tool was created by Anne-Marie Charrett, a pioneering voice in modern quality engineering who has shaped how teams think about quality practices in software development.
Anne-Marie is recognized for her innovative concepts in quality engineering and quality coaching, advocating for a modern engineering approach where quality is everyone's responsibility—not just testers. She champions the shift from traditional testing roles to quality engineering practices that integrate seamlessly into development workflows.
Key Contributions to Quality Engineering
- Quality Coaching Framework - Developed comprehensive approaches for mentoring engineers in quality practices
- Modern Testing Philosophy - Promoting quality engineering as a discipline for all engineers, not just dedicated testers
- Practical Quality Tools - Creating hands-on learning experiences that bridge theory and practice
Resources & Publications:
- Quality Coach - Comprehensive resources and training for quality coaching
- The Quality Coach Book - A comprehensive guide to quality coaching practices and frameworks
- Quality Coach Course - Structured learning program for developing quality coaching skills
- Industry Speaking & Writing - Regular contributor to conferences and publications on quality engineering evolution
Why this tool?
Story slicing is an art, and teams often forget to focus on business value and outcomes. Without this focus, stories get written according to front-end, back-end, and design boundaries, resulting in handoffs and a lack of focus on what actually matters to users and the business.
This tool helps practitioners understand and learn how to create well-written stories that directly impact quality. When user stories focus on business value rather than technical implementation, several critical benefits emerge:
- Better Testing - We can test for business value earlier in the development cycle
- Reduced Assumptions - Less chance of misunderstandings between designers, front-end, back-end, and QA teams
- Collaborative Focus - Everyone works on the same story together, rather than in silos
- Quality Outcomes - Stories become bridges between user needs and measurable business results
The tool emphasizes that good user stories aren't just well-formatted text—they're strategic tools that drive quality outcomes by keeping teams focused on business value rather than technical implementation details.