| || |
Federated QA Orgs - Leadership
Going to bring up a relatively modern topic I hope to learn from others regarding your experience in creating an effective Federated QA organizational model probably better suited for organizations where Agile Scrum is implemented across Product, Dev, QA, DevOps. We know there are camps of Centralized QA vs. De-Centralized QA hence the Federated QA model being somewhere as a happy medium. Not looking for a flame war around Centralized/DeCentralized approaches. How did you ultimately structure the Federated QA Council and what role, influence and execution did the Federated QA Council play that was beneficial in providing QA governance/guidance yet still allow for effective agility and innovation without any heavy handedness with process ?
To stay on point in transforming to Agile Scrum we (a large corp) are considering a Federated QA model which appears to be a popular lighter-weight option these days where Ive seen SOA IT organizations implement a Federated org/council model but havenšt been able to come across too many large public/private organizations in the QA world having done the same. Our current de-centralized model does not scale well nor is there much enabling of shared services/collaboration. The Federated QA concept sounds promising but looking for concrete examples from forum members that have successfully implemented a Federated QA Council/Organization. I'm considering this as a suitable management org model whereby QA teams can leverage shared quality services (labs, integration sandboxes, etc) with adequate business protocols yet maintain good levels of autonomy in their own independent teams to keep the testing, innovation and automation nimble.
Some key factors to consider are the following:
1. An active QA leadership governance body acting as cross-functional, cross-business stewards on improving & supporting QA business/technical platforms through leverage and sharing quality services
2. As a council, promote shared common services to minimize duplication of effort & enabling cross-domain interoperability
3. Be recognized as proactive enablers supporting whole-team quality approach with Product, Development, DevOps & Customer Support partners
4. Allow for autonomy yet requiring varying degrees of governance through shared integration to improve the whole
5. Federated QA Council must represent as 1 voice to organizationšs Senior Executive C-Level Staff providing visibility reporting on overall team test quality effectiveness and efficiency measures
6. Creativeness in developing QA communities that focus on automation, best practice, integration practices, common test environments
Again, not a topic that Išve seen a lot of in popular software Dev, QA, Agile forums but certainly a real consideration to adopt a Federated QA Model as part of Agile Scrum transformation.
Looking forward to responses or if you have resources, blogs, meetups to share on this subject. Not looking for flaming battles over centralized models or de-centralized models. Just looking for input from folks who have had professional exposure (med/large companies) to a Federated QA model or something similar (lightweight with enough council governance blended with agility/shared services/innovation).
Its more like an important thing according to me and if someone can learn the way of agile business and that is how it can be taken to another level because it grows each day it is an amazing thing.Good to see that you guys are doing well in it already for Quality Assurance Scrum is tremendous.
Tags for this Thread