documentation
Articles
 |
Slim Down Your Test Plan Documentation Test plans are essential for communicating intent and requirements for testing efforts, but excessive documentation creates confusion—or just goes unread. Try the 5W2H method. The name comes from the seven questions you ask: why, what, where, when, who, how, and how much. That's all you need to provide valuable feedback and develop a sufficient plan of action. |
|
 |
Don’t Be Fooled Into Thinking Agile Means No Documentation This is a common misconception of those inexperienced with agile, who choose this methodology on the basis of thinking that their project can be delivered more quickly and easily by avoiding documentation. But agile is not an excuse for skipping documentation. While some information will always need to be captured in written words, there are techniques that can be used to reduce documentation but will still give the customers what they want. |
|
 |
Specification by Example: Collaborating on a Scope without High-Level Control Understanding what the business users are trying to achieve can significantly help you focus the project on things that really matter. In this excerpt from Gojko Adzic's book Specification by Example, the author offers some tips for effectively collaborating on the project scope when you don’t have high-level control of the project. |
Recommended Web Seminars
Featured Resources
Visit Our Other Communities
AgileConnection is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.