Abstract
In this chapter I will describe two processes: one for managing non-development change in SharePoint and one for approving and rejecting development changes to your SharePoint environment. The processes for assessing which adjustments should be made to your SharePoint system are referred to as change management. The continuous process of managing the life of an application through governance, development, and maintenance is referred to as application lifecycle management. I will provide you with templates for both of these processes. I’ll also describe some of the reasons why change is resisted by IT departments, why change is necessary, but also why too much change is dangerous in a way that can be more sudden and destructive than too little.
“The one unchangeable certainty is that nothing is unchangeable or certain” —John F. Kennedy
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Rights and permissions
Copyright information
© 2011 Stephen Cummins
About this chapter
Cite this chapter
Cummins, S. (2011). Change Management and DR. In: Pro SharePoint 2010 Disaster Recovery and High Availability. Apress. https://doi.org/10.1007/978-1-4302-3952-9_9
Download citation
DOI: https://doi.org/10.1007/978-1-4302-3952-9_9
Publisher Name: Apress
Print ISBN: 978-1-4302-3951-2
Online ISBN: 978-1-4302-3952-9
eBook Packages: Professional and Applied ComputingApress Access BooksProfessional and Applied Computing (R0)