Related Content
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? |
||
Why Your Agile Team Needs to Slow Down in Order to Speed Up If you find yourself rushing through development or accelerating your testing process to a speed that’s not conducive to the nature of your software or project, it might be time to take a step back, examine your methods, and find a new solution. |
||
How Do We Sell the “Test Early” Principle? Many companies are striving to test earlier. But goals and principles are always easier to articulate than they are to implement. Often, this is less of a technical issue and much more an organizational, change management challenge. Michael Sowers talks about the steps to take to make things happen. |
||
Six-Hour Workdays: As Great As They Sound? Companies in Sweden are experimenting with shifting to a six-hour workday. If employees have less time to do their work, they won't dabble in personal, time-wasting activities, so the same amount of work will still get done as in an eight-hour workday—or so the thinking goes. Would you try a six-hour workday? |
||
What Do You Believe? Many people in the agile community believe their way of doing agile is the only right way. This is supported by confirmation bias, which lets us only see facts that support our beliefs. We deserve data-based approaches to determine what leads to the best outcomes. Can you look beyond your personal beliefs? |
||
Calculating the Cost of Failure What is the cost to your business of an outage due to a major bug? Usually it's calculated as mean time between failures multiplied by mean time to recovery. But what if you could deploy to a limited number of users and monitor effects? Then the equation includes a third variable: number of users impacted. |
||
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. |
||
How to Create a Team Charter for Success Do you find yourself working on a team that lacks initiative except for the things each individual finds useful? Making a team charter may help your team find their core values and purpose in the organization. Linda Cook tells you how to create a team charter that will point your team in the right direction. |