I lived through the first technology start-up boom and the subsequent crash that followed. Due to my success building Quality Assurance Teams in start-ups from the onset, many companies approached me and my team to assist them in their initial efforts to implement a Quality approach. I learned to ask all the right questions in order to assess their ratio of potential success and the actual importance of Quality Assurance. I turned down many startups because I predicted the eventual failure (and have a 90% of correctness) due to the answers I was given. Back in those days I rarely heard of a start-up thinking “lets just hire a entry level QA engineer or manual tester to start” but today that seems to be the norm. Since the startup boom and mobile apps boom has exploded again in the last few years I feel I should impress upon new business owners and entrepreneurs of my motto “How you strategize the importance of Quality Assurance NOW, will impact your value in your FUTURE”.
One of the most important to consider when hiring a QA team at a start-up is look for the qualities that will match your need for success:
- Can they adapt easily and still move quickly without being shaken up
- Are they willing to spend free time learning new technologies and tools
- Do they have prior experience in building QA quickly from the ground up in a startup environment
- Is their background and knowledge good enough they can make snap decisions and easily detect where a major issue is coming from quickly and relay how to fix it.
- Do they have equal knowledge in hardware – O/s – environments – services – data – software – code – design – platforms – websites and mobile applications
- Have they worked at more than one company where Agile has been implemented and worked successfully
- Do they have high energy and passion that will win over and spread to other teams – which will assist in building a positive and approachable QA team
First of let’s address the “Tester vs QA Engineer”. In my opinion and years of experience a “Tester or Test Engineer” is just like it sounds, they test the aspects of either your hardware of software. They have a limited scope on the overall product – application – system – service – project and the success of the delivery. Most testers or test engineers are assigned specific areas of product to focus on – which can lead to eventual errors due to lack of integration testing. Perhaps this is why so many years of blame on failure of a product or deadline has fallen of the software test team. It is what I refer to as the Reactive mentality.
A Quality Assurance Engineer performs what I refer to as the Proactive mentality. A Quality Assurance professional is the glue between all of your groups, they speak creative – business – technical speak and are instrumental at putting the pieces together for success.
How does a Quality Assurance professional assist you in your startup success?
- Validates that your site/product/service/application is actually what your customer wants and is delivered what they expect
- Assist in making sure you are not just a one trick pony by providing new ideas, avenues, markets to grow your site/product/service/application in to new areas.
- Assures that your customers privacy and security are not being violated or put at risk
- Assures that your customers and users will not be affected by load and performance issues
- Assists in making sure you are reaching your maximum customers base by implementing accessibility requirements for disabled users
- Assists in making sure you are reaching your maximum customer base by implementing your site/product/service/application is translated and able to be accessed in every language of your users
- Assists in making sure you are reaching your maximum customer base by verifying your site/product/service/application is accessible on every browser – operating system – device and is compatible across all promised platforms
- Assures that what your marketing has promised is actually delivered on time and meets the advertised deliverable
- Can be the most effective method to deliver customer/technical support issues to development and are communicated correctly and resolved in an expedited time
- Assures that deployments and roll-outs are executed gracefully with the least amount of impact on your customers/users
- Can utilize hundreds of tools for automating dozens of different aspects for quicker results that will affect the end results and deadlines of your releases
- Can be one of the most effective team members in an Agile environment where QA can be instrumental by understanding the entire system/software/environment/data/design/platform and providing a risk assessment if needed for a team sign-off for a release
So before you think you just need a entry level QA Engineer or Manual or Automation Tester for your startup – remember it is like building a skyscraper on ground that wasn’t checked by your future tenant or passed for foundation stability. It may appear stable and pretty on the outside but no one has looked at the interior and as you add floors you are building on you are adding to your eventual expensive costs to revise or rebuild later.
Provided below are links to Startup Statistics, Startups That Failed and Insights, Costs and Failures and Startup Lawsuits.
Startups That Failed and Insights
- 33 Startups That Died Reveal Why They Failed
- 10 Startups That Went Bust in 2014
- 101 Startup Failure Post-Mortems
- Fantastic Failures: 9 Startups that Sank in 2014
- Brutal Lessons From 4 Failed Startups
- Why Startups Fail According to the Founders
- 20 Founders Share Why Their Startup Failed
- Epic Fails of the Startup World
- 13 Valuable Lessons from Failed Startups
Costs and Failures
- Software Project Failure Costs Billions – Better Estimation and Planning Can Help
- Is Knight’s $440 million glitch the costliest computer bug ever?
- Top 10 Mega Software Failures of 2014
- Top 10 Software Failure of 2014
- Software Failures of 2014 – Entertainment Edition
- Software Failures of 2014 – Finance Edition
- Software Failures of 2014 – Services Edition
- Software Failures of 2014 – Retail Edition
- Software Failures of 2014 – Transportation Edition
- 25,000 Angry Users – Facebook Privacy Class Action Suit
- Facebook Must Face Lawsuit of Scanning Over Users Messages
- FTC Tells Snapchat To Stop Lying About Photos
- Security Expert Says SnapChat Needs “To Hire Some Really Good Lawyers”
- Snapchat Ignored Security Hole That Let’s Hackers Idenify Your Account
- Snapchat Reaches Settlement with FTC over Privacy Mispresentations
- Privacy suit filed against Path, Twitter, Apple, Facebook, others
- Instagram hit with a class action lawsuit
- FTC Should Investigate Facebook-WhatsApp Deal
- WhatsApp Reads Your Phone Contacts And Is Breaking Privacy Laws
- Facebook to Face Class Action Suit over Children’s Online Purchases
- Groupon to Settle Class Action Lawsuit for $8.5 Million
- Path Social Networking App Settles FTC Charges It Deceived Consumers