Related Content
 |
The Relationship between Agile and DevOps Many are touting DevOps as something new and different—just like agile before it. DevOps fixes an age-old conflict between software development and operational teams, but it’s not new. In fact, the DevOps philosophy is ingrained within the Agile Manifesto. So why is DevOps viewed as something different from agile? |
|
 |
Balancing Process and Tools The limits of a tool may lead us to realize that we are not working as effectively as we can, and often, changing a tool is part of the solution. But there are good and bad ways to select a tool and how you use it. In particular there are risks when you focus first on tools before considering the problem. |
|
 |
DevOps Isn’t a Fad, So You Need to Invest Now It’s easy to get wrapped up in the promise of ten-times greater production, shorter development times, smarter testing, and everything surrounding the fresh idea of the day, but when it comes to DevOps, there’s no longer a need for trepidation. DevOps is here to stay. |
|
 |
Why the Gig Economy Thrives in the World of DevOps Even if the industry is booming, it’s not easy filling the full-time DevOps roles. Every software team is vying to find the perfect person to come in and establish a culture to promote improved software release cycles, software quality, security, and rapid feedback on product development. But it's not easy. |
|
 |
An Agile Approach to Change Management Many organizations are reluctant to introduce new tools or technologies, or even to update existing ones. The reason is often framed in terms of risk management, but agile teams already have the tools to manage the risk of change: testing and experiments. These approaches together eliminate gaps in risk identification. |
|
 |
5 Myths and Misconceptions about Leadership It’s a common myth that leaders are born, not made. Even so-called natural leaders have plenty to learn about handling the kinds of challenges and problems they’ll have to face, and many others grow into the role. Let's explore this misconception and four others to learn that anyone with the drive can be a leader. |
|
 |
Think through System Changes to Anticipate Quality Issues When you replace or significantly modify components of a larger system, too frequently we focus on whether the code we are building functions correctly. This is important, but it’s also short-sighted. It’s easy to introduce errors because we are changing interactions. Coding bugs are only one quality problem. |
|
 |
Why You Should Have an Observer on Your Project Team If your project team suffers from misunderstandings or squabbles, it may be valuable to designate an observer role. This person would sit back and pay attention to whether there are patterns of miscommunication, interruptions, or conflicts that those in the conversations may not notice, helping resolve problems. |
