Quality Assurance: Value Added Partner, Not Blunt Instrument |
|
| Tuesday, 08 April 2008 11:51 |
In many
IT organizations, Quality Assurance (QA) staff are not dedicated to projects,
but are "shared resources" supporting many projects
simultaneously. Vast armies of QA staff execute
defined scripts to test and certify an application once development is
complete. Because they lack application
familiarity and test only at the end of the development lifecycle, QA staff
require significant execution support, and the feedback they provide is late in
coming and often inaccurate. By
comparison, on Agile projects, QA staff are dedicated team members.
Testers are co-located with business and development staff. Because they collaborate with the development
team on formulating acceptance criteria, and engage in testing continuously
through development, QA feedback is timely and relevant. In the Agile approach, QA is less of an
encumbrance and more a partner in delivery, increasing the efficiency of the
software development process and the effectiveness of solutions produced.
In many
IT organizations, Quality Assurance (QA) staff are not dedicated to projects,
but are "shared resources" supporting many projects
simultaneously. Vast armies of QA staff execute
defined scripts to test and certify an application once development is
complete. Because they lack application
familiarity and test only at the end of the development lifecycle, QA staff
require significant execution support, and the feedback they provide is late in
coming and often inaccurate. By
comparison, on Agile projects, QA staff are dedicated team members.
Testers are co-located with business and development staff. Because they collaborate with the development
team on formulating acceptance criteria, and engage in testing continuously
through development, QA feedback is timely and relevant. In the Agile approach, QA is less of an
encumbrance and more a partner in delivery, increasing the efficiency of the
software development process and the effectiveness of solutions produced.
Read more >>
Set as favorite
Bookmark
Email this
Hits: 1150 Trackback(0)Comments (0)
|


In many
IT organizations, Quality Assurance (QA) staff are not dedicated to projects,
but are "shared resources" supporting many projects
simultaneously. Vast armies of QA staff execute
defined scripts to test and certify an application once development is
complete. Because they lack application
familiarity and test only at the end of the development lifecycle, QA staff
require significant execution support, and the feedback they provide is late in
coming and often inaccurate. By
comparison, on Agile projects, QA staff are dedicated team members.
Testers are co-located with business and development staff. Because they collaborate with the development
team on formulating acceptance criteria, and engage in testing continuously
through development, QA feedback is timely and relevant. In the Agile approach, QA is less of an
encumbrance and more a partner in delivery, increasing the efficiency of the
software development process and the effectiveness of solutions produced.

