|
Regular Conference Session
A Technical Approach to Writing Good Requirements for Testing
Mr. Bill Rinko-Gay- Consultant
Session Abstract:
One definition of software quality is "Conformance to requirements." If this is the definition you're project is using, you need to be able to verify conformance. But if the requirements aren't testable, how will you be able to verify them? In this presentation, Bill will discuss the problems with poorly written requirements and some of the mistakes that lead to proper and improper requirements. Since most QA Analysts are not required to write the requirements, Bill will focus on good review techniques and a development methodology that ensures the right software will be built, and QA can verify it was built right. The methodology will be applicable to all types of SDLC methods, including waterfall, RUP, and Agile. The attendees will apply the method using hands on exercises so they will be able to apply the methodology upon their return to work.
• The presentation will cover topics like the following:
• The assumptions trap
• Vague and confusing requirements
• Unreasonable specifications
• Unnecessary technical detail
• The false success of persuasion
• It's what I said, but it's not what I want
Speaker BIO - Mr. Bill Rinko-Gay
Mr. Rinko-Gay is a senior level Software Project Manager and Delivery Director with over 29 years of experience. My strength is ensuring quality development process to allow a company to achieve more at a lower cost. I work across disciplines to find ways to reduce the cost of developing high quality software. I have significant experience using Agile methodologies to improve the success of development projects.
• As Delivery Director I developed technical specifications for over 10 proposals throughout the Northeast Region for a total of $2.5 million.
• As Project Manager I increased the number of key releases for a multi-agency municipal development project from 2 to 7 in 2009 without increasing staff. I introduced Agile methods to mitigate risk and increase quality
• As Test Manager I increased the efficiency of a 37-member test organization on a development project of over 300 people by 2.5 times with increased quality using industry standard processes
• As Process Improvement Manager I defined a process for releasing bi-weekly software patches using a Scrum methodology. This allowed a program to begin reducing the defect backlog for the first time
• As Quality Assurance Analyst I defined an integrated Quality Assurance program and acted as a change agent across multiple disciplines to achieve it
• As Test Manager I established management controls to give my team and my superiors a clear picture of project progress and quality
• As Program Manager I organized an enterprise test of key financial software from data input to GL booking to ensured a problem-free deployment
• As Lab Manager I defined an ISO 9001 process model for a Test and Certification Lab which allowed the company to add three new lines of business
• I have provided training and industry presentations to align Software Quality Assurance and test with business requirements
• I developed a configuration management and release control strategy to reduce deployment errors and improve customer satisfaction
a problem-free deployment
configuration management and release control strategy to reduce deployment errors and improve customer satisfaction
|
