The document compares Bangalore traffic to software development by noting their shared unpredictability and delays due to overcrowding of roads and last-minute changes. It states that on roads, vehicles are crammed into too few lanes and unpredictable incidents can cause delays, while in development, late changes to requirements and defects can cause reworks and delays. The solution proposed is to regulate vehicles and requirements, take responsibility, and be practical with time constraints.

1. Bangalore Traffic and Software Development

2. www.henryjacob.com www.designdrivendevelopment.org www.arrkgroup.com About Me

3. Not only Bangalore, even Bangalore traffic has a unique connection with Software Development.

4. In a two-lanes road, we try with 10 lanes of vehicles On Road

5. In one day, we try to finish 10 days of work At Office

6. Mad Trucks Irresponsible Autos & BPO Pickups Terrible Two Wheelers On Road We have to live with

7. Mad Requirements , which need not be developed at all Irresponsible defects , which comes just before you send to the client Terrible last minute discovery of something, which is not implemented At Office We have to live with

8. On Road You don’t know from where, how vehicles will land before you. You live in a fear of hit by someone

9. At Office You don’t know when requirements will change. You live in frustration with reworks, reworks and more reworks.

10. The result is unpredictability and delay.

11. Not just problem, even solution is same.

12. The current Infrastructure is an issue. But the real solutions is not just on expanding roads.

13. Regulate. Responsible. Practical.

14. Expand Infrastructure. Regulate Vehicles. Be Responsible while Driving. Be Practical and Don’t Bang Horn.

15. Regulate Requirements. Be Responsible. Be Practical (Unfortunately, we have only 24 hrs a day).

16. Let’s the requirement drive everything