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. |
|
 |
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. |
|
 |
3 Serverless Strategies to Look for in 2021 In this article, we examine the three serverless applications deployment and development approaches that are transforming the application development process and acting as a catalyst for fast adoption of the DevOps practice across the board. |
|
 |
What Exactly Is Serverless? The word serverless—it’s everywhere. The word has been Googled an average of 100 times daily in 2020. Is serverless just a buzzword? A facade? Or a world where we won’t need servers anymore? |
|
 |
A Physical Metaphor for Quick Fixes and Root Cause Analysis If you deal with legacy code you’ve likely found yourself struggling to debug and fix a mysterious, intermittent problem. Along the way you may have discovered some code that didn’t quite make sense. |
|
 |
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. |
