deven_a76

 Profile Answers by deven_a76 Questions by deven_a76

• Jun 21st, 2009

 

1) When there is regular change in requirements, inform to the client regarding the same as well as the project management

2) Identify the high risk area/scenario that to be tested and communicate with the client as well as senior mgmt

3) Keep the communication channel with the client open.

4) Whnever possible sell, sell, sell the quality and importance of it

5) Identify the ROI of the team members. What if the important defet would have leaked in the production how much cost it would have to recify the defect

6) Identify/present the cost of expenditure in terms of revenues to the mgmt.

7 Last but not the least, be cool and patience.

kurtz182

 Profile Answers by kurtz182 Questions by kurtz182

• Nov 8th, 2009

 

This is a huge undertaking.  Nevertheless, here are the steps:

1)  Establish the need for QA and testing.  Make it clear to management (and constantly remind them) that the cost of poor quality significantly increases the further a defect travels goes through a program's development cycle. 

2) Obtain upper management support.  They need to recognize the value added when spending 20 to 30 percent of total project cost on QA and Testing resources.

3) Define and document the organization's software development process.  This process must be well-defined, with clear life cycle phases, entry and exit criteria, in order to establish QA procedures appropriate to each phase. 

4) Integrate QA function into the life cycle phases of development.  This is your preventative measure to improve quality and minimize defects.

5) Develop plans and procedures.  Describe test  schedules, test methodologies, and planned tests at a high level.  Testing techniques should include software inspections, code walkthroughs, peer reviews, audits, and dynamic testing.  Test phases should include unit testing, integration testing, regression testing, system testing, and/or acceptance testing.

6) Maintain quality records.  Document the results of QA audits and reviews.  Document the results of testing.  Keep these documents on hand when the need arises to justify QA and testing's worth.

7) Maintain metrics of testing activities.  Monthly reports provide listings of all QA activities for projects and are useful when demonstrating how QA and testing'adds value.

8) Insist on solid business requirements.  QA and testing must drive the authoring of clear and thorough business requirements for all projects. 

9) Insist on solid technical specifications.  QA and Testing must drive authoring of clear and thorough technical specifications for all projects. 

10) Review the requirements.  Ensure that tests are mapped to business requirements and that tests are backward traceable to these requirements.

11) Create project standards and procedures.  This is a comprehensive manual that covers everything a person needs to know to efficiently and effectively perform their duties.    

12) Conduct reviews and audits to verify compliance with requirements, standards, and procedures.

13) Use lessons learned to continually improve QA and testing processes.