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. |
|
 |
Are Your Retrospectives Adding Value to Your Scrum Team? Sprint retrospectives are often skipped, compressed, or organized in a way that doesn't provide good feedback. This is unfortunate, as a well-planned retrospective is a great way to improve how you work. Good retrospectives enable engagement and safety, distill and prioritize ideas, and create concrete action items. |
|
 |
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. |
|
 |
The ‘Third Rail’ of Project Management: Cutting Quality Scope, schedule, and resources: Whether you’re using agile or more traditional project management approaches, this triple constraint is the law of the project universe. The unmentionable “third rail” of project management trade-offs is compromising quality to deal with the other two aspects. Don't make that an option. |
