Related Content
 |
How Group Norms Enable High-Performing Teams Group norms are the traditions, behavioral standards, and unwritten rules that govern how a team works together. They can be implied or openly acknowledged, but establishing a consistent way the team functions helps the individual members focus less on their own preferences and more on what works best. |
|
 |
Make It Easy for Your Customers to Provide Feedback The way some organizations request feedback ensures they don’t get much of it. If you really care about what your customers think of your product or service (and you should), you need to ask for feedback soon after the customer's interaction, give them time to respond, and allow space for their thoughts. |
|
 |
When Can You Honestly Call Yourself Agile? If you're working more iteratively and incrementally and things are better for your team and your customers, can you call yourself agile? As long as you're improving, does it really matter what you call yourself? Johanna Rothman says yes. Unless you're following the Agile Manifesto, you aren't truly agile. |
|
 |
Bringing the Value of Your Test Automation Efforts Front and Center Once you’ve adopted test automation, you should determine whether it’s actually yielding the expected benefits—and you’ll want to keep these benefits visible to stakeholders to reinforce the value. A metrics dashboard aligned with the organization goals and business objectives shows you're on the right track. |
|
 |
Staying Competitive in Software Testing In today’s global economy, staying competitive may be more important than ever. Three ways to contend are by focusing on price, niche (addressing a particular group’s needs), or differentiation (doing things better in some way). Which tactic you choose could make all the difference for your software team. |
|
 |
What’s in the Summer 2016 Issue of Better Software Magazine? The summer issue of Better Software magazine is now live! This issue includes a number of articles that emphasize state-of-the-art practices in the IoT, DevOps, and product-driven process, in addition to highlighting the roles of QA, women, and Millennials and the benefits they can bring to your organization. |
|
 |
Building a Business Case for Automation in Your Software Lifecycle To remain competitive, organizations should consider implementing a well-integrated set of automation capabilities—not just for testing, but across the entire lifecycle. Making the investment might take some convincing, so here are some questions to ask in order to assess the potential benefits of automation. |
|
 |
The Best Way to Communicate Project Quality Concerns When you encounter quality concerns in a project, it's important to let management know. But building an overly detailed list of faults and shortcomings undermines the impact of the important points and muddles communication. To effectively convey the crucial issues, you have to prioritize. |
