When two parties within the same company begin to bicker and disagree, things can go downhill quickly. Neither party may want to accept the blame for the poor relationship, but an improvement must be made in the communication between the two parties so that the disagreements don't extend further.
Rick Scott often writes about the lines that connect the dots between schools of philosophy and software testing. In this article, he shares some tips for seeking out your own new perspectives and introducing them into your testing work.
Shweta Darbha explains how teams can review their work and improve themselves after the completion of key projects or after they have adopted Scrum. Learn how your own team could benefit by following this practice after your next project.
Rather than rely on large handoffs between specialties, high-performing Scrum teams learn to do a little bit of everything all the time during a sprint. To do this effectively, teams must make three changes: shift from writing about requirements to talking about them, reduce the size of handoffs and make them more frequently, and pay more attention to the size of the product backlog items that they bring into their sprints.
Basic load testing is valuable, but it's important to move past simplistic efforts. Here are some ways to gain more accurate metrics from your load tests.
Mik Kersten and Heather Shanholtzer recently spoke about trends in cloud-based tools and how cloud technology affects application lifecycle management.
Knowing when to read the read the full slides of your presentation, when to paraphrase them, and when to let your attendees read them on their own. The way you read your slides can determine how much is learned during your session, along with keeping attendees engaged in your topic.
An objective ranking system is unnecessary when trying to determine an employee's value, and it can even be detrimental to collaboration on teams. Providing feedback, facilitating knowledge building, and allowing them to contribute are three key ways to help your employees excel in their roles.
Regulatory compliance may seem daunting, and penalties for non-compliance can be severe. What is the QA professional’s role in making it work?
Heather Shanholtzer interviewed Seilevel's Joy Beatty about the benefits of using visual modeling instead of traditional requirements documents and why writing good requirements might not be your best point of focus.
Agile Connection is one of the growing communities of the TechWell network.
|Featuring fresh, insightful stories, TechWell.com is the place to go for what is happening in software development and delivery. Join the conversation now!|