The documents / artifacts created in Scrum
Filed Under Document, Product, Product Backlog, Product Owner, Scrum | Posted on January 26, 2010
First, for all those of you are asking what an artifact is. Well, if you consider the Wikipedia definition, “An artifact is one of many kinds of tangible byproduct produced during the development of software.”, it can be used in the current case to refer to the documents that we generate from the Scrum process. [...]
What’s the role of documentation in QA?
Filed Under Benefits, Document, QA, QE, Software, Testing | Posted on February 12, 2009
Sometimes, for people who are new to the software line (and specifically new to the testing business), there are questions about how important documentation would be to regular Quality work. After all, the major work is about testing some software and getting the bugs resolved, how important could testing be ? Well, the role of [...]
Details (sub-parts) of a test plan !!
Filed Under Document, Testing | Posted on January 13, 2009
A software test plan is a document that is critical to any software project. This is the document that is the proper reference to the process that QE follows during the testing process. Having a software test plan is a critical requirement of quality processes, and the document by itself takes some time to prepare [...]
Some testing definitions
Filed Under Document, Terms, Testing | Posted on December 9, 2008
Some definitions of key testing terms: What is software ‘quality’? Trying to attain software quality implies being able to meet the following goals: reasonably bug-free, delivered on time and within budget, meets requirements and/or expectations, and is maintainable. It is not easy to objectively define quality. It will depend on who the ‘customer’ is and [...]
