One of the biggest gaps in the requirements discovery and specification, and solution design is formed because the whys are not communicated to the solution developers. The requirements specification usually talks only about what the solution should do. There is nothing that tells them why it is so. [Continue]
Marcel provides some insights on estimating. It is sound advice, except that estimation is usually done at a time when nothing else in the project is decided, which actually is guesstimation. So when we do this estimation, we define many other dimensions, like the team’s composition, skill-set and process. [Continue]
“We have found out what the software should do for us. Here are the requirements, which we know you will ask for; and here is the systematically documented design specification!”, says the client. “All you have to do is write the software and give it to us!!”. [Continue]
Jeff Patton says that agile development is more of a culture than a process. It is quite refreshing to read constructive a constructive discussion on the topic, though it did put pressure on me to really understand what culture meant, and it can have several meanings. I think agile can be agile because it asks you to follow a set of principles without being restrictive about how we do that. [Continue]
Clay has insightful thoughts about why CMSs don’t work. More often than not, off-the-shelf CMSs become a hurdle in the things we want to do our way. However, I do not think it is only the CMS to blame. [Continue]
Tiffin Meals, a food delivery service in US inspired by the mumbai dabbawalas! No technology, no operations research, illiterate workers lower literacy rates (updated after speaking to my dabbawala), using bicycles, crates and public transport, and still almost zero errors. Quite unique characters, wouldn’t you say! [Continue]
Andy Singleton has point when he says that Subversion still has its place. Or that centralized VCSs are not losing against the distributed VCSs. While I agree that Subversion is not going to fade away, I wonder if the ease of use is the best argument for it. [Continue]
I am happy to know that Infosys is taking initiative to encourage their employees to beat the traffic. The system of financial rewards is a good incentive. However, I wonder if companies will be willing to let their employees work from home whenever possible. [Continue]
Software sees a very high frequency of newer versions everyday, more so in the open source world. I have heard claims that this is just a way of the software developers/owners to continuously engage the user. However, reading faster horses (a must-read piece by JP) made me think that this is just the after-effect of engaging the user. [Continue]
The proponents of the agile methodologies wanted to change the way software development was done. I think that changes have happened, but unfortunately most of them are superficial ones, leading to failures and more notoreity for the underlying philosophy. Scott Nelson explains how some aspects of agile methodologies can be wrongly used. [Continue]