Writing on product & leadership.

Empiricism, lean thinking, the three pillars, the five values, and Scrum as a lightweight framework — the theory layer every PSK-I question is built on.

One cohesive unit, three accountabilities, no hierarchies. Everything the PSK-I exam tests about the Scrum Team structure, the Product Owner, Scrum Master, and Developers.

The Sprint as container, all five events, every timebox — plus the exact exam traps around cancellation, the three-question myth, and what the Sprint Review actually produces.

Three artifacts, three commitments — and why confusing which commitment belongs to which artifact is the most common mistake on the PSK-I. Deep coverage of the Product Backlog, Sprint Backlog, Increment, and Definition of Done.

What Kanban actually is (and isn’t), its relationship to Scrum, the four practices, the Definition of Workflow, WIP limits as a maximum not a target, and how pull systems work.

The four flow metrics, Little’s Law with worked calculations, all four charts explained (scatterplot, CFD, throughput run chart, aging chart), the SLE, and Monte Carlo forecasting.

How flow metrics slot into Sprint Planning, the Daily Scrum, Sprint Review, and Retrospective — without adding events, changing purposes, or altering Scrum’s structure.

The trap taxonomy, Little’s Law calculation shortcuts, tie-breaker rules, and exam-day tactics. Read this part last — it’s the meta-layer that makes everything else click faster under pressure.

Most PMs use JIRA. Very few can configure it. After years as a JIRA Cloud Admin I’ve seen how proper workflow design and automation rules can cut delivery noise in half.

Running 25–30 accounts taught me that CRM and product ops can’t live in silos. Here’s the 3-layer architecture I use to bridge them.

From my first product role in Retail to running a consulting firm — the things I wish someone had told me on day one.

The framework gives you the structure. Real delivery teaches you when to bend it. Here’s what works in 2026.

When you’re coordinating multiple Scrum teams on one product, Nexus changes the game. Based on real Health and High Tech engagements.