Most of us have heard the mantra, "Slice your User Stories as thin as possible!" In my travels as a coach since the early 2000's, however, I've rarely seen stories that truly are thin. What are these rare creatures? Why don't I see more of them? Having good User Stories is crucial to the success of teams using them as the means for determining what needs to be built to fulfill a customer's need. Having thinly sliced stories is even more important!

This workshop provides a level set on what stories are and explores why slicing stories very thin is important, what benefits thin slicing provides, and how to do it. Through a combination of examples and practical application in the workshop, you'll leave with slicing techniques that you can apply at your next planning session.

 
 

Outline/Structure of the Talk

  • Introduction - 5 minutes
  • Quick Review of User Stories - 10 minutes
  • Instructor-led Example of Story Splitting - 20 minutes
  • Group Exercise with Story Splitting 30 minutes
  • Group Exercise Review - 15 minutes
  • Questions - 10 minutes

Learning Outcome

You will leave this workshop with the tools to improve your ability to split stories, even ones that you previously thought couldn't be split! This will provide more granularity to your team's work, improving flow and avoiding blockages.

Target Audience

Product Owners, Product Managers, Business Analysts, ScrumMasters, Developers, QA People

Prerequisites for Attendees

None, although some experience with User Stories would be helpful.

schedule Submitted 1 year ago

Public Feedback


    • 60 Mins
      Talk
      Beginner

      The Product Mindset is the link between the products we build and the culture of the organization that is building them. It's the foundation for operating in a digital economy and creating new insights for success. So what is it, and why should we care?

      There is a shift happening. One that puts the user closer to the center of our work than ever before. We are moving away from the question "Are we building it right?" to asking "Are we building the right thing?" This approach isn't new - it's growing in response to the increasing speed and complexity of competing in today's marketplace. It's founded in human behavior and decision sciences. No matter what you are creating for your customer, there is one thing that unites us: Our customers want products that are simple to use and solve their problem.

      The best tool we have to grow our Product Mindset is a set of principles and techniques known as Design Thinking. This isn't trivial, it's big business. The Design Management Institute's study in 2016 says Design companies outperform others by 211% percent! You know the names; you use the products - companies like Apple, Starwood, Nike, Walt Disney to name a few.


      In this session, we will explore what the Product Mindset is and how to grow it within ourselves and in our organization. We'll identify the questions we can ask to go further than we have before to define value. We'll discuss how to develop products that resonate with our user's emotional needs. And we'll finish with a simple, interactive exercise that applies design thinking to product discovery that you can take back to use on Monday morning. No experience necessary.

      Join us. If we can change the way we think, we can change the way we work.

    • Dave Rooney
      keyboard_arrow_down

      Dave Rooney - #NoBigProcesses - Getting More Done By Doing Less!

      60 Mins
      Talk
      Intermediate

      You may have heard about the #NoEstimates movement, and even #NoProjects. Both of those concepts challenge the assumptions behind two key aspects of delivering software. But what about the process itself? Do we even need approaches like Scrum, Kanban or XP - let alone SAFe, LESS, NEXUS, DAD - in order to be successful? Is following a pre-defined process helpful at all? Is there a simpler way to be effective?

      This session examines the two key principles common to all successful software delivery approaches and builds out based on the experience of the participants. Like #NoEstimates and #NoProjects, the name doesn’t really mean to eliminate process altogether, but rather to build a process that works for your team, in your business domain, with your technology stack.

    • Dave Rooney
      keyboard_arrow_down

      Dave Rooney - Emergent Design with Test-Driven Development

      120 Mins
      Workshop
      Beginner

      This workshop shows how Test-Driven Development (TDD) is used to enable emergent design. Using a simple but representative example in Java, the presenter will demonstrate how a low-level design naturally emerges when using the TDD cycle of test/code/refactor. The audience will be involved by suggesting the next steps and also by pairing with the presenter.

      Note that the goal of the session isn't necessarily to have a complete working example at the end, but to illustrate the process of low-level design through TDD.

    • Tom O'Connor
      Tom O'Connor
      Solutions Architect
      Atlassian
      schedule 1 year ago
      Sold Out!
      60 Mins
      Talk
      Intermediate

      Waste – any work or effort that does not deliver customer value – haunts every organization. In this presentation, we will investigate this paranormal world of organizational waste, learn to see it and acts to reduce it. It is easy to get caught up in our work and day to day activities such that we miss the signs of waste around us. So how do we wade through the volumes of ideas and focus on those that transform and deliver the most value? Agile is in our DNA and we’ve learned how to identify some of the ghosts of waste that many do not recognize. Come join us to explore how we can improve our ability to run more effective meetings, make work visible and execute unique retrospectives to address and reduce waste, so that we focus on the value that every organization can benefit from.

    help