Hardfacts about Agile implementation
Agile, the name conjures up images of the experience I had since the last one and half years. I have been in this traditional school of thought for Software Development for nearly 18 years. That is an awfully long time. I have time and again been exposed to the same traditional methods of development and testing. With the advent of the Agile product development process that was undertaken in our organization, it was kinda difficult to adjust to this new pace of activity.
You know what I mean!!! It has been like walking on the edge, knowing very clearly that one fall will expose a far greater risk which we may not be able to overcome. However the experience has been exhilarating and thrilling to the core. Innovation and creativity has become a part of life as a software engineer now. For most of the developers it was a change from the usual chore of creating huge rolls of documents to prove what they had developed.
Now they are hardly concerned about the document creation. Whatever document you might have is just the bare essentials to cover the minimal aspect of the project. For them, it is a way back to the adhoc process with minimum processes and documents to a code-centric activity and they were thrilled with the prospects. Imagine shedding our clothes and going back to the primitive method of dressing.aaah I mean “just the fig leaf“. That would have been wonderful for some, but for some it was a risk not worth taking. Typical managers would shudder at the thought of not having a well defined plan for the next few months and doing away with documents. But if you read and adjust to the process very well, then we could have a better plan for a better throughput within the minimum possible time effort. It has been consistently proved that the time to market has reduced considerably in this world of cut-throat competition of product development.
An initial problem we faced and we still are facing is as regards the role of testers. We might still be doing the end of cycle testing after every component or iterative piece of code is developed. What is needed here is to treat testers on par with the other members within the project and enable them to contribute to the decision making process. This will enable them to have a fair idea on the product and do their bit to enhance from the user’s point of view. This becomes all the more important when we are talking of products that focuses on the end-user and the ability to market the product to these end-users.
Ultimately the success of the product will be determined by the number of users who have accepted the product in the first place and will be willing to improve their favorite product by constructive feedback.
I guess, we will still be continuing on the improvements with respect to the Agile process and be smarter to deliver the right product to the end-user.