Related Content
 |
Change Isn’t the Problem Project managers need to ensure that sponsors, team members, and stakeholders understand that un-managed change is the real bogeyman. |
|
 |
The Cost of Vendor Delays Make sure that your change management process is clearly outlined at the beginning of a project and use it when there are unforced errors to get concessions from a vendor when the fault is clearly on their side. |
|
 |
Securing Software Deployments: Understanding Your Attack Surface As organizations embrace new technologies to modernize their business processes, they increase their attack surface. Since it is easier to protect a small attack surface, organizations should strive to minimize it to reduce the risk of a successful cyberattack. |
|
 |
That’s a Great Idea! Let Me Get Back to You… Being responsive to customer needs and desires is not a bad thing—the decision to accept, reject, or defer a change is something that should be considered in light of the consequences of the delay. |
|
 |
The Cost of Running Late Projects exceed their predicted schedules for many reasons. The cost consequences of some delays are obvious, but some are subtle. Knowing the expected costs of delays is vital to supporting informed decision-making. |
|
 |
Test, Test, Test Test, test, test. This is a phrase that has caught everyone’s attention this year as we grapple to mitigate COVID-19. The WHO states that testing is the only way out, as we cannot fight the pandemic blindfolded. |
|
 |
Code Integration: When Moving Slowly Actually Has More Risk Many decisions about code branching models are made in the name of managing risk, and teams sometimes pick models that make integration harder in the name of safety. Moving slowly and placing barriers to change can seem safer, but agile teams work best when they acknowledge that there is also risk in deferring change. |
|
 |
Achieve Repeatable Builds with Continuous Integration Continuous integration is essential to provide the feedback needed to keep a team’s code agile. One crucial aspect to a successful CI process is a repeatable build. There are two parts to maintaining a repeatable build: the idioms and practices to define it, and the feedback cycle to maintain it. Here's what you need. |
