Let's Talk About the Agile Transformation of Quality Engineering
Quality Engineering should be Agile ! We all know that testing is not the same as it was before. In many cases, the barriers between Test Engineers and Software Engineers must be destroyed.
Testing and programming are two parts of the software development life cycle done by the same people, but all of them have a specified impact on not only the time to market but the quality of the software functionality itself. Taking an Agile approach means that the purpose of the tests changes from finding defects to preventing them by using different approaches and processes, like RCA, shift left, etc.
This fundamentally different viewpoint guides essential changes in how engineers work together. And while there is a noticeable shift from traditional Quality Assurance towards Quality Engineering, the primary testing principles remain the same. A product should be shipped to market fast without incidents that can impact customer satisfaction.
An Agile attitude to the culture of quality within an organization is an excellent place to start, but just integrating agility into workflows is rarely enough. Companies need to know that these changes in attitude can take time to implement, it is hard to start and process but it is always worst to do it. This transformation will require full support across the organization. Real transformation requires change at all levels, but whenever you commit to an investment in Agile and in the testing processes will drive you to success in the long run.
During the session, I will go through the experience I had and will present the potential outcome of the Agile transformation of Quality Engineering.
Outline/Structure of the Presentation
- What is the Quality of Engineering
- How to ship the product fast
- Agile transformation of Quality Engineering
- Potential outcomes from the transformation
- Promoting prevention rather than correction
Learning Outcome
- What practices to use to increase the effectiveness of the Agile transformation
- How to move from subteam to whole team contributing to Agile transformation
- What does success in Agile Transformation look like in an organization, incrementally
Target Audience
anyone working in agile environment
Video
Links
https://www.linkedin.com/in/sargissargsyan/
https://www.youtube.com/playlist?list=PLKmffI5z7mGhVTfIho7Lw1FufunKjonTJ
schedule Submitted 7 months ago
Recent Activities
- assignment Sargis Sargsyan added a new proposal Let's Talk About...schedule 7 months ago
Call for Proposals CLOSED
Ended on Nov 18 '22 05:00 PM AEDT
IMPORTANT - PLEASE READ BEFORE SUBMITTING
Submission close date
Round 2 submissions must be submitted (not in draft) by 5pm AEDT on Tuesday the 15th of November.
Update: A temporary extension has been granted for in-progress submissions until 5pm AEDT on Friday the 18th of November.
Submissions are public
Upon selecting "SUBMIT PROPOSAL" at the end of the submission form, please be aware that your proposal will be publicly visible to all Confengine users. Also expect a tweet from @Confengine advertising this. This allows the community to upvote your submission.
If you have not finished your submission and do not wish it to be visible publicly yet, please select "SAVE AS DRAFT" and return to submit it before the close date.
Why submit a proposal?
- Credibility with agile practitioners. Reputation for quality content selected by a well-qualified programme committee.
- Visibility to the world’s largest agile community, Scrum Alliance members.
- Stepping stone to speak at another Regional Scrum Gathering or a Global Gathering.
About Scrum Australia
If you are not familiar with previous Scrum Australia events and what we envisage for the 2023 event, see the Scrum Australia website.
Session formats
- Experience report with Q&A 40 mins
- Interactive presentation 40 mins
- Interactive workshop 40 or 80 mins
Interactive presentation may be primarily a talk with slides or live drawn material. Our hope is that you will include at least a small amount of interaction e.g. anonymous poll, pair discussion.
Open Space sessions do not require submission through this process. Please bring your topics to the Open Space opening circle at the event.
Audience level
You can expect there to be a mix of experience levels at Scrum Australia from people starting out with Scrum and agile to experienced practitioners with many years of experience.
We encourage you to select the most advanced level that you believe would comfortably understand the material in your session from the following options. The assumption is that your session will be accessible to people with less experience than the level advertised.
- Beginner
- Intermediate
- Advanced
Breadth of topics welcome
We welcome topics that are far broader than Scrum and application context beyond software development. The material presented should however be compatible with a Scrum based agile environment and we encourage an explicit description of how participants could apply what they are learning to a Scrum based environment. For example, in a talk about the Kanban method you could spend a minute or two explaining how Kanban could be used within Scrum Sprints or be used as a portfolio wrapper for Scrum.
Tracks
There are four tracks to select from.
- Leadership and Culture
- Practices
- Agile Everywhere
- Product
Rowan Bunning
Sally Sloley
Jess Bates
