Related Content
![]() |
The Key to Avoiding Procrastination If you have a task you've been putting off, dividing it into small chunks is a good idea. But the real key to overcoming procrastination is just getting started. Once you begin, you’ve built momentum and are likely to keep going, doing a little more until you’ve made good progress—and maybe even completed the job. |
|
![]() |
How Testers Can Collaborate with the ScrumMaster ScrumMasters serve the team by providing facilitation and coaching, but they also have many challenges. Those in testing roles are in a good position to collaborate with the ScrumMaster to improve agile processes. Here are some ways testers can partner with, support, and assist the ScrumMaster—and the rest of the team. |
|
![]() |
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. |
|
![]() |
Breaking the Cycle of Bad Scrum When practiced well, Scrum can empower people, teams, and organizations to solve complex problems and deliver value to their customers. But bad Scrum does the opposite. If team members or leaders don't embrace Scrum values, it can be oppressive and create tension. Here's how you can prevent bad Scrum from taking hold. |
|
![]() |
Why Frequently Delivering Working Software Is Crucial to Agile While completing documentation is often an indication that some progress has been made, until software has been implemented, tested, and approved by a customer, the amount of progress cannot be measured. Here are some common reasons agile teams fail to frequently deliver working software—and how to avoid them. |
|
![]() |
Measuring Objective Continuous Improvement in DevOps When you're beginning your DevOps journey, it is incredibly important to know where you are starting. You will want to know later on what progress you have made, and you won’t be able to figure that out unless you have benchmarks from the beginning. Here are six steps to objectively measure your continuous improvement. |
|
![]() |
A Lean, Flexible Measurement Dashboard for Agile and DevOps If you’re moving from a more traditional software development approach to agile and DevOps, or if you’re struggling with implementing metrics, consider reviewing, revising, and refining your measurements. Leave those that add no value behind and look at a monitoring system that has these five essential categories. |