Related Content
 |
The Consequences of Project Delay An often overlooked and underappreciated aspect of project schedules is the consequences of delay on others. Due dates and commitments sometimes matter more than they appear. Knowing the larger context of your project can help you prioritize how you undertake it, consider options, and improve problem-solving. |
|
 |
The Tester as Product Owner A lot of the bugs we find were never thought through in the first place. Many of these situations are preventable, yet instead of prevention, we get the tester playing the role of the product owner—and playing it late. Why is it that we never have time to do it right, but we always have time to do it over? |
|
 |
You’ll Only Create Bottlenecks if You Become Too Agile If your goal is to do everything agile, bottlenecks will begin to rear their ugly heads. Not every aspect of the business lends itself to an agile structure, so it’s important to evaluate each situation in order to determine the method that suits it best. |
|
 |
The Evolution of a Product Owner The practical application of agile in organizations is still difficult. The role of product owner has changed, and today a PO has to be tech-savvy, aware of the market, and accountable for execution, innovation, and quality. Tim Wise shows the evolution of a product owner and details what it should be now. |
|
 |
Jelly Beans and Defect Classification: Different Strategies for Success When there’s a bowl of jelly beans, some people grab a few at random, but most of us have favorites. If you're crafty and have flexible standards, you can maximize consumption by adjusting your criteria as colors dwindle. Classifying defects should not be like choosing jelly beans; you need firm standards. |
|
 |
Stronger, Faster Quality with Simple, Focused Checks Imagine focusing on prioritized business requirements at the software layer closest to where those business items are implemented. Writing just one check—that is, a programmed verification—per business requirement makes for simple, focused checks, supporting stronger, faster quality around the team. |
|
 |
What Are You Measuring? Many teams do single-point measurements in their projects. But that doesn't give you a good long-term picture. When you look at multiple-dimension measurements—especially trends over time—you learn more. You can take those trends into a retrospective to investigate how your team could work better. |
|
 |
What Do You Do When You’re Stuck on a Problem? Some problems we can resolve on our own in a couple of minutes. Some take more time, or we can’t resolve them alone. What do you do then? Johanna Rothman suggests scheduling a timebox to find a solution alone, then if that doesn't work, using one of the ideas in this story to "unstick" yourself. |
