Quality Assurance PlanNeed a change management quality assurance
plan and want some practical suggestions to ensure rapid project
delivery?
A quality assurance plan is part of a change management plan and 
describes the review/checkpoint process that will be followed to ensure
that the change satisfies approved
change request
requirements and
complies with standards
and best practices.The following identifies some key things I like to review to ensure that change quality management. Depending on the size of the project; these might be more (or less) elaborate. Change management quality assurance plan
checklist
Change request  Was the change request reviewed by
each the data
architect, data movement designer and business
intelligence designers.Were all configuration items impacted
by the change request identified?Did the impact analysis include a
review of the following:
Data requirements Were changes required for the logical
data model?Was a peer review completed?Is all model documentation complete?Are data model changes included in the
release package?Data movement requirements Were changes required to the data
movement requirements?Was an architecture/design review
completed?Were changes required for the data
movement model?Has model documentation been updated?Are changes included in the release
package?Were changes required to the
analytic/reporting requirements?Did these changes impact any
dimensional models?Were these changes reviewed by the
data movement team?Were data movement changes required to
satisfy changes to analytic/reporting requirements?Were any changes required to
functional requirements?If so, were these changes reviewed and approved by the business
owner?Were any changes required to non
functional requirements?If so, were these changes reviewed and
approved by the architecture and design team?Was the requirements specification
updated to reflect changes?Was the requirements specification
reviewed and approved by the business owner, data architect/project
manager and test lead?Are changes included in the release
package?Requirements management plan Were all requirements updated in the
requirements management tool?Were the requirements re-baselined?Was the requirements traceability
matrix updated?Were changes required to any
architecture documents?If so, were these changes reviewed and
approved?Are these changes included in the
release package?Were database design changes required?Were data models synchronized with
production environments?Were DDL scripts tested?Were changes required to any design
specifications?If so, were these changes reviewed and
approved?Are these changes included in the
release package?Were test cases created, or modified
to reflect changed requirements?Was data data modified?Was test data modification performed
under configuration management control?Are test cases and test data included
in the release package?Quality assurance testing Was all required testing completed?Are all test results and test data
included in the release package?Are all exit criteria completed?Release plan Has a release manager been identified?Has a release plan been created?Has the object migration plan been
reviewed and approved by all stakeholders?Has the release plan been reviewed
with the release team?Release testing Has release testing been scheduled?Does the release test environment
"mirror" production?Has release testing been completed and
approved?Consider some form of project collaboration tool such as Net Meeting, WebEx, Acrobat.com, Instant Messenger, etc--This way, everyone involved with the review can work at their desk and focus on the specific items being reviewed. I have found it a lot easier for team members to follow review items on a computer screen than on hard-copy material. Summary... A change management quality assurance plan is essentially a checklist of items that should be considered before a change moves into the production environment. Some changes are minor in nature and do not require extensive review but some impact many configuration items and must follow a disciplined quality assurance process to ensure no impact to the production environment.
|
|
 |
|
