prev next front |1 |2 |3 |4 |5 |6 |7 |8 |9 |10 |11 |12 |13 |14 |15 |16 |17 |18 |19 |20 |21 |22 |23 |24 |25 |26 |27 |28 |29 |30 |31 |32 |33 |34 |35 |36 |review

One of the most common areas for conflicts in software is the failure to clearly define a change management process.

All software will require changes as the system is developed. 

No specification is ever perfect.

The change management process should define how changes to the software will be specified, approved, and costed with the impact on the timeline for delivery.