change management
 |
The Importance of Timing when Implementing Change Too many changes at once can prolong upheaval and delay people's adjustment to the new norm. If you are planning to start a complex project, introduce a new tool, or undertake any other major initiative, and employees are still reeling from other changes, it may be wise to delay the planned change if you can. |
|
 |
Shake Up Your Software Processes: The Intermediate Disturbance Hypothesis Organizations that refuse to change will get left behind. But at the other end of the spectrum, too much change is also harmful. Revamping everything you do at once creates stress and can lead to your efforts failing. The right balance is shaking things up just often enough to experiment with new ideas. |
|
 |
How Do We Sell the “Test Early” Principle? Many companies are striving to test earlier. But goals and principles are always easier to articulate than they are to implement. Often, this is less of a technical issue and much more an organizational, change management challenge. Michael Sowers talks about the steps to take to make things happen. |
|
 |
Reliability Is Possible with Environment Management To have completely reliable systems, we must have effective IT controls in place that help to identify risks before they turn into incidents. Change management meetings are very helpful for coordination. Effective environment management and change control can keep your systems reliable and secure. |
|
 |
Agile Teams Can Learn a Lot from the World Cup It might not seem apparent at first, but there are more than a handful of similarities between agile teams and those football/soccer teams representing their respective countries in the World Cup. How teams are built, their objectives, and on-the-fly changes are all facets that tie both together. |
|
 |
Stop Blaming Changing Requirements for Your Project's Failure Blaming changing requirements for a project's downfall is about as misguided as it gets. When you start accepting that change is in coming and you start preparing for it by using iterative development, you'll see that dreading or fighting change is the only way to ensure failure. |
|
 |
What Is the Purpose of Configuration Management? Joe Townsend attempts to find out: What is the purpose of configuration management (CM). This seemingly simple question is the one we CM professionals are often asked, and at times we stumble to offer the answer that really drives home the true purpose of what we do as configuration managers. |
|
 |
Embrace Changing Requirements or Work Hard to Reduce Uncertainty? Agile development teams and practitioners can welcome changing requirements all they want—but how hard should they work to reduce the uncertainty that accompanies changing requirements? Experts have mixed opinions on the topic, and each side makes a pretty convincing argument. |
