Agile in a Flash #4

Role-Playing in Agile – The Idea

Agile in a Flash by Jeff Langr and Tim Ottinger (card #4)

> Customer: Helps define the product

> Programmer: Helps construct the product

> Tester: Helps verify the product works as defined

> Tracker: Helps gather and present useful metrics

> Coach: Helps guide the team to success

> Coordinator (optional): Helps manage external communication

--

In an agile team, everyone helps out, doing whatever it takes to deliver a useful, high-quality product. You are not bound by your job title. A tester might track team metrics, a programmer might help define acceptance criteria, and so on.

The customer has special responsibility and authority, because they are responsible for the product’s functionality and user-facing design. Their supporting cast may include business analysts, product owners, and others who help define the product (including testers), but everyone on the team is responsible for advising the customer.

Programmers (and other technical folks, such as architects and support technicians) are responsible for the internal design, construction, and maintenance of the product.

A coach helps educate and guide your team, shunning command-and-control approaches. They help your team devise their own rules and protocols. The best coaches help teams mature to the point where the team no longer needs them.

We substitute team coordinator for roles like manager, project manager, and Scrum Master. The coordinator buffers the team from outside interference and distraction. They might communicate schedules, handle incoming requests, and smooth interpersonal problems.

LibreOffice kind of sucks...