Related Content
 |
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. |
|
 |
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. |
|
 |
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. |
