Related Content
How to Be a Team Player Some people think of themselves as team players because they're technically savvy, hard workers, and strong contributors. But these traits alone don’t make someone a team player. Teamwork, after all, is the process of working together to achieve a shared goal. Team players collaborate to solve problems. |
||
The Importance of People in Software: A Tribute to Jerry Weinberg Gerald Weinberg's work inspired many to be better engineers and better leaders. Although he’s no longer with us, his message about the role of people in building quality software lives on in his writings and in those who have learned from him. Here, Steve Berczuk recalls some of Jerry Weinberg's most influential books. |
||
3 More Fundamentals of a Successful Testing Team Many QA managers seek a formula for creating an effective testing team. While they may pursue endless tools and lifecycle approaches, the answer is actually simpler. These three fundamentals will ensure you’re leading your test engineers in the right direction and building a world-class testing organization. |
||
5 Features of a Successful DevSecOps Pipeline When practicing DevOps, how should you include security? What's the best way to build security into an existing continuous integration, continuous delivery, and continuous deployment pipeline? Let’s take a look at five essential features of successful DevSecOps pipelines and analyze where security can benefit most. |
||
Measuring the Effectiveness of Your Vulnerability Discovery Strategies Trying to prove an app has no vulnerabilities is fraught with challenges, so teams need to choose appropriate strategies for securing apps and ways of measuring whether the time and money spent searching for vulnerabilities is effective. This means understanding how metrics apply to your specific environment. |
||
DevOps and Security: 5 Principles for DevSecOps With the trend toward a more continuous delivery and deployment process, late-lifecycle activities like security assurance present a significant hurdle to continuously delivering value to customers. DevSecOps addresses this by shifting security assurance activities, personnel, and automation closer to development. |
||
Defining Velocity for Your Agile Team When an agile team talks about velocity, it's usually how much functionality they'll deliver in a sprint, often based on historical data about the number of story points the team tends to finish. But you shouldn't use velocity as a measure of success for your agile process. Make sure everyone knows what's important. |
||
Engaging Developers in Unit Testing Unit testing is key for driving early defect identification, but organizations and teams continue to be challenged when it comes to designing and implementing unit tests. Realizing a culture of sound unit testing is often more a leadership challenge than a developer one. Here's how to instill a culture of unit testing. |