Related Content
Continuous Risk Management in Cybersecurity Traditional cybersecurity is reactive. It responds to threats as they surface while trying to minimize the chance they will ever be an issue. Yet in an environment of constant change and evolution, this is insufficient. What your business needs to do is approach cybersecurity from the perspective of continuous risk. |
||
Fueling Innovation through Design Thinking Organizations must embrace new technologies in their product engineering efforts to stay ahead of the curve. But there is another quality that will be key this decade to giving product teams a proactive advantage: design. Design thinking should be embraced not just by designers, but by everyone involved with a product. |
||
Machine Learning and Deep Learning: What's the Difference? Many people think that machine learning and deep learning are each just a fancy way to say artificial intelligence, but that is a misconception. Both terms represent subsets of AI technology, but they are different, and their differences dictate the functionality and application of these two software solutions. |
||
To Be a Better Tester, Ask the Right Questions Critical thinking is a core trait a software tester needs to succeed, and asking questions is a great skill to help. Questioning brings out the required information, breaks assumptions, and enables everyone on the team to give their perspectives. But there's an art to asking the right question at the right time. |
||
Pros and Cons of Codeless Test Automation To create automated tests for software applications, testers have historically needed to be able to code in programming languages. Codeless testing eliminates the need for scripting from scratch every time, but in addition to its advantages, there are also some drawbacks. Is codeless automation right for your team? |
||
2 Ways to Get Better at Test Automation Many people in testing roles want to grow their skills and learn to build some tests with code. But no matter how well you test, automation is programming work. If you want to get better at automation, your best bet is to get into a role where you are dealing with code. Here are two ways you can break in and learn. |
||
Scrum Roles, Goals, and You The Scrum Guide specifies that there are three roles: product owner, developer, and ScrumMaster. It’s essential that a Scrum team have each of these roles to help it work well. But depending on how you implement the roles, you may end up hurting rather than helping your Scrum process. Focus on goals, not job titles. |
||
The Problem with the People-Management Bell Curve Conforming team performance evaluations to a tidy bell curve is a simple, quantitative solution to the challenging problem of rating employee performance. However, it doesn’t work. It’s unrealistic (not to mention counterproductive) to force-fit employee evaluations to the curve when that doesn't reflect their work. |