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 very crucial to Identify the Ideal Bite Size -- to identify the ideal size of our User Stories, yet keeping these Effective!


Outline/Structure of the Workshop

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

Learning Outcome

This workshop will help the audience to understand the fine prints to slice big requirements into 'effective' and 'deliverable' user stories.

Target Audience

Product Owners, Agile coaches, Scrum masters, project managers

schedule Submitted 5 years ago

  • 45 Mins

    The retrospective is one of the most powerful Agile ceremonies. They require you to learn from your experiences and challenge you to continuously improve.

    In this interactive session, you’ll explore retrospectives in depth, including activities to bring out different personality types and patterns for different levels of team maturity.



    Scrum has gifted a few Scrum Ceremonies to the world: Sprint Planning, Daily Standups, Backlog Grooming and the Sprint Retrospective. The Retrospective is one of the most important and the most powerful Ceremony.

    Retrospectives are required to learn from the experience and improve upon. To he ever-growing competition, the Organizations need to learn a lot from their experience and change accordingly (Charles Darwin: Survival of the fittest).

    If it is performed well, it can yield wonderful outcomes to improve anything/everything.

    Over a period of time, the teams start feeling bored about the same Old Retrospective (Glad, Sad or Mad, etc) so a lot of Fun/engagement part needs to be added to the same.

    In the current times, Retrospectives need a rebirth otherwise Retrospectives will die and the Learning curve will die as well!

  • 45 Mins
    Case Study

    Culture is the most widely talked in societies, religion, race, region and workplaces as well. Organizations are the Second Homes as people spend their better half of their time in their offices. Hence, Culture is an integral part (good or bad) for driving the happiness of clients and the colleagues, and success for the products/projects and growing / sustaining business. Agile Implementation is highly dependent upon the Culture of the Organization.


    How does a Manager transition to the Role of a Product Owner? What happens to a Product Owner who wants to retain his control on the team rather than working on the Product? Some developers think that Scrum, for instance, brings a lot of meetings and these meetings are a waste of time. The Scrum Master’s role is not a full time role in many companies. Leadership thinks Agile can solve most of their issues without even knowing the root causes of the issues.


    Come to this talk and we will discuss a selection of real-life experiences to tackle these cultural issues and the actual/suggestive steps taken to improve the culture of organizations.


    Presented at Qcon Rio International Software Conference: