Creating Purposeful Scrum Teams via Awesome Backlog
Scrum is a practical framework to build products, provided you identify, in advance, what to build. However, even after a successful product discovery phase, you may struggle to implement 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 and time-consuming process, to an interactive, iterative process that effectively engages team members, customers, and stakeholders. It will teach you how to develop solid techniques to help you build, prioritize, and maintain your product backlog.
Outline/Structure of the Hands on Session
- 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
- Common Pitfalls
- Things That Are Not User Stories
Key learning objectives:
- Creating purposeful backlog
- Beauty and benefit of Feature and story prioritization
- Painting the big picture using the Story Mapping
Product Owners, Product Managers, Business Leaders, Agile Coaches, Scrum Master, Developers, Architects
Prerequisites for Attendees
- Come with an open learning mind
- Ask questions with focus on discovery and learning
- Participate fully in activities - this is a workshop that will take you step by step from idea to a well refined backlog
- Share experiences
schedule Submitted 8 months ago
People who liked this proposal, also liked:
Bibin Mathew / Shijo Paul / Venkateswara Reddy P, CSM - OKR & Agile - Making the best out of bothBibin MathewScrum MasterCisco SystemsShijo PaulAgile CoachConsultantVenkateswara Reddy P, CSMScrum MasterDBS
schedule 8 months agoSold Out!
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 Benefits OKR
- How to use Agile & OKR as a combination
- Get started with setting OKR for some typical scenarios