Maintenance of Your Agile Process Agile Testing

Almost as soon as it has been rolled out and adopted, your agile process is likely to be out of date;implementation technology changes at a very rapid pace, new agile practices continue to be developed and refined, and new and improved tools become available to be used on agile projects. At the very least, the process will need to change to take account of lessons learned during its use.

You should establish some key points where your agile process should be reviewed and proposals for changes discussed. These could include the following:

  • At the end of individual projects to identify any lessons learned during the project. If agile retrospectives are a feature of your agile process, define a formal mechanism for documenting the lessons learned from all agile projects, and put a change management process in place to process proposals for change to the process. Consider the value of using tools to support the process of accepting requests for change and for documenting and maintaining the requirements(ensure these are distributed products if you have a number of sites using your agile method).
  • Following changes in the wider agile community, such as the availability of new or refined agile best practices. You should be receptive to such changes and new agile practices by being aware of the agile literature, registering on agile special interest Web sites and visiting agile blogs, and attending appropriate special interest group meetings.
  • As a prelude to the adoption/introduction of new or enhanced testing tools or techniques.
  • Following changes in the management approach of the organization, such as the adoption of a new project management methodology, or some formal process improvement scheme, that impacts your agile process.
  • At regular dates, such as an annual or biannual review.
  • As and when requested by the company quality assurance manager(or equivalent).

Following such a review and where changes need to be made to the process, the following actions should be performed:

  • Update whatever mechanism you have selected to distribute your agile process to your colleagues(ensuring that any changes do not adversely impact agile projects that are still active).
  • Actively inform key stakeholders in your company that changes have been made and tell them where they can find more information.
  • If the change is a major one, consider the need for training and mentoring to make sure that your colleagues are able to employ the changes correctly and benefit from them.
  • Review the success of the change at some point following its introduction and after sufficient time has elapsed to allow an accurate appraisal to be made of its benefits.

All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd Protection Status

Agile Testing Topics