What I learned at the Agile2010 Conference
I attended a conference, yeah!
The Agile 2010 Software Development Conference was held in Orlando, Florida from August 9-13.
The last technical conference I attended was OSCON (Open Source Convention) 2006 in Portland, Oregon. Agile 2010 was a really great opportunity for me to jump-start my transition from system administrator to software developer.
I am part of a small, dispersed team. We currently have multiple active projects with each developer assigned to a project. We are already following practices such as Test Driven Development (TDD), but we have some challenges ahead if we wish to apply additional Agile practices throughout the team.
Before the conference, I scanned our office bookshelf and wrote down the author names from our most respected volumes. It was great to go to a conference and hear the authors speak on these topics and in many cases have a chance to talk with them. I learned something in every session.
Today was my first day back in the office and I immediately got to work trying to implement ideas from the conference. The first artifact of this effort is a shiny new story board that more accurately reflects project scope:

A few concepts presented by Scott Ambler (and others) particularly hit home with my project:
1. Yes, with Agile you still need to do Initial Requirements Envisioning and Initial Architecture Envisioning.
2. Identify major components / subsystems / services first.
3. Flesh out interfaces first... sometimes this is known as "API First".
4. Prove the architecture with working code.
Here are some interesting statistics shared by various speakers at the conference:
The Agile 2010 Software Development Conference was held in Orlando, Florida from August 9-13.
The last technical conference I attended was OSCON (Open Source Convention) 2006 in Portland, Oregon. Agile 2010 was a really great opportunity for me to jump-start my transition from system administrator to software developer.
I am part of a small, dispersed team. We currently have multiple active projects with each developer assigned to a project. We are already following practices such as Test Driven Development (TDD), but we have some challenges ahead if we wish to apply additional Agile practices throughout the team.
Before the conference, I scanned our office bookshelf and wrote down the author names from our most respected volumes. It was great to go to a conference and hear the authors speak on these topics and in many cases have a chance to talk with them. I learned something in every session.
Today was my first day back in the office and I immediately got to work trying to implement ideas from the conference. The first artifact of this effort is a shiny new story board that more accurately reflects project scope:

A few concepts presented by Scott Ambler (and others) particularly hit home with my project:
1. Yes, with Agile you still need to do Initial Requirements Envisioning and Initial Architecture Envisioning.
2. Identify major components / subsystems / services first.
3. Flesh out interfaces first... sometimes this is known as "API First".
4. Prove the architecture with working code.
Here are some interesting statistics shared by various speakers at the conference:



