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. |
||
5 Factors That Could Be Making Your Project Estimates Go Wrong Why do our estimates for a project or a testing phase so often turn out wrong? Whatever causes underestimation, we clearly do not learn from experience, as we repeatedly make estimation errors, despite feedback showing previous errors. It’s a chronic problem. What could be driving these errors? Here are five factors. |
||
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. |
||
An Agile Framework for Improving Your Hiring Process When hiring, adopting a framework to help you screen candidates can save a lot of time. However, much like adopting Scrum to improve your software development, following a framework won’t magically guarantee perfect results. But a framework will give you the tools to start off better, and to improve over time. |
||
Dealing with a Coworker You Can't Stand If you worked with someone years ago who was highly unlikable, it’s natural to assume that the person is just as unappealing now. If circumstances bring you together again, it’s unlikely you’ll find the person tolerable. You might as well expect the worst because once a jerk, always a jerk, right? Not necessarily. |
||
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. |