Welcome

Change management

Articles

2012 Technology in Review
2012 was an amazing mix of challenges, achievements, and even a few notable disasters for those in technology. Here are a few things to consider in understanding the year behind us and preparing for the peopl challenges that no doubt await in the year ahead.
After Ten Years: One Person's Stance on the Agile Manifesto
Joe Farah often writes about ALM relative to agile. In this article, he lays out his views on the Agile Manifesto specifically. From collaboration and clear communication to the focus on individuals over tools, Joe covers what works, and what he thinks could work better.
Continuous Process Improvement: From Help Desk to Fix Release
Listening to your customers is absolutely mandatory to ensure their satisfaction and making sure they know you listened to them is just as important. Wayne Goldstein takes a look at how simply resolving an issue a customer brings up isn't always enough. Take a look with him at continuous process improvement from the help desk to releasing the software update to fix a problem.
Personality Matters: Process and Quality
Engineers know the importance of process and quality, and many engineering disciplines emphasize quality control and quality assurance. Some people enjoy the challenge of focusing on quality, while others find it a necessary but less-than-exciting chore. Leslie Sachs look at some of the factors that impact process and quality.

More

Better Software Magazine

Surprise! Making the Most Out of Your Most Surprising Moments
Lee Copeland explains that surprise is often an indicator that discovery, learning, or even delight may be just around the corner. The surprise itself can be amusing, enlightening, befuddling, disconcerting, or frightening, but surprise should not be the end of the experience; it should be the beginning. Analyze the surprise to learn why you didn't see it coming and what you gain from that.
Working Together—Not Just Working Together
People collaborate—and don't—in a variety of ways. Johanna Rothman examines what happens when collaboration isn't working, and how to make it work. Watch for several barriers to collaboration including those imposed on people by the organization itself.
Passing the Buck

One way object-oriented systems address the maintenance problem is by using "implementation hiding." Clients of an object shouldn't be dependent on its inner workings--they should only have to know how to talk to it.

Fighting Temptation
Programmers must balance time, business needs, and a long-term maintenance profile while producing code. Are you willing to accept the easy path now, even if it means trouble down the road? Tod Golding explains that the fastest way may not always be the right way.

More

TechWell Stories
Should Agile Teams Minimize Branching?
Software Configuration Glitch Shuts Down Chicaco trading system
Six Questions to Ask When Selecting a CM Tool
Does Software Configuration Management Follow CM's Core Processes?
Recent Corporate Acquisitions Highlight Growth of DevOps

Recommended Web Seminars

May 21 Quality Engineering: Build It Right the First Time
May 23 Key Principles to Mobile Performance Testing
On Demand 7 Habits of Highly Effective Agile Teams
On Demand Achieve Scriptless Test Automation Utopia!
On Demand Best Practices for Post Data Center Migration Testing

Featured Resources

» Skytap Automation Pack for Microsoft VS Team Foundation Server | Skytap
» An Innovative Approach to Integration Testing | IBM Rational
» Improve Quality and Decrease Time to Market with Requirements Management | PTC
» Cloud-Enabled Software Development and Testing | Skytap
» Perfection Just Became Mobile: An Easy-to-Use Solution for Mobile App Testing | Micro Focus

Visit Our Communities

The home for software testing and QA professionals—practical advice on test automation, test management, test techniques, and more.
Bringing you today’s best agile ideas and thought-leaders with how-to advice on the latest agile development & methodology practices.