Executive Level Tracking for Agile Projects

8

Click here to load reader

description

This deck provides the theory and execution for tracking agile projects with predictability and precision.

Transcript of Executive Level Tracking for Agile Projects

Page 1: Executive Level Tracking for Agile Projects

Executive Level Trackingfor Agile Projects

(Theory and Execution)

Elliot Susel, Agile Project Manager

Page 2: Executive Level Tracking for Agile Projects

Flexibility from agile is great…

But how the heck do I track and plan through uncertainty?

Page 3: Executive Level Tracking for Agile Projects

Conflicting Interests

What Executives Want vs. Agile Methodology

Big picture understandingof features

Smallest possibledecomposition of features

Set deadlines andrelease dates

Select content only at thestart of a sprint

Page 4: Executive Level Tracking for Agile Projects

The Solution?

Map the details back to thebig picture

Page 5: Executive Level Tracking for Agile Projects

Story Maps

Visual representation of the big picture (content and timeframes)

Display costs of features

Page 6: Executive Level Tracking for Agile Projects

Nice theory…

But how exactly do we execute on this?

Page 7: Executive Level Tracking for Agile Projects

Building a Story Map

Add tracking in your backlog for “Epic” and “Feature Group”

Trace all User Stories up to Epics Trace all Epics up to Feature Groups

Use velocity to determine feature completion dates

Prioritize the backlog Calculate the total point cost per epic and feature group Use prioritization, point costs, and velocity to calculate completion

Page 8: Executive Level Tracking for Agile Projects

Questions?

[email protected]

online presence:about.me/ElliotSusel