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. |
|
 |
How “Large” Is This Project? When organizations want to step up their project management game and implement more rigorous project management practices, there is always fear that the administrative overhead will exceed the value gained. |
|
 |
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. |
|
 |
Ditch Your Logs for Better Monitoring Metrics Many teams use logs to track the behavior of applications, services, or platforms. But how actionable is that log data? There are better ways to parse that information and make it more visible, more useful, and easier to understand. Try converting your logs into metrics for a faster and more lightweight monitoring system. |
|
 |
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. |
|
 |
Exploring Containers: Creating a Dockerfile Docker containers are launched using Docker images, which are built from layers of Dockerfiles. A Dockerfile is a text document that contains all the commands or instructions to create, copy, and run an image. Let’s look at what goes into creating a Dockerfile, which could be used to build a runnable Docker image. |
