process improvment

Quality Department Involvement in Project Lifecycle Part 2

This is the second and the last part regarding quality department involvement in project lifecycle, for introduction please look at Quality Department Involvement in Project Lifecycle Part 1

Acceptance phrase
If all previous steps have been made by my description, this step looks fairly straight. We can easily accept the iteration with ready to use acceptance tests connected with requirements. Is there any important activity ? Yes:

  • Acceptance testing requirements by the owner
  • Accept the code coverage percent (project manager + quality manager)
  • Supervision the revision of the code

Testing phase
This step is fairly simple for testers community 🙂 the majority has already been said, it is obvious that the involvement of the team is at this point reaches an extreme. It is very important to not close yourself in the four walls of the testers room at that moment. We should be connected with developers and project manager to communicate problems and successes.

  • test along scenarios: automation and manual
  • exploratory Testing
  • test report creation
  • mistakes clarification to business owner
  • communication with project owner and developers

Release acceptance phrase
We closed testing period with or without the delay, we have a list of fix and not fixed issues together with the classification. How to decide whether we have the full knowledge to release the product to the customer? Head of the tests should participate in release accepting, he will bring not only knowledge about whether it is good or bad but also their views on the importance of these issues.

  • test report
  • deep issues analyze
  • decision of quality assurance team

Release deployment
Another very important step depends on the product and its architecture. If only our production environment is available and ready to do the tests, we must provide such service. When dealing with Web application in SaaS model or the internal system, set up an test for the target site. When we not have access to production sites we must check the route from our company to our clients: installations, auto update engines, etc.

Release clean up
Every successful release should be followed by the clean up. We are often excited and tired after testing stage but it is very important to do some tasks which prepare us for next iteration. What can we do to ensure that all developed and discovered goods in the testing phrase and will be used to improve quality in the future?

  • Rollout test environment
  • Freeze test environment
  • Backup test data
  • Backup test reports
  • Plan new requirements / features based on test observations

Release maintenance and support
When we have our release on the market we are in the maintenance phrase which takes a long time but is in fact made up of many small application life cycles. The difference is that now we are working not only with our internal business analysts but also with the customer, which often does not match the standard processes of thinking. We can help with:

  • issues prioritization
  • client support observation
  • consult support manuals

Summary
That’s all there on this subject at this moment. As previously written, this knowledge is not complete, but merely an attempt to systematize the subject and arouse discussion.
Recently I came to the problem of quality management in ITIL v3 framework, next article of this kind will be treated precisely the approach to ITIL processes. I’m not a big fan of Big Names, but live creates different scenarios 🙂

Discussion

No comments for “Quality Department Involvement in Project Lifecycle Part 2”

Post a comment