With the development of the Learning tools for NSW DET there has been building interest about development methodologies. The traditional waterfall method is well in favour by software developers, but change is happening. Rapid application development underpins most Web 2 technologies and of these methodologies Agile development seems to be getting particular attention. Agile is about easily adapting to changing requirements throughout the process. Agile development is pragmatic in understanding the fact that requirements in a business environment changes constantly. They all incorporate iteration and the continuous feedback that it provides to successively refine and deliver a software system. They all involve continuous planning, continuous testing, continuous integration, and other forms of continuous evolution of both the project and the software.
The manifesto sums the core values:
• Individuals and interactions over processes and tools
• Working software over comprehensive documentation
• Customer collaboration over contract negotiation
• Responding to change over following a plan
But change management must always harmonise with any project development methodology. Again questions of what is the most appropriate CM strategy should be asked. Currently at CCP we are using the Prosci methodology- for organisational change. But applying this to a complex product assumes a product is a fixed entity- and developed in classic waterfall methodology-sequentially. Web 2.0 applications are not static but rather rapidly evolving – not just in terms of functionality but also how they are being used. We can no longer assume that CM is around a single event based on a particular product but need to have a more iterative and evolving model. A model which doesn’t see a linear progression of adoption and engagement but rather a continuing and cyclic engagement of CM elements such as Awareness, Desire and Knowledge in relation not just to the whole product but realising that these Web 2 learning tools are composed of many sub components which make up the overall entity. As such perhaps the CM strategy needs to target these components and not just the overall application. For instance the blog currently under development, is adopted by users in multiple and evolving ways. Many of which could not have been realised in any requirements specifications.