Flickr Badge
Thursday, August 24, 2006
Why software processes are like exercise
Why don't more people exercise? Because its too hard and it involves too much change. You see, exercising involves things like 'determination' and 'discipline' and 'goals', and who has time for that? An entire industry has evolved around the fact that people would like to be fit but do not like to exercise. At one extreme is the quick fix solution - wear some gadget and get fit without doing anything. At the other extreme are the hardcore fitness people who spend hours in the gym and scoff at any fitness scheme that tries to water down exercise. In the middle are a whole lot of activities that try to make exercise more fun and meaningful. The idea is not to be the fittest that you can possibly be, but to be as fit as you can be, without feeling like giving up.
Software processes are exactly the same. Processes are the right thing to do, but its far too easy to not see results and give up in frustration. At one end are the silver bullet providers - do X and your project will deliver itself. At the other end are those who live and breathe process, the process gurus, the people who have paparazzi following them all around.. well ok, maybe no paparazzi.
The agile early adopters are high up on the agility scale. The mainstream following behind are low on this scale. The big challenge for the agile community is to transfer the benefits of agility to the mainstream.
One way to do that is to take a bunch of processes that are radically different from what they are used to doing and ask them to follow them all. Some will try it out, get overwhelmed by the change, and give up in frustration. Others will resist the change. Still others will quit and go with what the silver bullet providers have to offer. A few will cross over. Those who didnt make, well, the fault lies with them - they are weak and have no discipline, and no wonder their projects failed.
Another way is to provide a transition path from zero agility to full agility. Pushing companies to go all the way, all at once, just makes them give up completely. This is bad. Companies should adopt agility at the point that they are comfortable. The idea is to maximise benefit, without feeling like giving up. That way, companies know that they can take the next step, and get better results, if they want to, or else they can stay where they are comfortable if they so desire. Just like exercise.
What would this transition path look like? How would you define 50% agility? How would you reconcile this against different agile processes that advocate different things? What should a company be doing if they want to be semi-agile? I don't have answers to these questions yet. What do you think? Is this possible? I would love any comments and feedback.
This post is a part of the selected archive.
Sunday, August 20, 2006
5 dangers when adopting agile processes - and what to do about them
- Unfamiliarity: When early adopters practice agile, they really understand what agile is all about. Mainstream companies are less likely to understand the principles of the process. They've heard about 'this agile thing' and want the same benefits on their projects.
- Top-down thinking: Most organizations practice top-down management, where managers make decisions and staff follow them. Agile processes work bottom-up, where the team is empowered to take many decisions, and the team is responsible for changing the process. This can be uncomfortable for many managers.
- Culture change: Agile processes not only demand a change in they way software is developed, but a change in culture. Agile processes value a culture of openness, cooperation and collaboration. The mantra is "get work done", instead of "cover your ass".
- Incomplete implementation: Companies that implement agile processes sometimes change the process out of convenience, without an understanding of the process. 'We don't do retrospective meetings because they waste a day of work', or 'Everyone knows what to do, a daily standup is not required' are some forms of process change that are instituted under the guise of 'tailoring the process'. Tailoring the process is good if you know what you are doing, but can lead to disaster if it is done just for convenience.
- Silver bullet syndrome: Agile processes are not a silver bullet. They will not magically deliver your software, cure all ills and create world peace. There are many components to a successful project, and the process is just one of them. You still need a good team to do the work - in fact a good team is even more important in an agile process than in traditional processes. There are many components that determine project success or failure - management support, effectiveness of the process, quality of the team, familiarity with the domain and technology, to name a few. Agile can help with the process, but don't ignore the other components.
Right, so what can you do about it? Here are three ideas to help you get started with agile
- Learn about agile: The best thing to do is to learn about agile. I mean really learn about it, not read a single article in a magazine about how agile is the next big thing. There are lots of great online resources for learning. Check out agile websites, blogs covering agile or agile groups on Yahoo! Groups. You will find lots enthusiastic people just waiting to help out.
- Start small: Start small, refine, repeat. Implementing an agile process is not something that can be done throughout the organization in one shot. Accept that the first few months will be unproductive as everyone comes to grips with agile, its culture and its values. Choose a small project as a prototype, and iteratively refine the process. When you are comfortable, move on to another project, then another.
- Examine the organization culture: A big stumbling block is reconciling the existing organization culture with the values of agile processes. Transitioning to agile involves change, and like all change it is easy to see things not work out at the start, get frustrated and return to known, comfortable ways of doing things. Take some time to learn the values of agile, and how it can be incorporated into the organization.
This post is a part of the selected archive.
Thursday, August 17, 2006
Interesting way to sell your company
You know that the action in the web space is starting to get hot when everyone starts talking about startups that closed down.Online calendering company Kiko.com has decided to call it quits and put the site up for auction on eBay. They are also offering to export or delete user accounts.
Sunday, August 13, 2006
Final batch of photos uploaded
Wednesday, August 02, 2006
France photographs
Tuesday, August 01, 2006
Cyclists, cyclists everywhere
Wednesday, July 26, 2006
Fun at Paris Charles De Gaulle airport
Before me is baggage collection belts 1 and 2. The screen only shows flights from Prague, Bucharest and a couple more east european countries. Hmm. No London anywhere. There are these two people waiting for luggage, so I ask them, but they don't speak english. Where are the others from my flight anyway? I go over to what looks like a help desk and ask the person there. After some broken english, I am told that British Airways is at Baggage Belt 4, at the other end of the terminal. To get there, I need to exit this baggage area and go to the other end.
I leave, walk over to the other end and find Belt 4, but I can't find the enterance to it. The only enterance seems to be through the Immigration desk on the other side of the terminal, and I've already finished Immigration. I go to the Information Help Desk and the person there informs me that I should wait near the baggage exit. When someone comes out, the door will open and I should walk in when the door is open. Interesting!! I do that, and get in. Inside, a customs guy asks me why I am entering from here, and when I tell him (going to the wrong baggage area seems to be a common thing), he says that I should go to the British Airways desk where they will fill up a customs clearance form and I need to give that to the customs.
Back outside, I go to the British Airways desk, show my boarding pass and get the customs clearance form. This is so common that the person at the desk had lots of these forms on the top of the desk. I take the form and get back into the baggage area. The customs guy takes the form and I can finally get my baggage!!
Monday, July 24, 2006
Back from France trip
Friday, July 07, 2006
Electricity plug points again
Thursday, June 29, 2006
Complaint of the day
Wednesday, June 28, 2006
Berlin Photos
Monday, June 26, 2006
Back from Berlin
Another funny thing was the subway/metro system. You need to buy a ticket, but it is not checked anywhere. It is entirely possible to ride the subway without a ticket. In all the subways that I've seen, you have to put your ticket into a machine to be able to enter the platform, but not here. The other cool thing is that you can get a 3 or 7 day pass that not only allows unlimited travel on the subway but is also valid on the buses and trams.
The difference between east and west Berlin was also clearly evident. West Berlin was a lot more crowded during the day, but the situation was the opposite at night. The trams are mostly seen on the east Berlin side, and the building architecture is noticibly different. Oh, and of course, the pedestrian lights are different (see this).
The new Berlin station (Hauptbahnof) is really pretty (More about it here).
Another concern that I had was safety. It felt pretty safe even in the metros and the streets around midnight. Maybe the extra security for the world cup helped. Roaming the east Berlin side was nice especially around Friedrichstraße, and Unter den linden, two important roads in this part of Berlin. Kufurstendamm on the west side was also good.
Also notable was the number of cyclists. Cycling around seems to be very popular, and you can find cyclists everywhere. There is a special coach on the subway for cyclists to use. There are even some dressed in suit and tie cycling to work.
Monday, June 19, 2006
Windows and process
"Windows process has gone thermonuclear. Imagine each little email you send asking someone else to fill out a spreadsheet, comment on a report, sign off on a decision -- is a little neutron shooting about in space. Your innocent-seeming little neutron now causes your heretofore mostly-harmless neighbors to release neutrons of their own. Now imagine there are 9000 of you, all jammed into a tight little space called Redmond. It's Windows Gone Thermonuclear, a phenomenon by which process engenders further process, eventually becoming a self-sustaining buzz of fervent destructive activity."