Hands-on Agile #30: Making Your Scrum Work—The Product Backlog Forensic Analysis

PLEASE READ THE FINEPRINT FIRST:

1. You need to RSVP to receive an invitation with includes the Zoom link for the event. (I will not post a Zoom on a public webpage.)

2. I communicate with people who RSVP’ed via Meetup.com’s internal messaging system. Ignore emails from Meetup at your peril. (Pro tip: check your email and notification settings with Meetup.com.)

3. I kindly ask for your understanding that RSVPs will no longer be available after March 8, 2021, for organizational reasons without exception.

4. Newly available seats after closing RSVPs — some people will cancel — will be allocated via the waiting list. (There will be no extrawurst for anyone.)

HANDS-ON AGILE 30:

Forensic Analysis: “Forensic analysis refers to a detailed investigation for detecting and documenting the course, reasons, culprits, and consequences of a security incident or violation of rules of the organization or state laws.”

(Source: https://enterprise.comodo.com/blog/what-is-forensic-analysis/.)

Even if you chose to use Scrum for the right purpose—solving complex adaptive problems and your product quality is high, and the team is self-managing entirely; If your Product Backlog is not actionable, your Scrum Team will be performing at a mediocre level at best—way below its potential.

We will use Liberating Structures to dive into the top-ten Product Backlog anti-patterns and suggest how to fix them.