Randy Slade
Member for
24 years 11 monthsRandy Slade has been working on software development projects for the past 30 years. He has worked for telecommunications companies, public utilities, insurance, banking, and a medical corporation as a full time employee and as a consultant. He has worked in all phases of the software development lifecycle including: Requirements, Design, Programming, Testing, Implementation, Hot Line Support, Maintenance, and Data Center Operations. Having worked in all phases of the software development life cycle, he discovered that Quality Assurance and Testing are his passion. He is currently a Quality Assurance Testing Lead at Kaiser Permanente Information Technology in Oakland, California. He is a graduate of California State University at Chico and is a past member of the Data Processing Managers Association, Association for Computer Operations Managers, and the Bay Area Quality Assurance Association.
Randy Slade has been working on software development projects for the past 30 years. He has worked for telecommunications companies, public utilities, insurance, banking, and a medical corporation as a full time employee and as a consultant. He has worked in all phases of the software development lifecycle including: Requirements, Design, Programming, Testing, Implementation, Hot Line Support, Maintenance, and Data Center Operations. Having worked in all phases of the software development life cycle, he discovered that Quality Assurance and Testing are his passion. He is currently a Quality Assurance Testing Lead at Kaiser Permanente Information Technology in Oakland, California. He is a graduate of California State University at Chico and is a past member of the Data Processing Managers Association, Association for Computer Operations Managers, and the Bay Area Quality Assurance Association.
All Articles by Randy Slade
All Stories by Randy Slade
| How To Break Out of the Same Old, Bad Quality Routine Changing everything at once rarely works. Instead, you can make small improvements each day. Over time they add up to significant improvements. "Lessons Learned" is a powerful post-mortem process that can be used at the end of a project, phase, or deliverable to evaluate how things went, and what could be improved. |