• Paul Gravina

Change Control Agile/Traditional Implementation

You can try some of these objectives for implementing some change control in your projects whether you are using agile (XP, Scrum) or traditional (waterfall) frameworks. Remember that “change” is a technique in a scrum, every iteration, every cycle and every sprint encounters change and as purveyors of agile frameworks, we embrace it as a team. What happens in these types of frameworks is the team gets very good at change; the team does not shy away from the change they accept and embrace the change building better software for the stakeholders/business owners. By structuring change the agile team benefits the business organization by cross team education, better ROI, more control of the product and satisfaction amongst all your stakeholders/business owners. Agile frameworks build adaptable, cohesive, and disciplined teams, some paperwork will still have to be created but try to complete “just enough” you will find that the framework starts to create gradual structures within the team which morph into full-scale development processes.

Implementation steps: (any framework)

1.Publish your project plan and all supporting documents.

Communicate to EVERYONE your objectives.

2.Create a policy on how to initiate change.

Try to make it formal even in an agile framework because suggestions in a formal environment are usually more legitimate ones pertaining to the project.

3.Address your change requests in a timely way.

Some changes to a project are unwarranted, many represent major improvements so make sure to review proposed changes on a timely basis.

4.Define the benefits, costs of change requests.

Cost-benefit analysis is a technique to help you decide whether to make a change. Try adding up the value of the benefits of the action and subtract the costs associated with it.

#agileframeworks #scrumframework #XPprogramming #Costbenefitanalysis

  • LinkedIn Social Icon
  • Twitter Social Icon

© 2017 Created by  Agile  Atlanta, GA