Achieving higher quality software through knowledge exchange
For this year’s conference, we’re focusing on Quality Looking Forward — how AI is changing the industry, staying ahead of hacks on the security front, managing remote teams during COVID-19, and where software quality is heading in the future.
PNSQC 2020 will be online this year, so you can easily join keynotes, technical presentations, panels, and workshops. Stream the conference to watch from the comfort of your home office, or next to your cat or dog on the couch.
For just $137 for all three days, which includes a hands-on security vulnerability testing workshop, accessibility tutorial, and agile user stories tutorial. Join us for October 12-14, 2020, by registering now.
Keynote
Keynote
Keynote
Keynote
KeynotePNSQC Talks with 2020 Keynote Speaker Jenny Bramble on Mental Models, Cats and the Future of Testing
Join us October 12-14 to reconnect with your team, get inspired, and learn how to implement software quality tips, tricks, and techniques for your own projects.
We are partnering with groups to provide diversity scholarships to cover the cost of attending PNSQC 2020 this Fall.
PNSQC Interviews 2020 Keynote Speaker Paul Gerrard on Test Automation, the “Q” word (Quality) and his thoughts on poetry.
PNSQC started the 2020 conference season with a Light The Torch event at Cvent in Portland. Topics included cyber security, communication issues, mob programming, using biologically inspired testing methods, and thoughts on vision problems in executing enterprise IT projects.
Announcing 2020 Vision: Lighting the Torch. A lightning talk event in January 2020 to kick off the call for proposals for presenting at the PNSQC 2020 software quality conference.
Webinar on Information Security: Practices & Trends in Agile Enterprises.
How has Agile evolved over the past twenty years? The Agile Manifesto was signed in 2001. Companies and teams have been discovering the agile framework and new ways to work for quite a while. What did the signers get right, and what could have been improved? What parts of agile thinking may have been lost along the way and where are we going next?
