TechWell Insights
The Latest Stories
|
How to Be a Team PlayerSome 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. | 
|
|
Creating a Company Culture Where Agile Will ThriveA so-called generative culture has all the characteristics necessary to support self-directed teams, shared responsibility, experimentation, and continuous process improvement. But what about the rest of us? Most large organizations don't have a culture where agile will take hold so easily. Here's what needs to change. | 
|
|
Notable Challenges: NASA, LEGOs, and YouTubers Did you ever say to yourself, "What a brilliant idea! How did they come up with that?" One school of thought holds that the best "aha" moments take place when someone’s alone. However, another theory—shared by organizations such as NASA and LEGO—is that a problem shared is a problem solved. |
|
|
Guaranteed Methods to Ruin Your Test AutomationAfter working to develop the test automation patterns used by experienced practitioners to solve common test automation issues, Seretta Gamba started to consider what can ruin a test automation effort instead. Here she shares two sure-fire methods that can destroy your test automation. Steer clear of these examples! | 
|
|
The Importance of People in Software: A Tribute to Jerry WeinbergGerald 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. | 
|
|
Signs of a Project Headed for TroubleProjects rarely get in trouble suddenly. More often, the descent into trouble is gradual, and the signs are easy to miss—but they are there. If you detect any of these potential signs of possible failure, it would be wise to take steps sooner rather than later to address them and get the project back on track. |
|
|
Improving Requirements with Preemptive TestingMost product defects are created during requirements definition. To significantly reduce and prevent requirements problems, consider making their management your software testers' responsibility. They can identify requirements defects as they are being developed, as well as work out mitigations for their root causes. | 
|
|
5 Factors That Could Be Making Your Project Estimates Go WrongWhy 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. | 
|