All of us have our own view of what MUST be the proper New Product Development phases. I believe those are:
1. Ideation: Come-up with an idea you think it could be a market winner.
2. Patenting: Evaluate the merit of getting Intellectual Property (IP) protection for your new product idea.
3. Design: Develop non or partially functioning models of your new product idea and start soliciting user feedback.
4. Feasibility Proof: Perform various technical/business studies to determine IF your new product idea is feasible.
5. Development: Develop a product/process to yield a number of fully functioning new product prototypes as if each of them were to be used by the final user/customer.
6. Controlled Field Use Trial: Let potential users use the new product as IF it were purchased by them and generate feedback based on a previously approved protocol.
7. Design-Verification/Validation: Fine-tune new product design/development and complete design verification/validation studies to confirm the new product meets User Requirement Specifications (URSs) per its respective Labeling Claims.
8. Regulatory Filing (if required): Prepare any required documentation and submit it to appropriate Regulatory Authorities for securing their approval to market it.
9. Full Field Use Trial: Repeat above phase 6 but using a comprehensive pool of potential users/customers.
10. Scaling-up: Scale-up your process so your new product could be manufactured in high quality/low cost conditions.
11. Technology-Transfer: Develop documents' list for new product's production in high volume.
12. Process Validation: Validate your process so it produces final product consistently meeting specifications.
13. Manufacturing: Start manufacture and ship product to market.
14. Launch: Launch product and monitor its acceptance by the user.
15. Line Maintenance/ Improvement: Compile, analyze user feedback and continuously improve product.
What is your opinion? Please explain, if you could.
Each QA automation team has its own specific priorities when choosing a test automation tool to facilitate the UI regression testing process. But what approach is more popular: a lightweight solution which is simple and quick grasp (but will not cover all your regression testing scope) or a full-scale test automation framework which can do much more but will require lots of time to create and maintain the test coverage? What would you/your team/your manager(s) choose and why?
Can anyone recommend SQA Forum to join or SQA user group in Boston area? Office is in Boston. Interested in following topics: Selenium WebDriver and UFT automated frameworks, agile testing, mobile testing non-apps (browser based websites on mobile devices).
I am a test automation specialist and test manager and I am seaching for ideas in which way I have to change my mindset, my knowledge and tool expierience when beeing part of a development team or company for developping digital services and products?
It is seen that many vendors publish thousands of android apps in a month. Unfortunately, most of them remain unnoticed in the app store. Lack of proper testing is the primary reason for the failure of these apps. Professional Android App Testing Services know how to make an app user friendly. Can you say some unavoidable aspects for all android app testing services?
i have one application to test. it has caling functionality. its impossible to test application in all avaliable android device. so give me way to teast it. i have also tried amazon cloud services. but it has limited devices.