Being Agile

being agile David Sturtz david@davidsturtz.com twitter: @sturtz

Hi. I’m David. Product Manager, Geonetric Information Architect / UX Designer Certified Scrum Master

Many denominations Agile Unified Process, Crystal, Dynamic Systems Development, Extreme Programming (XP), Feature Driven Development (FDD), Lean Software Development, Scrum, etc. I will generally be talking from a Scrum perspective.

Why Agile?

Waterfall… Requirements Design Implementation Verification Maintenance

…or other ‘methods’.

Q: Ought form to derive from the analysis of function? A: The great risk here is that the analysis may not be complete. — Charles Eames

Why Agile? Change is constant. Development is design. Human interactions. Collaboration. Inspect & adapt. Build quality in. Demonstrable value. Aligned with goals.

What is Agile? Project Management Process Leadership Philosophy Engineering Practices Business Approach Jon Strickler, Defining Agile Development

How will we get there? Agile is a project management process. Jon Strickler, Defining Agile Development

Resources Scope Quality Time

Team Backlog ‘Done’ Iteration

Team Backlog 2 weeks to 30 days ‘Done’ fixed goalpost Iteration

Scrum Stand-up 24 hours Product Backlog Sprint/Iteration 2 weeks to 30 days Sprint Potentially Backlog Shippable Increment Adapted from Mountain Goat Software

planning Team Backlog daily stand-up ‘Done’ review Iteration retrospective

The Scrum Board To Do ∂ In Progress ∂ Complete ∂ Accepted

The Burndown

Who is in charge? Agile is a leadership philosophy. Jon Strickler, Defining Agile Development

Team Backlog team members ‘Done’ scrum master product owner Iteration

7±2 Team Backlog committed ‘Done’ co-located cross-functional Iteration self-organizing

Inspect and adapt “Agility might be said to be about encountering all the problems so early and so often that the e fort to fix them is less than the pain of enduring them.” — Ron Jeﬀries

When are we finished? Agile is a set of engineering best practices. Jon Strickler, Defining Agile Development

Team Backlog demonstrable value ‘Done’ definition of ‘done’ team owns quality Iteration

Slices, not layers

Done-done. “If we’re not shipping our software when it’s ready, it’s poor business practice. If we’re not sure whether our software is ready, it’s poor software practice.” — Ron Jeﬀries

What are your priorities? Agile is a business approach. Jon Strickler, Defining Agile Development

Team Backlog user stories ‘Done’ acceptance criteria prioritized Iteration

The User Story As a USER I want GOAL so that VALUE

Strategy Executive Years Team Portfolio Product Product Management Planning Release Months Iteration Development Team Daily Hours Adapted from Rich Mironov/Enthiosys Planing Time Horizons

Fail early, fail often. “By far the dominant reason for not releasing sooner was a reluctance to trade the dream of success for the reality of feedback.” — Kent Beck

Team Backlog ‘Done’ Iteration

What is Agile? Project Management Process Leadership Philosophy Engineering Practices Business Approach Jon Strickler, Defining Agile Development

What is Agile? “Simplicity does not precede complexity, but follows it.” — Alan Perlis

being agile David Sturtz david@davidsturtz.com twitter: @sturtz

Being Agile

by David Sturtz on Feb 10, 2010

Accessibility

Categories

Tags

Upload Details

Usage Rights

3 Embeds 15

Statistics

Being Agile — Webinar Transcript

http://www.davidsturtz.com	7
http://davidsturtz.com	6
http://www.slideshare.net	2