Where do Open Source and Agile Methods meet? Dennis Byrne - ThoughtWorks [email_address] http://notdennisbyrne.blogspot.com/

Overview Experience Define “Open Source” and “Agile” Process, not stacks Compare and contrast OS and Agile Opportunities for mutual benefit

Experience

Define “Open Source” and “Agile”

Process, not stacks

Compare and contrast OS and Agile

Opportunities for mutual benefit

My Experience Open Source Apache (MyFaces) JBoss (JSFUnit) ThoughtWorks, Agile Tech Lead Iteration Manager Scrum XP

Open Source

Apache (MyFaces)

JBoss (JSFUnit)

ThoughtWorks, Agile

Tech Lead

Iteration Manager

Scrum

XP

Defining OS and Agile Open Source Mature Successful “ Large” numbers of users Agile Plain Vanilla Agile Not Scrum, Crystal, XP, Lean, etc.

Open Source

Mature

Successful

“ Large” numbers of users

Agile

Plain Vanilla Agile

Not Scrum, Crystal, XP, Lean, etc.

Comparing OS and Agile Continuous Integration Tight feedback loops Lightweight processes High visibility Collective code ownership “ Release soon, release often” Small, self-enabled teams

Continuous Integration

Tight feedback loops

Lightweight processes

High visibility

Collective code ownership

“ Release soon, release often”

Small, self-enabled teams

Old Question, New Answer Other Opinions Adina Levin Nicholas Goodman Stefan Cook My point of view Agile and OS are different (process) Agile and OS are orthogonal (stacks)

Other Opinions

Adina Levin

Nicholas Goodman

Stefan Cook

My point of view

Agile and OS are different (process)

Agile and OS are orthogonal (stacks)

Contrasting OS and Agile Pair programming Daily stand up meetings Iterative development Card walls

Pair programming

Daily stand up meetings

Iterative development

Card walls

Contrasting OS and Agile “ Software requirements is a communication problem. Those who want the new software (either to use or to sell) must communicate with those who will build the new software. To succeed, a project relies on information from the heads of very different people: on one side are customers and users … on the other side is the technical team.” - Mike Cohn, User Stories Applied

“ Software requirements is a communication problem. Those who want the new software (either to use or to sell) must communicate with those who will build the new software. To succeed, a project relies on information from the heads of very different people: on one side are customers and users … on the other side is the technical team.”

- Mike Cohn, User Stories Applied

Contrasting OS and Agile Leadership structure Linux Ruby on Rails Spring Hibernate TDD Face to face communication Co-location

Leadership structure

Linux

Ruby on Rails

Spring

Hibernate

TDD

Face to face communication

Co-location

Apache is an Exception Voting system “ Community Before Code” JSR/JCP Implementations Geronimo (J2EE) MyFaces (JSF) Tomcat (Servlet, JSP)

Voting system

“ Community Before Code”

JSR/JCP Implementations

Geronimo (J2EE)

MyFaces (JSF)

Tomcat (Servlet, JSP)

TDD Difficult to get people to practice TDD when you are not paying them On other projects the challenge is how to keep the tests under ten minutes Encourage contributions with tests “ Ten furlongs of text justifying a position is poor form; better would be a (failing) unit test.” – Codehaus Manifesto JCP: more TCK, less specification JCP: open source the TCKs

Difficult to get people to practice TDD when you are not paying them

On other projects the challenge is how to keep the tests under ten minutes

Encourage contributions with tests

“ Ten furlongs of text justifying a position is poor form; better would be a (failing) unit test.” – Codehaus Manifesto

JCP: more TCK, less specification

JCP: open source the TCKs

Why Nightly Builds? Pros Decreased TCO, technical currency Incremental costs of change are less “ Fail Fast” Agile teams should “eat their own dog food” Cons It’s called the bleeding edge for a reason? Business loses control of the project Schedule risks

Pros

Decreased TCO, technical currency

Incremental costs of change are less

“ Fail Fast”

Agile teams should “eat their own dog food”

Cons

It’s called the bleeding edge for a reason?

Business loses control of the project

Schedule risks

Continuous Builds Continuous builds > nightly builds “ Failing fast” OS community And the businesses that support it One way to diversify a marketplace OS project vs. OS project OS vs. Proprietary Software

Continuous builds > nightly builds

“ Failing fast”

OS community

And the businesses that support it

One way to diversify a marketplace

OS project vs. OS project

OS vs. Proprietary Software

Benefits of Continuous Builds The software to support this mature Continuum, CruiseControl and Hudson are free No existing technical hurdles Strengthen the community A new way to contribute

The software to support this mature

Continuum, CruiseControl and Hudson are free

No existing technical hurdles

Strengthen the community

A new way to contribute

Benefits of Continuous Builds Put instructions for Continuum or CruiseControl on the web site, just like Subversion or CVS Pay attention to Continuous Integration reports from outside of your projects Target release dates (JBoss)

Put instructions for Continuum or CruiseControl on the web site, just like Subversion or CVS

Pay attention to Continuous Integration reports from outside of your projects

Target release dates (JBoss)

What can Agile learn? Giving credit where credit is due Common code ownership High visibility Lightweight process

Giving credit where credit is due

Common code ownership

High visibility

Lightweight process

Dennis Byrne - ThoughtWorks [email_address] http://notdennisbyrne.blogspot.com/

Dennis Byrne - ThoughtWorks

[email_address]

http://notdennisbyrne.blogspot.com/