• Português
  • 简体中文
  • 繁體中文
  • Deutsch
  • English
  • Español
  • Français
  • 日本語
  • Latviešu
  • Lietuvių
  • Русский

Submitted Conference Content

Full name

Gurpreet Singh Chadha

Job Enterprise Agile Coach
email gp [dot] singh [dot] tech [at] gmail [dot] com
Skypeid gsingh1480@live.com
Phone number +5491167890411
Company OLX (Naspers)
Time 45'
Type of Conference Conference > 100 attendees
Level Everybody

Ideal Bite Size - Slicing User Stories


Gurpreet Singh is an Agile Enthusiast with over 8 years experience in coaching Agile, including Scrum, Scaled Agile, XP, to geographically diversified teams. He worked on multiple roles – Product Owner, Scrum Master, Agile Coach – for products ranging from CRM and ERP to US Health Care, Market Research and Mobile Applications. He is working as an Agile Coach in OLX, Buenos Aires, Argentina and is an Active Blogger on Scrum Alliance and contributes in Agile discussions on Linkedin Forums. He loves spreading the word of Agile in Organizations, Conferences and Meetups. Speaker - Conferences: 1) Qcon International Software Conference, Rio, Brazil http://www.qconrio.com/rio2014/presentation/smell-agile-culture.html 2) RallyON Conference, Phoenix, Arizona, US https://www.rallydev.com/rallyon/rallyon2015/sessions/retrospectives-reinvented


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: 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


Markers, flip charts, etc

Benefits for the attendees

In this interactive session, the audience will understand the different techniques to slice the User stories into small, doable and deliverable Business value(s).

Go to the submission page!