Related Content
Protect Your Software through Threat Modeling Many software organizations are overwhelmed with a laundry list of vulnerabilities. They often have no idea where to start, how to determine prioritization, and whether or not those vulnerabilities accurately represent the threats to our applications, users, and data. Threat modeling is a simple yet effective solution. |
||
3 Ideas to Prevent ‘All Talk and No Action’ Meetings When many people are speaking in a meeting but it never translates into meaningful actions later on, it can leave us frustrated. But with some planning and collaboration, we can facilitate ways to make it easier for people to communicate better. Here are three ideas for a little less conversation, a little more action. |
||
2 Good Practices Agile Says You Don’t Need There are lots of good practices that people will tell you aren’t agile. Usually this comes from people who read a book on Scrum or Extreme Programming and took it literally. But agile is not methods and tools associated with a particular methodology; as long as you follow the agile principles, anything is fair game. |
||
A Musical Metaphor for Agile Estimation Many explanations of relative sizing in agile estimation fail to capture the mix of knowledge, skill, and effort involved in completing a task. Learning to play a song seems to capture the core ideas of estimation. With a metaphor, it is easier to come up with baselines to estimate against for your own agile sizing. |
||
Testing the Ethics of AI AI is a double-edged sword. When it's being used in situations involving sensitive personal data, such as health care, banking and finance, and real estate, security is of the utmost importance—and so are ethical implications. It’s up to testers to mitigate risks and make sure AI is used responsibly. |
||
Can We Ever Find All Bugs? This may not be what testers want to hear, but Ingo Philipp is convinced we can't ever answer the question "Did we find all bugs?" It all comes back to the fact that testing can prove the presence of bugs, but not their absence. Here, Ingo explores how we find and fix bugs, as well as the notion of quality assurance. |
||
Who Should Be Doing Automation Work? Testers often look at automation work as the next career step after manual testing. Automation work has more visibility at the project level, and people who do this work usually also tend to have a little more social status. But Justin Rohrman makes a case for why testers shouldn't be the ones doing automation work. |
||
Agile Collaboration on Remote Teams The first value in the Agile Manifesto is “Individuals and interactions over processes and tools,” and for many teams, being located in the same place facilitates these interactions. However, being part of an effective, collaborative team is less about location than it is about motivation and good practices. |