1 / 15

Overview

Overview. Background – Small Fish in a Big Pond Proposed Solutions The Freebies Where does QA Fit in? Evolution of the Patch Process QA and Development Conclusions. Small Fish in a Big Pond. The transition of Jabber Inc into Cisco Systems Inc Culture of Hardware vs Software

idalia
Download Presentation

Overview

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. Overview • Background – Small Fish in a Big Pond • Proposed Solutions • The Freebies • Where does QA Fit in? • Evolution of the Patch Process • QA and Development • Conclusions

  2. Small Fish in a Big Pond • The transition of Jabber Inc into Cisco Systems Inc • Culture of Hardware vs Software • How our Product fits into the Larger Picture • What do you do when you realize your “baby” is desired by too many suitors?

  3. The Proposed Solutions • Split the Team • Massive Hiring • Open Source the product only within Cisco • Community Style of Development

  4. The Brute Force Solutions • Split the Team • Overly Fractured • What do you do with New Projects? • Extreme Overhead • Lots of Redundant work • Massive Hiring • Long Term Downtime due to Training • Quality Degradation of Personal • Bureaucracy

  5. The Open Source Solution Open Source it! • Benefits • Everyone has access to it • No need for additional Labor • Continue to work like Business as Usual • Problems • Potential for Out of Control Forking • Potential for Duplication of Effort • Loss of Control of Quality across all Child Projects

  6. The Community Development Solution Run it like the successful Open Source Projects run their projects • Benefits • Everyone has access to it • No need for additional Labor • Lots of Quality Freebies • Collaboration Between Business Units • Problems • Bureaucracy, lots and lots of it • How do you integrate QA into it? • Giving up Ownership

  7. The Quality Freebies • Consistent Quality Across All Child Projects • Fast Patch Distribution • More Teams Finding and Fixing Bugs • Increased Collaboration

  8. Where does Formal QA fit in?

  9. Open Source QA Solutions Crowd Sourcing! • Problems • Cisco doesn't have 1,000,000+ employees • Source isn't available to the public • The Shareholders • Resulting Release Cycle

  10. Fixing the Patch Process Patch Patch Code Code Test Cases Bug Info Bug Info Test Scripts Required Docs Unit Tests Optional

  11. Definition of Done All QA tasks must be completed before code is committed. This makes developers care more about QA tasks. Gonna have to get this tested if I want it included. Not enough testers? I guess I'll have to do some testing. Dev

  12. Developers and QA • Both are contributors • Both are responsible for completion of tasks • Neither given priority Developer Contributer QA Engineer

  13. Conclusions • Higher Quality • More Consistent Quality • Increased Collaboration

More Related