We have 5256 guests and 9 members online
Featured Whitepapers
- Apples, Oranges, and Acorns - All Agile Development Tools Are Not the Same
- One's Enough for Agile Application Development Management
- Requirements Management 101 – 4 Basics Everyone Should Know
- Tips on Requirements Traceability – Learn How to Control Change and Improve Quality
- Scaling Continuous Integration to Large and Distributed Teams
|
Effective Agile Testing: Asking the Right Questions - November 2008
Since the September issue of this year we’ve moved away from themed issues to mixed-subject issues where each issue has a variety of articles. This month’s issue is no different; you’ll find articles on selecting your first project, questions an effective Agile tester should ask, a story about a fictional offshore project, and much more.  Rather than summarizing the articles in my notes, I’d like to share a story and let you read the summaries below. Last week I was working with a group who are two years into an enterprise-wide Agile adoption at a large organization. One of the questions that kept coming up was a variant on “how do I get person X to do action Y?” This was not the only time I’ve been asked this question, and previously I would go into a long discussion/discovery session to understand the context of the environment and then share my experiences in similar situations. This time, however, I chose not to do so. I answered the question differently. My answer was that you cannot get person X to do anything, so just get over it. Instead, my advice was as follows: You can practice action Y yourself. You can talk to person X and try to find out what his or her goals are and help him see if action Y addresses those goals at all. You can try to change the environment by using big visible charts so that person X can see how not practicing Y affects the group. But in the end, person X has to decide to do action Y. If action Y does not meet person X’s goals, they will not (and should not) practice it. (If you are high up the food chain, you can probably force person X to do your bidding, but that is usually less than fully effective.) So why this story? Hopefully it was a bit more interesting than a summary of the articles you are about to read since they are already paraphrased below anyway. This also is another way to view the articles we bring to you every month – a chance to see how others have practiced Agile successfully. Possibly the articles are a source of validation if you know a person X who might not see the value of practice Y. Finally, the publishing calendar for 2009 is available. I would like to remind and encourage all our readers to consider becoming authors by contributing articles. Since we are now publishing mixed-subject issues, every month is the right month to submit your work for publication and feedback from the community. You can read more about what we are looking for in September’s Letter from the Editor and if you decide to contribute please review the submission guidelines. Amr Elssamadisy
|
|||||||||||||||||||||||||||||||||||||||||||
| Last Updated on Wednesday, 08 September 2010 10:12 |
Agile Marketplace - Announcements and Special Offers
The Business Case for ALM Transformation
Are legacy systems holding your company back? Breakthrough these technical constraints with an open and scalable environment that meets your unique business need to transform. There is no reason to be locked into an obsolete platform. The output of a number of recent transitions from legacy systems, this is practical white paper shares lessons learned and illustrates how guidance and enablement can pave the way for change.
Download this Whitepaper