documentation
 |
How to Use Mind Maps to Boost Your DevOps Testing Efforts Mind maps have several applications, but few QA teams are aware of their usefulness when applied to testing software. Visual, fun to play with, and free to use, mind maps can spur creativity and group collaboration. This article helps explain how to use mind maps to organize your testing efforts, supporting the rapid rate of delivery inherent in a successful DevOps organization.
|
|
 |
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.
|
|
|
|
Agile Architecture Practices for Large Scale Agile Development Although “agile architecture” may sound like an oxymoron to you, the reality is that a simple, elegant architecture is a key enabler of any successful system, particularly large scale ones. Scott Ambler describes agile architecture practices-at both the project and enterprise level-that form a middle ground between the extremes of big architecture up-front and outright hacking. Scott discusses agile modeling practices-initial architecture envisioning, proving an architecture with working code, and just-in-time model storming-that enable agile teams to benefit from architectural modeling without suffering the drawbacks of detailed design documentation. Beyond architecture, Scott introduces agile design techniques-continuous integration (CI), test-driven development (TDD), and refactoring-that build on and provide feedback to an emergent architecture.
|
Theresa Quatrani, IBM Rational
|
|
|
"Excel-erating" Test Status Reporting As a tester, you're often asked how far along your testing effort is, and when it will actually be done. This is one of the most difficult-and nerve-wracking-questions to answer, especially when a project has just begun or is nearing completion. While a tool is what's needed to help gather information and effectively answer this inquiry, many companies cannot afford to purchase or implement a complex, commercial tool. But there is a solution available in commercial spreadsheet products, particularly Microsoft's Excel. Earl Burba shows you how to use the logic and formula functions of Excel along with a combination of linked worksheets to develop an easy-to-use test status report tool.
|
Earl Burba and Jim Hazen, SysTest Labs
|
|
|
Simple Software Defect Categorization for Defect Prevention Based on her experience with software development organizations at all five levels of the Capability Maturity Model (CMM), Barbara Kolkhorst outlines simple methods for documenting and categorizing defects and how to proceed with analysis for defect prevention. Learn how these simple methods can be implemented within your organization resulting in the prevention of significant numbers of software defects.
|
Barbara Kolkhorst, IBM
|
|
|
Software Documentation Superstitions Do you need credible evidence that disciplined document reviews (a.k.a. inspections) can keep total project costs down while helping you meet the schedule and improve quality? The project documentation we actually need should meet predetermined quality criteria, but organizations are often superstitious about writing this documentation-and they let their superstitions inhibit their efforts. This presentation dispels the superstitions and shows you how reinforcements for improving the quality of your software project documentation-such as requirements, design, and test plans/procedures-can occur through disciplined document reviews.
|
Gregory Daich, Software Technology Support Center
|
Visit Our Other Communities
CMCrossroads is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.
