Related Content
 |
What It Takes to Be an Effective Leader in Software Testing Similar to the discussion of “How much test automation do I need?” the answer often depends on your team’s makeup and what sort of product you’re making. There isn’t a perfect equation, but there are still general, proven qualities that lead to better software and happier software testers. |
|
 |
Skills and Attributes Agile Testers Need to Thrive Communication is more important than ever, with developers and testers working together more closely. You can no longer think of the “development” and “testing” stages as diametrically opposed sides of the process—in order to succeed, developers and testers need to communicate and work as a unit. |
|
 |
Fitting Specialists into Your Scrum Team While you may try to create Scrum teams composed entirely of people with T-shaped skills, you might still have gaps in certain specialized areas. Consider forming “specialist teams” to organize experts in the areas that require certain skills. You can have these specialists temporarily become part of your Scrum team. |
|
 |
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. |
|
 |
How You Can Help the Human Animals in Your Group Thrive On our teams, we deal with many individuals with diverse perspectives. It's not always easy, but we are animals, and many animals live and work—and are only able to survive—in teams. You can look to how animals interact with and react to each other to see how we, as human animals, can not just survive, but thrive. |
|
 |
What’s in the Fall 2017 Issue of Better Software Magazine Better Software magazine editor Ken Whitaker highlights content from the latest issue, including articles on bridging the divide between agile and waterfall, scaling agile through empowered teams, DevOps and IoT, and continuous development. |
|
 |
Use Continuous Backlog Grooming to Refine Agile Requirements Continuous backlog grooming means systematically refining your user stories: breaking up larger stories, obtaining detailed requirements, writing the requirements in terms of acceptance criteria and acceptance tests, and sharing and refining these details with the team. Acceptance test-driven development can help. |
|
 |
Technical Debt, Product Value, and Risk Management Reports that the Equifax breach took advantage of a known issue in Apache Struts set the stage for a conversation about technical debt, product value, and risk management. Steve Berczuk shares his thoughts on how to help prioritize technical work in a way that balances short and long term value. |
