Related Content
 |
Agile Dojo: Speed Up Delivery Using Focus An Agile Dojo is an immersive learning experience where teams bring their work into a collocated space and work together to complete a project, using “hyper-iterations” of two-day sprints, over six weeks. Even distributed teams are able to collaborate, focus, and deliver projects on time and within budget. Here's how. |
|
 |
Making DevOps Evolution Happen It takes effort to evolve an organization’s culture, processes, and technology to optimize performance for a DevOps environment, and it all comes down to the people. Large-scale mobilization requires a focus on people at all levels, empowering them to discover and make the changes that will help them most. Here's how. |
|
 |
Transforming a Team of Agile Skeptics into Agilists Coaching an agile-skeptical team demands a personalized approach. Agile introduces a different way of working and thinking, and leaders must find a way to overcome resistance and foster a collaborative culture. Take these three steps to move toward achieving an agile mindset and realizing the benefits of agile. |
|
 |
Maximizing Agile by Understanding Learning Styles To be most agile with your communication, understand several models of learning styles, where you fit into them, and where your team fits into them. By tweaking the ways you communicate to fit the information and the situation, you are helping your team remain agile by valuing people and interactions over processes. |
|
 |
Smart Testers Adopt Smart Automation As technology continues to evolve, questions around the role of quality also continue. Is manual testing still required? What should the role of automation be? Where are we heading with quality? Smart testers hoping to develop their careers will have to brush up on their exposure and expertise and embrace automation. |
|
 |
Deception and Estimation: How We Fool Ourselves Research suggests that humans are biased, not-very-rational decision-makers. We believe we see things clearly when the evidence shows otherwise. Throw in a big dose of optimism, and it's easy to see how estimating software projects can be problematic. Our best hope is to construct diverse groups with varied viewpoints. |
|
 |
A Simple Rule of Thumb for Unit Testing There's a simple rule for the minimum values testers should explore: “none, one, some”—or, how the software behaves if you send it nothing, one thing, or some set greater than one. It's not comprehensive, but it gives a good feel for how the feature works at the moment. Developers can also use this in unit testing. |
|
 |
Why API Testing Is Mission-Critical With API testing, if you change how the API works—even if it now works better—it will break all of the code written by people using the API. Consequently, testers have a responsibility to make sure they are testing the same contract that was established when the API was first released. Here's how to test APIs right. |
