Agile Fundamentals

Overview of fundamental agile principals and background information.
http://www.meetup.com/AgileCommunity-Canberra/events/112428842/

Transcript

1. AGILE CANBERRA MEETUP AGILE FUNDAMENTALS
2. ABOUT ME • Sean Wilbur • @sgwilbur • about.me/sgwilbur
3. AGILE INTRODUCTION • Introductions • Agile Origins • Common Flavors • Scrum • XP • Lean • KanBan • Scrum Water-Fall / Agile+ / <insert market term>-agile
4. BEFORE AGILE • Traditional methodologies were mainly around predictive approaches • Provides the ability to plan and act • Clear boundaries and gates to progress ( focus on tools and process) • Lack of transparency • Large amount of upfront work required • Limited chances to review "finished" work • Detailed plan needs constant updating
5. WHISPERS OF SOMETHING BETTER • Various disciplines in manufacturing and engineering have grappled with this problem and started the notion of iterative approaches • In the 1980's the successful work from Japanese auto makers helped to influence other industries, the notion of "Kaizen" becomes mainstream • 2001 the current generation of agile thought leaders met and came up with the Agile Manifesto
6. AGILE MANIFESTO • Individuals and interactions over process and tools. • Working software over comprehensive documentation. • Customer collaboration over contract negotiations, • Responding to change over following a plan. • We are uncovering better ways of developing software by doing and helping others do it. Through it we have come to value: • That is, while there is value in the items on the right, we value the items on the left more.
7. SCRUM • Roles • Product Owner • Team • Scrum Master • Ceremonies • Daily standup • Sprint review • Sprint retrospective • Artifacts • Product Backlog • Sprint Backlog • Working Software • Project management method for managing using an empirical process.
8. XP • Pair programming • Planning Game • TDD • CI • Refactoring • Small Releases • Coding Standrard • Collective ownership • Simple design • Sustainable Pace • Pair negotiation • Stand up Meeting • Improve software quality and responsiveness, by advocating releases in short cycles and many inspection points.
9. KANBAN • Make work visible • Limit work in progress • Help work to flow • Make policies explicit • Continuous Improvement • A scheduling system for lean and just-in-time production.