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!

 
2 favorite thumb_down thumb_up 0 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

  1. Introduction of Stories / Importance of being Short and Effective
  2. Quick Recap of INVEST / 3 Cs model of Stories
  3. Slicing techniques with Activities
  4. MOSCOW / KANO – User needs
  5. CYNEFIN Framework – Measure of disorder
  6. Dividing the Stories into Workflow steps
  7. Create Stories for Happy Path first
  8. Keeping UI simpler and then add frills and thrills
  9. Improve Performance in iterations
  10. Starting with Minimal Data
  11. Confining within Acceptance Criteria
  12. Divide by User Personas
  13. SPIKE for Research Stories
  14. Horizontal Vs Vertical Slicing
  15. Split by Operations (CRUD)
  16. Split by Platforms

Learning Outcome

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!

Target Audience

Product Owner, Scrum masters, Leadership

schedule Submitted 2 years ago

Comments Subscribe to Comments

comment Comment on this Proposal

  • Liked Heather Fleming
    keyboard_arrow_down

    Heather Fleming / Justin Riservato - Stop “Going Agile”! The three conversations you need to have before you start.

    60 Mins
    Talk
    Beginner

    All too often, companies set out with the mission to “go agile” before truly understanding what that means. Business managers are quick to jump on the agile bandwagon, believing that “going agile” will magically make projects happen faster. Teams are getting certified in Scrum as if it’s a silver bullet that will suddenly make everyone more productive. Inevitably, cracks begin to show, and expectations are missed--leaving everyone involved questioning the value of “going agile” altogether.

    There is a better way! The truth is that going agile will result in more productive teams and faster delivery of projects--but only if everyone can agree on the rules of the game.

    Come hear Heather Fleming and Justin Riservato from Gilt discuss why gaining consensus on the principles of Agile is more important than implementing a process, and learn how having these three conversations can save you from an agile disaster:

    • “But when will you be done?”  Why getting rid of the concept of deadlines is the most important (and most difficult) conversation when going agile.
    • “This is my top priority, but I can’t meet with you until next week.”  What to do when your business partner can’t (or won’t) be a full member of the team.
    • “I just want to code. Why do I have to be in all these meetings?”  Why implementing Scrum is not the first step to going agile.
  • Liked Jonathan Hansen
    keyboard_arrow_down

    Jonathan Hansen - Evolutionary Agility with Kanban: Introduction to Kanban for Scrum Practitioners

    60 Mins
    Talk
    Intermediate

    Scrum is by far the dominant Agile methodology and has been put to good use to positively change many software development groups. Some have found that even when they follow all the Scrum practices, they are still having some challenges, and they have turned to Kanban for help. Kanban is often framed as an alternative to Scrum, but it need not be so. Organizations using Scrum can augment their process with the Kanban Method to become more agile and delivery-oriented.

    Jonathan Hansen will use real-world examples, both from product and consulting companies, to show you some of the ways Kanban can work together with Scrum to help you manage the work inside Sprints, manage work that doesn’t fit in Sprints well, and provide a means to continuously improve your work.

  • Liked Laura Burke
    keyboard_arrow_down

    Laura Burke - Using Experiments to Overcome Your Fear of Change

    Laura Burke
    Laura Burke
    ScrumMaster
    Appia, Inc.
    schedule 2 years ago
    Sold Out!
    90 Mins
    Workshop
    Beginner

    Agile prescribes continuous reflection and improvement -- in essence, change. And while everyone fancies change, implementing change can be scary and painful.

    However, most people fear change because they lack the structure and process to approach it, assess it, and then implement it. The key to implementing change is approach it as an experiment where you form hypotheses, collect data, and assess results. While most people relegate experiments to high school science class, they are powerful business tools to help enact change.

    The goal of this session is to introduce three powerful techniques for implementing experiments in any organization. This session will introduce these varied approaches and give the audience experience using them via time-boxed exercises. People will not have an excuse to fear change again!

     
  • Sneha Kadam
    Sneha Kadam
    Business Analyst
    ThoughtWorks
    schedule 2 years ago
    Sold Out!
    60 Mins
    Workshop
    Intermediate

    After revolutionizing the automobile industry, Lean principles have been successfully applied to different knowledge areas including software development. This workshop is intended to master Lean concepts like Waste, Push&Pull systems, systems thinking, Kaizen etc. & practicing cross-functional collaboration, self-organisation and safe-fail experimentation! In this interactive game, the participants will work in a small production lines, experiencing problems and applying Lean practices to overcome them.