Related Content
 |
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. |
|
 |
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. |
|
 |
When to Use Different Types of NoSQL Databases Web-scale data requirements are greater than at a single organization, and data is not always in a structured format. NoSQL databases are a good choice for a larger scale because they're flexible in format, structure, and schema. Let’s explore different kinds of NoSQL databases and when it’s appropriate to use each. |
|
 |
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. |
|
 |
Using Agile to Navigate through Medical Device Regulations When you test medical device software, you must be very careful. But when development wants to push a cadence of two weeks per sprint, every sprint, you’ve just got to keep up! Interpret the regulatory requirements not as a set of disabling constraints, but as a challenge to find the optimal route to navigate through. |
|
 |
Lower Risk of Downtime by Testing with Production Traffic Teams need a means of identifying potential bugs and security concerns prior to release—with speed and precision, and without the need to roll back or stage. By simultaneously running live user traffic against the current software version and the proposed upgrade, you can detect bugs while reducing risk and downtime. |
|
 |
How Embracing Differences Makes More Robust Agile Teams On any team, there are bound to be some differences. But even though work styles may differ from what you expect, they may not be problematic simply because they are different. Before making assumptions about what a teammate is doing or why, just ask to find out. Their differences may bring a helpful new perspective. |
|
 |
Creating a Community of Testers Many teams are divided by product or feature, with only one dedicated tester per team. How do you learn and grow in your career when you’re disconnected from your peers? One solution is to create your own community of testers that spans the organization. Here are some ideas to start and facilitate a Quality Guild. |
