Related Content
 |
Interface Grief: Is It Agile, or Just Bad Software Engineering? There are people who will use "being agile" to justify software engineering practices that could be perceived as lazy or even bad. The specifications are going to change, they say, so it would be a waste to engineer more to begin with than the minimum viable product. What's expediency and what's just poor practice? |
|
 |
Agile and Testing Change Can Come from Leaders at the Bottom, Not the Top Change doesn’t need to be a decree from the top that forces everything else to follow suit. Change can and should start from the bottom, and that happens after you empower your developers and testers and clearly show why things like agile are critical to overall success. |
|
 |
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? |
|
 |
Understanding the True Meaning of Quality Day-to-day testing techniques, strategy, approach, and automation are all things that teams understand and will continue to implement, but how many teams understand the elements of purpose, belonging, transcendence, and storytelling as they apply to software quality? |
|
 |
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. |
|
 |
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. |
