Creating Purposeful Scrum Teams via Awesome Backlog

Scrum is a practical framework to build products, provided you identified in advance what to build. However, even after a successful product discovery phase, you may struggle to make the right thing in the right way if your product backlog is not up to the job. Garbage in, garbage out — as the saying goes.
Managing the product backlog is a full-time and continuous evolution. In this session, we will share Simple techniques that can help change what can be an overwhelming, time-consuming process to an interactive, iterative process that effectively engages team members, customers, and stakeholders. It is essential, therefore, to learn solid techniques to help you build, prioritize, and maintain your product backlog.

Outline/Structure of the Workshop

  • Product Discovery to Delivery
  • Identification – Product backlog items identification
  • Planning, prioritization and investment
  • Backlog grooming techniques
  • What User stories are
  • Users, User Roles and Personas
  • Story Mapping and Story-Writing Workshops
  • Story Sizing and Ruler
  • Adding Detail and defining Acceptance Criteria
  • Dependency Management
  • Release Planning and MVP identification
  • Common Pitfalls
  • Things That Are Not User Stories

Learning Outcome

This Session is a hands-on and practical and we will be working directly with each one of the fellow learners.

  • A variety of techniques to try, as we all know not one-size-fits-all advice
  • lessons that are easy to consume and focus on a specific problem rather than going all out
  • Walk-through examples from practical world with step-by-step learning experience
  • Worksheets to help you apply the lessons to your specific situation
  • Knowing what Product backlog really is, and how to communicate this to team members
  • Having a strong process and foundation for creating a robust backlog and continuous evolve that.
  • Knowing how much detail to include, and when to add this
  • Dealing with Granular level of backlog
  • Splitting user stories so that they are valuable and deliverable in an iteration
  • Spending too much time writing user stories at the cost of developing something

In addition much more.

Target Audience

Product Owners, Product Managers, Business Leaders, Agile Coaches, Scrum Master, Developers, Architects, (If you have only experienced the product backlogs with all items written by the product owner, we’d consider that a very bad sign. You are welcome to

Prerequisites for Attendees

- Come with an open learning mind

- Ask questions with focus on discovery and learning

- Participate completely in activities

- Share your on experiences and more importantly failures and learning.


schedule Submitted 3 years ago

  • Bibin Mathew

    Bibin Mathew / Shijo Paul - OKR & Agile - Making the best out of both

    45 Mins

    Many companies have transformed to Agile from waterfall model in the Past. Recently many organisations are struggling to migrate to OKR (Objectives and Key Results) from Agile. When used correctly, OKR and Agile are a powerful combination. They can create Value-driven teams and transform how organizations work.

    Studies have shown that committing to a goal can help improve employee performance. But more specifically, research reveals that setting challenging and specific goals can further enhance employee engagement in attaining those goals. Google often uses OKRs to try to set ambitious goals and track progress.

    OKR is a goal setting framework and has two components, the Objective (What we want to achieve) and a set of Key Results (How do we know if we are getting there): The main objective of OKR is to create alignment in the organization.

    In waterfall model also we set goals, but it is more of a project Goal /Static Goal. In OKR Modal, High-level goals for the company are set annually and Detailed incremental goals for the teams and individuals set at shorter goal cycles (iterations) that usually last a quarter.

    In this session we will talk about the key benefits of Agile and OKR and how we can make best use of both.

    OKR for this session


    • Enlighten the attendees about the powerful combination of Agile & OKR

    Key Results

    • Key Benefits OKR
    • How to use Agile & OKR as a combination
    • Get started with setting OKR for some typical scenarios
  • Ashish Kumar

    Ashish Kumar - A Confused tester in Agile World- QA a liability or an asset !!

    Ashish Kumar
    Ashish Kumar
    Agile & Lean Coach
    schedule 3 years ago
    Sold Out!
    45 Mins
    Case Study

    A QA Perspective on Agility and Scrum.Focus is mainly on QA role in Scrum,Challenges & Implementation of correct QA process in Scrum.

    This case study is to break the shackles of misconception or a myth that agile development places less emphasis on testing.
    Some QA professionals believe that the quality of software is compromised due to the shortened periods allotted for testing, which results in releasing software that has been only partially tested.
    Some think that with complete automation and continuous integration, the software testing job will become obsolete.
    Contrary to the synchronous activities of a traditional Waterfall project, Scrum expects development activities to be performed in the order they are needed – i.e. asynchronously.
    This break from tradition raises a common question by many of the clients, developers, and business stakeholders new to Agile – “How can testing professionals engage effectively during a sprint before anything has been built?”
    This article focuses on explaining how the QA role performs agile testing and the place of importance they hold on a Scrum team.
    Many think that maybe testers are not at all required and are a liability in the Agile process.

    This study was an attempt to find the truth and myth.

    This is an effort to look into agility and scrum from a perspective of QA. Which is although not a defined but very integral part of an agile team. I have tried to touch upon many bases as QA roles, Process, Challenges and benefits realized. How the different stages of QA contribute to Continuous Integration and Development and enables a Quality product delivery. I have a strong
    belief of learning with Sharing.

    This Study was executed based on survey as well contains some relevant questionnaire based on the topic. It was not limited to following questionnaire.

    1. Is the team cross functional and independent to deliver functional software (story) within a sprint?
    2. Do you have a setup to handle continuous integration and delivery to maintain the pace of delivery?
    3. Are you using Automation to optimize effort and to improve product quality?
    4. Is the deliverable at the end of the sprint / iteration ready to be shipped? (Is there a separate testing phase or deliverable from each sprint is ready to Ship?)
    5. Do you adapt techniques like Mocking Objects, Simulators, and Stubs etc. to take care of dependencies within Sprint instead of waiting for delivery from other team?

    6. In case of distributed team, are there a handshake / stand-up meeting daily with business partner team located remotely?
    7. Are the QA activities part of DOD and are there enough time for it?
    8. What is the ratio of QA to Programmers in Development team?

    For all the above survey questions response, recommendation and suggestions were requested.
    Based on the same model of above questionnaire set this study accumulated some real time data which helped to understand derive data on QA Practices, roles and challenges in Agile organization.
    The study further helps to understand the general QA practise being followed in agile teams and tester’s mind to understand how Scrum enables complex development practices such as CI and CD, and how it influences day-to-day approaches to software development.
    With this case study I would like to share with fellow learners how QA/ tester as individual and practice plays a very important role for successful delivery of Software development and what are the challenges involved.

  • Ashish Kumar

    Ashish Kumar / Shivali Chadak - An Exciting journey from Raw Idea to High fidelity concepts – Let's Discover, Design and Explore !!

    90 Mins

    In today’s hyper-competitive global economy, customer satisfaction is increasingly being driven by software. If we compare the past of software development from today's world It is definitely not the same. Customers is impatient because of available choice of ideas with better quality and reliability is important piece with the innovative faster time to market.

    The session is all about how we can transverse from a Raw idea to high fidelity concept in different phases keeping the market condition and aggressive customer in mind but at the same time our vision for organization is intact and future looking.

    Any simple or however complex it is , solutions and data tend to change over time. Intrinsic human needs do not. People, therefore, are the most constant variables in the design equation. By empathizing with your users and understanding what they need upfront, you can build products they’ll love to use — because your products will be both useful and usable.

    We will uncover that - An Idea is not just what it looks like and feels like. It is all about how it works. At its core, any idea is about solving problems. Efficiently,Effectively, And elegantly.

    This practical session offers a clear framework for you, your team, and your stakeholders to solve complex connectivity design problems — together.