Test/Performance Eng.
Home » Test/Performance Eng. » Product Testing

Portfolio

Posted by Mahesh Mathpal | Dec 23, 2010 | (0) | Add a Comment  |   Bookmark and Share

Asking question and finding their answers, is one of the best way to understand a subject. Same principal, we can apply to collect information to make the Testing Project’s portfolio.

Please see below the exhaustive list of question to be asked to client, you, colleagues, documents, Subject matter experts, and etc.

You may like to add/delete/modify this set of questions depending upon their relevancy.

 1.     Portfolio Management

 Test Basis Related

1. Do you have the test bases? Is so, what are those?
2. Could you please share with us your previous test basis, which might include test cases, test
     results, bug reports and so on and so forth?

3. Could you please share with us the architecture and Design documents?

 Product Related- Non-Functional

Could you please share with us?

1. How stable is the product?
2. How frequently the product crashes?
3. What are the MTBF and MTTF?
4. Specific patterns of the product crashes, if any?
5. How frequently the application undergoes changes?
6. Is there any Change Management in the process?
7. Do you foresee this product be retiring in the couple of years to adapt the new technologies?
8. Do you have any migration plan?
9. Do you have identified the new technologies and platforms?
10. On what time zones the application will be running?
11. Do you need multilingual support?
12. You have any planned security measures?
13. What are the security protocols this product will use?
14. If you need role based security levels?
15. If you have any pain areas in the current look and feel of the system?
16. If the current system in intuitive by nature?
17. If you want your system to be portable?

 SLA, IPR, Support and Impact of Failure Related

Could you please share with us?

1. Your support SLAs with your customers?
2. The sensitivity aspects of your customer artifacts?
3. Is there any IP involved in any of your customer or your artifacts?
4. Is the application data intensive?
5. Will you provide us the data generator tools or we need to create this on our own.
6. What are the platforms you would like to support?
7. What is the impact of failure of this product on your business and on your end customer?
8. What are the liabilities in cases of failure of this product?
9. What the logistic support required and how they will be achieved?

Back up and Disaster Recovery Related

1. Do you need daily/weekly /Monthly backups?
2. Do you have a disaster Recovery plan in place?

Status Reporting and Vendor Interaction Related

1. If you have any reporting and meeting protocols in place for example Daily status calls over VC
    or telephone etc.
2. The protocol involved in interacting with your other vendors?

0 Comment for this post

Post a Comment

Required Information *
Name* Email*
Comments*  

*

In accordance with our comment policy, we encourage comments that are on topic, relevant and to-the-point. Once submitted, your comments will be published by the Impetus blog moderator. We will remove comments that include profanity, personal attacks, racial slurs, or threats of violence, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.
Cloud and SAAS model for ISVs Big Data : Open Source Revolution Mature Big Data Open Source products adding excitement
Cloud and SAAS model for ISVs Cloud and SAAS model for ISVs Pankaj Mittal,
CTO & Sr.VP, Impetus
More More More Videos