|
The Benefits of Pair Programming This article details a team’s experience in implementing pair programming as a way to get work done as part of its agile transformation. It delves into the many positive results from the pairing experiment, as well as some of the negatives that were encountered, and weighs whether developers think pair programming is a worthwhile endeavor.
|
|
|
Accelerating the Adoption of Technical Practices Agile teams are supposed to take responsibility for how they work and how they learn. But what if you need to jump-start that learning? Agile transformation is about making this happen rather than waiting for it to happen. You need to get your team to learn the technical side of agile, and soon. Here are some effective approaches.
|
|
|
QA Management: All Bark and No Bite? Mike Talks shares with us the unlikely story of how his pet German Shepherd inadvertently became his team's QA manager. Talks explains how his German Shepherd was able to gather people together and have them talk to each other, similiar to what a QA manager does—keeping people on task, handing out assignments, and following up with team members.
|
|
|
Think of the People First Johanna Rothman tackles the Paterno/Sandusky scandal and notes that the truth has a way of always coming out. Will you still have your integrity when the truth emerges?
|
|
|
Keeping Secrets Test data has long been a challenge for testing; privacy legislation, identify theft, and the continued trend towards outsourcing has made it even worse. Just establishing and maintaining a comprehensive test environment can take half or more of all testing time and effort. In this column, Linda Hayes adds in the new and expanding privacy laws that inevitably limit your testing options. Yet from the quagmire of laws and company standards, better testing can emerge.
|
|
|
Always Assume Your Assumptions Are Wrong A potentially serious impediment to success in software projects is false assumptions. Both yours and everyone else's. If you act on false assumptions as though they're true, such as by assuming you understand exactly what your customers want, you may find yourself faced with flawed software and failed projects. In this column, Karten explores false, conflicting, and hidden assumptions, and how you can "surface" them.
|
|
|
The ROTI Method for Gauging Meeting Effectiveness When I visit software organizations, I often hear complaints that we spend too much time in meetings. Many people spend a significant portion of each day in meetings. Wouldn't it be great to give some of that time back?
|
|
|
Ten Ways to Guarantee Project Failure Naomi Karten specializes in helping companies succeed in their projects. In this column, however, she gives tongue-in-cheek advice on how to make a project fail. Read on to see if these steps to failure are part of your organization's modus operandi.
|
|
|
But I Don't Have Time! Overworked software professionals sometimes skip things they know they should do, because they "don't have time." In this week's column, Karl Wiegers asks you to think about what you really mean when you say you don't have time, and he cautions you to take time to make time.
|
|
|
Giving the Human Touch to Software Yogita works as a QA/testing professional with Mindfire Solutions, and has written a number of articles on QA and testing strategies. Yogita is currently exploring thoughts of beauty as an area of testing and its relation to usability. Her role at Mindfire has been to implement Quality processes throughout the organization and build a dedicated testing team. The team recently published a White Paper “Porting projects: Test techniques,” downloadable from www.mindfiresolutions.com. Yogita can be reached at [email protected].
|
|