1 / 10

"What Makes SQA a Waste of Time"

"What Makes SQA a Waste of Time". SASQAG Seattle Area Software Quality Assurance Group Sept 18, 2008. Tom Gilchrist tomg@tomgtomg.com. Disclaimer. The views and opinions in this presentation are my own and do not necessarily reflect those of my employer….

teagan-stephens
Download Presentation

"What Makes SQA a Waste of Time"

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. "What Makes SQA a Waste of Time" SASQAG Seattle Area Software Quality Assurance Group Sept 18, 2008 Tom Gilchrist tomg@tomgtomg.com

  2. Disclaimer • The views and opinions in this presentation are my own and do not necessarily reflect those of my employer…. • Context is everything…your mileage may vary. • If you don’t try something different, don’t be surprised that the outcome doesn’t change!

  3. Discussion Points • Being a Professional • Value vs. Quality

  4. Value vs Quality Customers are concerned with value not just quality. • "Value is not overpaying for quality." • Value is..."the right combination of product quality, fair price, and good service.“ * From Business Week, Nov 11, 1991

  5. SW Value vs Quality QUALITY FUNCTIONALITY SCHEDULE COST

  6. Low Quality in Software • Unneeded Complexity • Rework • Missing • Extra • Wrong • Unclear

  7. Discussion Points • Being a Professional • Value vs. Quality • Quality Control vs. Quality Assurance • What does it mean to be done…how do we define it, how do we measure it? • Assumes we can baseline intermediate software engineering elements

  8. Basic Questionsin Systems Development • Is software development deterministic or non deterministic? • In software development, is variation good or bad? • Is there one best way?

  9. Process Assumes we live in a deterministic domain (at least partially). • How we remember those things that work so we can repeat them. • How we remember those things that don’t work so we can avoid them.

  10. Questions…Comments…Concerns

More Related