Related Content
 |
Who’s Responsible for What? Use a RACI Matrix to Keep It Straight As projects get larger and more complex, roles and responsibilities can become confusing. To clarify, teams can create a RACI matrix: a chart that shows who is Responsible, Accountable, Consulted, and Informed for any work product. Each role has a different level of authority, so everyone knows their duty. |
|
 |
Accelerating Your DevOps Processes with Agile Everyone wants to accelerate the application development process. Agile has done a lot to help, but going faster without understanding whether we are going in the right direction has a significant risk of us getting lost. To really achieve development velocity, you need to understand agile in a pragmatic way. |
|
 |
Automate for Efficiency: How Test Automation Does More than Spot Bugs Some form of automation should be used to streamline testing, but leveraging automation as a crutch won’t help you or your team spot every bug and produce high-quality software. In automation, the tools don’t do all the testing—they simply do what they are told to do by the actual tester. |
|
 |
The Risk of Negative Customer Experiences If people have a positive customer experience, they tell a few friends, but if they have a negative one, they tell everyone—and now that social media have made sharing so easy, no flaw, delay, or mistake seems too small to complain about. More than ever, it's important to create positive customer experiences. |
|
 |
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. |
|
 |
Start the New Year with a Retrospective This new year, instead of a resolution, consider a retrospective. Rather than just setting one large goal for yourself, you review what you've been doing, what's been working and what hasn't, what you want to accomplish, and what small steps you can take every day to reach your objective. |
|
 |
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. |
