Practicing Scrum

Agile training notes from a Scrum workshop by Ron Lichty.

Aug 27, 2019 · 5 min read

I recently attended an Agile training by Ron Lichty. These notes are my attempt to digest and process this outstanding Scrum workshop, focused on delighting customers and team happiness for our Engineering and Product teams.

Defining Scrum

Scrum is an Agile process framework for teams of less than 10 members. Teams break their work into goals that can be completed within timeboxed iterations, called sprints (usually two weeks). They track progress and re-plan in 15-minute timeboxed stand-up meetings, called daily scrums.




“The point is not to do Agile. The point is to be effective. Agile provides us insights.”

Al Shalloway, agile author


Ideal team

Definition of done

Project planning

Snake sizing / two-pass relative sizing

Product business value sizing

Product Backlog Items (PBI's)

Backlog

Sprints

Sprint planning

User stories

Technical debt stories

Agile disciplines

Standups

Sprint Retrospectives

Scrum ceremonies and events

Project Workflow

Stage Product / Overall Technical
Listing: Epics and stories user PBI Technical PBI
Sizing: Snake sizing, two-pass relative sizing
Ordering: ROI/Dependencies/Risk Urgency/Risk
Integrating: 1-2 backlogs with 2 1/2 sprints detailed
Planning: Sprint Plan, team pulls from 1 or 2 backlogs

Focus on what matters the most

  1. Delight customer
  2. Team happiness


“Do as little [design, code, requirements, testing, QA] as possible, and no less.”

John Steele


Visit homepage
comments powered by Disqus