Apply today for a FREE subscription to CIO Magazine!
Tue, Jul 15, 2008 13:03 EDT
|
Posted by: AlexForbes in Questions Topic: Development
Current Rating: |
I've heard the phrase People and Process over Tools when referring to Agile.
I've heard of the rustling of 3x5 cards on posterboard in the hallways.
I've heard how putting information into a tool hinders communication when not efficiently relayed to those areas where the information is being consumed.
When outsourced teams are collaborating on onshore projects with teams of teams, what is your answer for effective communication and collaboration? How much labor is going into your information radiators when scaling Agile beyond a dozen collacated team members?
Anyone use a 42 inch plasma TV with an Internet picture device to upload their daily burndown chart or anyone still using lava lamps for continuous integration?
An inquiring mind wants to know.
I believe the point you are trying to make is a valid one, but you probably won't find much in the way of participation here. We personally use the phone, wikis and a blog to keep our external development efforts on track. I agree what you put into a tool doesn't always come out the way you intended, but anyone who says you don't need tools for Agile is probably one of the original writers of the Agile Bible written before the Internet.
Agile supports the use of tools and values them, it just supports people and processes *more*. I find a decent user-friendly helpdesk system does just the job for managing a sprint backlog. I tried whiteboards but frankly they are pretty lousy for external reports, lousy for gathering the metrics you need to project forward as to whether the burn rate is realistic and pretty lousy if you have flexible working and not every developer is in the office every day.
So, software tools (inc wikis) over whiteboards wins for me every time.
The whole point if "tools" is to make one's job so much easier.
Agile is such a tool which helps the SDLC that much easier. Especially onshore/offshore development teams.
The concept of sprints in agile is really remarkable, since it allows requirements to change and limits the re-architecture efforts required.
Bottom line is that, Tools are there for a reason. "To help get the job done!"
Arsen Pereymer
Chief Technology Officer
eCompetitors, Inc.
http://www.ecompetitors.com