Related Content
 |
Prioritizing Invisible Work There are work items that will give the team an operational boost and perhaps avoid a crisis, but that never make it to the top of the priority list—like build and deployment improvements, or paying down technical debt. For enabling work that is valuable but too invisible to be a priority, consider breaking it down. |
|
 |
Team Agility in a Post-Pandemic World COVID-19 has necessitated entirely remote environments, and people the world over have had to inspect their foundations of working, adapt to a new way of remote execution, and integrate their personal and professional lives more than before. Organizational leaders need to embrace a new outlook in four critical areas. |
|
 |
Is It Really ‘Us vs. Them’? Teams often view executives as being "against" them and making decisions that are clueless at best or nefarious at worst. Usually, neither is the case, but there's no way of knowing true motivations if there's no discussion. Teams and directors need to repair their communication rift. This is a tale of two perspectives. |
|
 |
What’s the Problem with User Stories? Agile projects focus on very lightweight, simple requirements embodied in user stories. However, there are some problems with relying solely on user stories. They often don't contain enough accuracy for development, testing, or industry regulations. There's a better way to write detailed requirements that are still agile. |
|
 |
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. |
|
 |
The Real Value of Cross-Functional Agile Teams Agile teams know that cross-functional collaboration is central to the methodology, but there are often barriers to fully embracing this idea. If teams are used to handoffs, it may seem like it makes sense to maintain the status quo. Try collaborating on something small to realize the true value of cross-functional teams. |
|
 |
Testing in the Dark Requirements only go so far in identifying areas to test. Sometimes testers are given no information at all, leaving it up to them to determine what to test. Don’t accept the need to indiscriminately test with no clear understanding. Your testing should be targeted, and these techniques will help focus your test effort. |
|
 |
Leave No Tester Behind Creating comprehensive automated tests within a sprint can be a challenge. If the testers don't finish the automation and the rest of the team moves on, testers get left behind and can't catch up. You need some techniques to keep everyone together and ensure that all essential work is accomplished—including test automation. |
