Ideal Bite Size - Splitting User Stories
The transition of Waterfall to Agile methodologies is never easy. The Waterfall approach consisted of these documents as a way to analyze the User needs: BRD (Business Requirement Documents), FRSs (Functional Requirement Specifications), SRS (Software Requirement Specifications), PRDs (Product Requirement Documents), etc. After the initial agreements, the development starts. In Scrum, the most important artifact to map User needs is the User Story. However, sometimes, the User Story is too big or too small or too abstract or never ending. This often lands the teams in difficult situations. So, it is vey crucial to Identify the Ideal Bite Size -- to identify the ideal size of our User Stories, yet keeping these Effective!
Outline/structure of the Session
- Introduction of Stories / Importance of being Short and Effective
- Quick Recap of INVEST / 3 Cs model of Stories
- Slicing techniques with Activities
- MOSCOW / KANO – User needs
- CYNEFIN Framework – Measure of disorder
- Dividing the Stories into Workflow steps
- Create Stories for Happy Path first
- Keeping UI simpler and then add frills and thrills
- Improve Performance in iterations
- Starting with Minimal Data
- Confining within Acceptance Criteria
- Divide by User Personas
- SPIKE for Research Stories
- Horizontal Vs Vertical Slicing
- Split by Operations (CRUD)
- Split by Platforms
In this talk, the Audience will become aware of the techniques like MOSCOW, CYNEFIN, Horizontal Slicing, etc, to slice the big and Abstract User stories into Short yet Effective Stories!
Product Owners, Stakeholders, Scrum Masters, Technical leads
schedule Submitted 3 years ago
People who liked this proposal, also liked:
Gurpreet Singh - Top up, Scale downGurpreet SinghAgile Coach / Culture HackerJohnson & Johnson
schedule 3 years agoSold Out!
Every Company is trying to surpass its Competitors in this ever changing World. Today, World is changing so fast, that every company needs to Iterate faster after reading the Customers’ insights. The transition happened from the Industrial Age to the Waterfall Age. The Waterfall resolved the concerns to an extent; however, it laid the foundation for a new set of issues. Then the focus shifted to RUP, Spiral, V models and finally to Scrum, XP, Lean, Kanban, Scaling Agile, etc.
However, no framework or methodology can solve the concerns without having a Good Engineering Culture. The Culture undoubtedly consists of People and the surrounding Processes & Practices to help them (& not act as Blockers) to achieve the ever changing Definition of Success.
In this context, this talk will emphasize to shift our focus from the Leadership-Powerpoint Slides to our Engineering Culture. It will highlight the Problems and an attempt to answer the same by taking good case studies of Companies like Spotify, 3M, etc. We will talk about philosophies like M3.0, Holocracy, Tribal Leadership, etc and Engineering practices like Pair Programming, Continuous Integration, etc. We will also focus on the Roles of PO, SM, Developers, UX and the Leadership to shift to better Engineering Culture for the overall success of the Employees, Teams, Products and the Company on the whole.
Ina a nutshell, this talk underlines the importance of Alignment of Leadership’s Vision with Actual-on-the-ground Engineering Culture to achieve a Win-Win situation.