Your clients may not understand why you follow certain practices as a project professional. They may encourage you to take shortcuts that they believe will save time, money, and difficulty. You know better, but how can you convince them?
When you transition to agile and you have a reasonably size codebase, chances are quite good that you’ve been working on the product for a while. You certainly have legacy ways of thinking about the code and the tests. Now learn how to work yourself out of the technical debt you have accumulated.
Johanna Rothman describes a hectic situation involving having to deal with four people and four different projects. The folks involved are in over their heads and Johanna can't even tell if these people are qualified for their job.
Joe Strazzere is a longtime software tester and test manager, blogger, an active member of the online testing community, a sports fan, and a recent grandparent. Here, Alan Page chats with Joe about his love of testing, his career in test, and his philosophies of test management.
Lisa Crispin shares some helpful tools she has come across in her software career. Although Lisa has written automated test code since the early '90s, in the past year she's collaborated more with coder and tester teammates to write maintainable, DRY, automated test code.
The temptation can be incredibly strong for managers—especially new ones—to step in when a technical problem arises. But, that isn’t a very good show of faith in one’s team members. Johanna Rothman writes that as a manager, you have to delegate a problem and leave it delegated.
Has the agile world’s insistence on collaboration blown away the need for testers to be independent? What do we mean by “independence,” anyway? Consultant Fiona Charles argues that tester independence is essential, but that it is a state of mind that can thrive only when the whole organizational culture supports it.