Fri 27 Jul 2007
Web 2.0 and Agile
Web 2.0 is catching attention of all and organizations need to adopt a quick deployment strategy to stay in the game .Most Web 2.0 projects are consumer oriented and it is very important that users feedback are incorporated early to measure success. This would require a methodology which accommodates users feedback and also has a faster release cycle based on priorities.
Agile development which favors short iterations and continuous integration testing could be one of the methods that can be adopted.Agile development emphasizes the need for feedback, exploration and Release adaptation. One of the common themes in agile is “release early, release often.”, The Continuous feedback would ensure users involvement throughout and Agile development and this would ensure that the released product is as per users expectation and this is one of the key success factors in an Web 2.0 development .
In an Agile development we can use a combination of XP and SCRUM, SCRUM can be used for project Management and XP can be used for implementation. In this methodology it would be logical to group stories (Use cases) in multiple iterations and the Stories to be addressed in each iteration can been decided based on the dependency between stories. Techniques like the DSM would help in sequencing stories. Each group iteration can have 2-4 iterations and length of each of these iteration to be not more than 5 weeks, This would ensure that feedback from each iteration flows into subsequent iterations for action.
While it is commonly believed that this methodology can be applied only in scenarios where we need to closely interact with users and hence it is required that the execution needs to be done at customers site, we have seen large success adopting this in an onsite offshore environment but this needs to done in a well defined process and clearly articulated deliverables .