Skip to main content

John Tyson

John Tyson
Profile picture for user jtyson

Member for

25 years

John Tyson has been testing software and systems for over 20 years and considers himself fortunate to have worked almost exclusively in Agile environments (called RAD back in the day). He makes extensive use of black box and exploratory testing and is a strong proponent of lean software development. Clients have included start-ups, public sector, non-profits, F500 and multi-national corporations.

Mr. Tyson holds a Professional SCRUM Master I (PSM I) certification from scrum.org.

Job Function
Consulting
Industry
Business Services - Consulting - Non-profit
Interests
Agile
Architecture
Business Analysis
Development Lifecycles
Lean
Process Improvement
Project Management
Quality Assurance
Requirements
Test Automation
Testing
Country
United States
Profile picture for user jtyson
John Tyson

John Tyson has been testing software and systems for over 20 years and considers himself fortunate to have worked almost exclusively in Agile environments (called RAD back in the day). He makes extensive use of black box and exploratory testing and is a strong proponent of lean software development. Clients have included start-ups, public sector, non-profits, F500 and multi-national corporations.

Mr. Tyson holds a Professional SCRUM Master I (PSM I) certification from scrum.org.

All Articles by John Tyson

All Stories by John Tyson

Infinity symbol Has Continuous Deployment Become a New Worst Practice?Software development has been moving toward progressively smaller and faster development cycles, and continuous integration and continuous deployment are compressing delivery times even further. But is this actually good for businesses or their users? Just because you can deploy to production quickly and frequently, should you?
The Testing Tsunami

The testing tsunami is the tidal wave of testing work that occurs at the end of development. The developers' workload starts high and progressively decreases until all work is completed. This is just the opposite of the testers' workload. As more code is completed, the testers' workload increases. By being aware of the massive workload that awaits testers at the end of the project, do everything possible to move up testing activities as early as possible. This will lessen, although not eliminate, the testing tsunami.