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.
 
3 favorite thumb_down thumb_up 2 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the 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

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, many, many more.

Target Audience

Product Owners, Product Managers, Business Leaders, Agile Coaches, Scrum Master, Developers, Architects, (If I saw a product backlog with all items written by the product owner, I’d consider that a very bad sign.)

Prerequisite

- Come with an open learning mind

- Ask questions with focus on discovery and learning

- Participate fully in activities

- Share experiences

schedule Submitted 8 months ago

Comments Subscribe to Comments

comment Comment on this Submission
  • Vishal Prasad
    By Vishal Prasad  ~  8 months ago
    reply Reply

    This should be under building agile teams track.

    • Shijo Paul
      By Shijo Paul  ~  8 months ago
      reply Reply

      Thanks Vishal for the comment. 

      As per confengine, "Emerging Technologies & Agility – APGI is always excited to take up this hot topic that covers the role of Agile in emerging technologies like SMAC, IoT, Design Thinking, User experience Design, CI, CD, and DevOps. There may be a touch upon a few Product Management related topics too." As our topic was falling more into "Product Management related topics", we went with this track.


  • Liked Tathagat Varma
    keyboard_arrow_down

    Tathagat Varma - The impact of "Triple A: AI, Analytics and Automation" on the Future of Work

    Tathagat Varma
    Tathagat Varma
    Founder
    Thought Leadership
    schedule 8 months ago
    Sold Out!
    30 Mins
    Keynote
    Intermediate

    Coming Soon!

  • Liked Srinivas C
    keyboard_arrow_down

    Srinivas C / Dan R Greening / Payal Dev - ScrumMaster Master Class

    90 Mins
    Workshop
    Advanced

    ScrumMaster who take their role seriously are beset with difficulties. As a process Owner and problem solver, the issues are many and systemic fixes needed. So what can/should they do? As with many other competencies, problem solving needs practice. Here we confront a fictitious case-study (based on two real projects) with help from India's first Scrum coach. As he takes you through the thicket of a complex situation (aren't all real situations complex, and not just "complicated"?) you will get a series of in-depth example SM situations. Further a moderated discussion on how to handle them. Some will be your own. This will be different from a Certified Advanced ScrumMaster class, this doesn't have much coaching content, but a strong problem solving slant.

    NOTE: Case study here is of a "cummulative" type, which allows drawing wider lessons based on familiar common experience. The situation is meant to illustrate common (and one or two not so common) problems and their treatment.

  • Liked Nilesh Kulkarni
    keyboard_arrow_down

    Nilesh Kulkarni - How to get more out of your agile transformation journey.

    120 Mins
    Hands on Session
    Intermediate

    Many organizations are introducing agile transformation programs or maturing their existing programs. However overall business outcome of the transformation journey is not substantially high. While there could be many reasons for this, one of the major reason is focus on transformation of one small unit in entire organization - called product development. This session will help the attendees to understand what is business agility and how to rethink your enterprise agile transformation strategy for greater business outcomes.

  • Liked Vishal Prasad
    keyboard_arrow_down

    Vishal Prasad - The Grand White Elephant One Day Project Kick-off

    45 Mins
    Talk
    Advanced

    One of the most widely used Scrum anti-patterns is the infamous Sprint Zero. This iteration is used by many teams across the globe as a period for homework activities before kicking off a project. Activities may typically include backlog refinement with the product owner, setting up development environments, reading deployment pipelines, applying logging frameworks, etc.

    It has been mentioned multiple times by the innovators of the Scrum Guide that it shouldn't take more than a day to begin a project, alas as the Scrum Guide mentions, Scrum is simple to understand, difficult to master; and the difficulty increases exponentially as we scale. So here's a workshop to master a one-day project kick-off using an extension of the white elephant exercise which I like to call - the Grand White Elephant for scaled teams.

  • Liked Sharmila Patwardhan
    keyboard_arrow_down

    Sharmila Patwardhan - Entrepreneur mindset for Agile teams

    45 Mins
    Talk
    Intermediate

    While most of the agile teams struggle to have "ownership" from their team members, how can we establish Entrepreneur mindset and how will it really benefit the teams is the real question.

    This session is to explain what Entrepreneur mindset is and how it can help Agile teams

  • 45 Mins
    Case Study
    Intermediate

    Every organisation hopes / expects / demands high performance from their employees and teams. It's not very long ago when most effective organisations in the world had a ritual called yearly goal - setting. Many organisations still continue with this where the HR cascades a set of goals set by the organisation's leaders for their employees. This is usually followed by a quarterly to yearly review cycle which with most organisations are linked with incentives. In general terms, there ain't any flaw with this system; goal setting is an efficient way to continuously improve oneself. However, the execution of this process may be flawed and may lead to unoptimized results.

    With the advent of business agility, this focus shifted towards continuously learning & improving organisations. This meant that faster feedback was highly recommended for performance improvement and the idea of year-long goal setting seemed a talk of the yesteryears. Many organisations embraced this change by completely abolishing the yearly goal setting practice and instead relying on mentor relationships for an individual's performance improvement. This did improve relationships at the same time hindered transparency since the organisation goals were no longer directly accessed by every employee.

    When seen from the perspective of game theory, it's evident that optimum results are obtained when employees achieve goals which are highly beneficial to them at the same time aligned with the organisation's goals. With the former approach explained above, it's pretty clear that the employees in the first case were aware of the organisation's goals, even if the goals were not aligned with their personal goals. Whereas in the latter case, the lack of transparency meant that the individual's goals were highly focused and may not be in-line with the organisation's objectives.

    This is where Performance Kaizen aligns these two systems with a flavour of Management 3.0 in order to create an optimum setup where high performing individuals, teams, and organisations can thrive. In this session, we present a case study of this implementation at Springer Nature along with our results and learnings; followed by a brief hands-on exercise for the attendees.

  • Liked Ritabrata Moitra
    keyboard_arrow_down

    Ritabrata Moitra - The Why and How of Trunk Based Development

    45 Mins
    Talk
    Intermediate

    Background

    A variety of branching strategies exist in the delivery universe as of date. Having worked with multiple of these, in my personal experience, I have explored the pains and gains that each of these strategies have to offer. While there are certain situations or delivery patterns that might make a certain strategy a better fit, in my experience, Trunk Based development usually is the most sane way of writing, maintaining and delivering production code.

    Approach

    Trunk Based development is a source-control branching model where developers push code ( of all possible features that are in development ) on to a single remote branch, referred to as the trunk. Developers at all costs try and resist the urge to create other long-lived development branches. This is important because developers, including myself, are mostly lazy. So if there is something that can ease their lives off today, they would rather do that knowing that they are up for a hard day in the future. This is mostly the paradigm of not developing on the trunk. Branching by features makes it easy for development teams in the shorter run. However a developer is well aware that he is going to stay up late in office the moment his project manager says that the code he has written on the trunk has to be released. What follows is merge hells, integration nightmares, bugs, angry developers and divorces.

    Findings

    In my career, I have worked with a bunch of branching strategies up and until now. While it is indeed easier in the shorter run to create feature or team-specific branches, it is almost always a painful and tedious job to bring things back into the master in order to release. Also in my opinion, other branching strategies defeat the entire purpose of Continuous integration since not ALL the code that is being written is being tested in unison.

  • Liked Chandan
    keyboard_arrow_down

    Chandan - AGILE COACH AS A PSYCHOLOGIST OR BECOMING A PSYCHOLOGIST

    Chandan
    Chandan
    Enterprise Agile Coach
    Shell
    schedule 9 months ago
    Sold Out!
    45 Mins
    Talk
    Advanced

    We are in business of building software with the people, by the people and for the people.

    We need to build expertise to know people, understand people (Consumer behavior).

    How? We as an agile coach, what skills we should have to acquire such level of mastery through which we can be effective in change management.

    Coaching, is meant to help “healthy” clients, but instead of helping them solve problems, coaching focuses on helping persons utilize their abilities more effectively than they have previously.

    In my journey of Agile coach role for last 7 years I have read most of the materials related to Psychology. If we read more about Psychology the resultant outcome is enormous. It is advantage for self-development and developing others also.

    I have been coaching from last 7 years, I have coached more than 200+ team members, I have interacted with more than 400 + agile coaches, and I have taken more 100 + hrs. of Agile training. All these experience inspiring me that more and more we are maturing, we are becoming a Psychologist. We are becoming life coach where team members comes to us and share their challenges, personal challenges, they are trusting us. Most of the time various psychological techniques helping coaches to connect with the team members at much deeper level.
    I will be happy to share various models and techniques which is working for me and they are proven and should be work for anyone. We will talk more about positive psychology and its effect on team coaching.

  • Liked Siddharth Kulkarni
    keyboard_arrow_down

    Siddharth Kulkarni - Dr Culture Shock - Or How I stopped worrying and embraced Org Culture

    45 Mins
    Talk
    Intermediate

    The org culture mantra is usually considered a silicon valley mumbo jumbo. Although many companies and teams rant about culture, very few in my opinion take it seriously. In this talk I would like to discuss the importance of Org culture and how it makes or breaks businesses and teams. I will lay out some key pointers that will help the influencers in the audience make decisions about their org or team culture. The talk will be in the context of culture in tech companies.

  • Dan R Greening
    Dan R Greening
    Managing Director
    Senex Rex
    schedule 8 months ago
    Sold Out!
    180 Mins
    Workshop
    Beginner

    Agile isn't just for software, it's for your thing, whatever that is. In my keynote talk, Agile for Everything, I introduced six fundamental patterns that comprise Agility. They apply not just to software, but to virtually any situation where rapid adaptation can improve success.

    In this workshop, I'll teach and coach you to apply those six principles to your thing. "Your thing" might be marketing, UX design, software, finance, hardware, business development, product management, your company, your family, your career, a classroom, your education, your kids' education, an art project, or building a house. Or it might be something else.

    You gain two ways attending this workshop: First, you will get coaching help in achieving "your thing," whatever that is. Second, you will gain an intuitive, visceral understanding of agility—its strengths and limitations, its nuances and quirks. That understanding will help you rapidly assess agile opportunities and dangers, and will help you teach and coach in more fruitful ways.

  • Liked Sunil Mundra
    keyboard_arrow_down

    Sunil Mundra - The Elephant Can Dance

    Sunil Mundra
    Sunil Mundra
    Principal Consultant
    ThoughtWorks
    schedule 8 months ago
    Sold Out!
    45 Mins
    Case Study
    Beginner

    Agile Transformation Journeys are difficult, long and uncertain. They need patience, perseverance, conviction, commitment and an unwavering focus on outcomes. It is therefore not surprising that as of now there are few known instances of successful Agile Transformation. For organization which are intending to commence a Transformation and also those who are doing it, the lessons learned from successful and not so successful transformations should prove highly valuable.

    The speaker will showcase 2 contrasting case studies, one a failure and the other a success in agile transformation, to bring out the key variables that determine success or failure in Agile Transformation. The speaker will offer practical recommendations on enablers for successful Agile Transformation.

  • Liked Ankita Mathur
    keyboard_arrow_down

    Ankita Mathur - Creating a successful product for the emerging IPTV platforms

    45 Mins
    Talk
    Intermediate

    Ever wondered how Netflix works? And what it takes to create a successful video streaming platform from scratch? How to create a full fledged product for the emerging IPTV platforms, create a brand value and earn as well.

    There are various aspects which we can touch, starting from the notion of creating such a product, how data is collected and streamed, how Machine Learning and Artificial Intelligence change the entire landscape, and how to measure.

    It will be a mix of technical aspects and business details, so to make everyone aware of a great opportunity that exists for developers and for companies!

  • Liked Shivali Chadak
    keyboard_arrow_down

    Shivali Chadak / Ashish Kumar - Big O of RetrO - Retry Out of the box !!

    90 Mins
    Workshop
    Intermediate

    Retrospective is the heart of scrum and agile world. We need to ensure this heart is well connected to other parts and functioning well. Getting the right amount of inputs and making sure with the right outcomes. This workshop will be an eye opener to understand anti patterns of retrospective. It will be more of a hands-on exercise for all the attendees based on our experiments which we have conducted got benefited. Will help to practice an effective retrospective which enables the team to seize opportunities to improve. Retrospectives can become monotonous and boring over time and so they become ineffective. We need to bring something new, fun, or exciting to the retrospective to make it lively.

    This workshop will lead a way as a food for thought for scrum practitioners. Why it is important to ensure that each team member is comfortable participating and sharing thoughts and ideas requires that the Retrospective be conducted with an atmosphere of respect, honesty and positivity. Retro facilitator who contributes structure and process to a Retrospective to help the Scrum Team identify and bring about an outcome that is consistent with the Team’s objectives.

    Will also cover the aspect as how a Retrospective lacking a Facilitator will suffer problems similar to a team-based sporting event lacking a referee. Retrospective should be facilitated in a healthy and fun way, team level engagement should be taken on priority. Retro outcome apart from the action items team should look forward to participate and leave a mark.

    Successful retrospection responsibility who ensure, is it team or scrum master or both? Together teams need to think outside the box when approaching Sprint Retrospectives and appreciate that these short gatherings need not to be done only by using the usual techniques or methods. Instead they can bring their own ingenuity, knowledge, and experiences to the table to create games or to start meaningful discussions that the team drives.