how to get an Agile project started this afternoon

Jane Prusakova's picture
Submitted by Jane Prusakova on Thu, Feb 19 2009 - 12:17 PM

There are lots of excellent books on developing software, many dealing with Agile, Lean, Iterative and other popular methodologies.

But how do you get started in Agile or some other iterational methodology for the first time ever?
Suppose there are no detractors - the management is on board, the team wants to try Agile and people do not mind going against old habits.
However, nobody knows much about what Agile really is and how it is done, and there is no time for taking workshops or gaining certifications.

Where does one start, which book or article to read first, what to do - this afternoon, which is when the project is getting started?

We had this discussion yesterday on AgileBCS.
One excellent suggestion offered on the technical side is to start by creating continuous build and test infrastructure, and designing metrics. Another idea would be to arrange regular access to the client - whether through a regularly-held meetings, or by having a product-owner person on-site.

What else is necessary to start on a first Agile project?

Comments

threew's picture

I've been down this road

Submitted by threew on Thu, Feb 19 2009 - 5:32 PM.

I've been down this road many times over the past several years. If you check my LinkedIn profile you'll see the tracks ;~)

There are scars and gray hairs as well but not all of that from Agile.

OK: Books are good. But you can't run a succesfull Agile project the first time from a book.

Training is good. But you can't run a succesfull Agile project the first time from one training session.

Coaches and mentors are better. With training and some study, you can (with difficulty and a lot of effort) run a succesfull Agile project for the first time with an experienced coach / mentor.

Get one now or stop the project.

If you are starting an Agile project for the first time this afternoon without someone on your team with experience in Agile development(Scrum or otherwise), you are profoundly doomed.

You need a coach or mentor who is highly experienced in Agile (several years and many projects) and is highly experienced in bringing new, inexperienced Agile groups on line.

• There is big footnote with Agile: “It's simple, but it changes a lot”
• Need to be willing to work in time boxes (might not feel natural)
• Agile “exposes” issues quickly and effectively, but it doesn’t “solve” them
• Engineering, design and testing practices need to become more Agile
• Interactions and communication need to become clearer, more personal and more transparent
• Honesty, trust and a sense of commitment need to be developed
• When the going gets tough it is easy to slip back into the old way of doing things. Courage is essential

If testing isn't ready for this, it won't happen now.

I know this all sounds horribly negative and I hate that -- but I hate project failure even more ;~)

If you're really going ahead and need some quick reading material, I'm sending two things by email through your account on your LinkedIn profile.

Wow,

William W. (Woody) Williams
Senior Project Manager
Software Development, PMO, IT Governance
My door64 Blog
enweave