First came agile, then came DevOps and Continuous Delivery, now comes Continuous Testing. Managing the balance between speed and quality is a difficult decision for many organizations. In this new reality of rapid releases, incremental changes, and short QA cycles, testing is becoming a bottleneck. The adoption of DevOps has brought this more into the forefront as testers find their place in this emerging area. Continuous Testing is a major opportunity for QA leaders to redefine the strategic role in the organization, specifically as drivers of quality within Continuous Delivery.

We will have an overview of the upcoming challenges that you will face as QA leaders and how Continuous Testing will bring you through these changes on top. We will discuss real time experiences as a tester bringing quality into the DevOps process, with key strategies used to ensure quality is infused in every step of your process. Also we would discuss about the different cases where CI, CT & CD are in practice.

 
2 favorite thumb_down thumb_up 3 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

We shall start with an Intro which might help me to adjust the content to be more relevant to the room. Presentation should take approximately 40 minutes and I will open it up for questions in the end. I also encourage the attendees to actively participate during my session. Here is a bit more clear picture on what are all the things we discuss during the session:

  • What is and What is not DevOps ? - 5 minutes
  • What are the continous things in DevOps ? Why and how we should implement it ? - 15 minutes
  • What does CI/CD translate into for a developer and a Quality Engineer ? - 5 minutes
  • The story of our project - A journey of challenges, risks, learning and solving - 10 minutes
  • Best practices for DevOps & QA. - 5 minutes.
  • Q & A - 5 minutes

Learning Outcome

Many people think like the role of Testing has become a '?' while DevOps comes into picture. With this session you will understand it's just the opposite. QA/Testing has become a crucial part in DevOps. We will have an overview of the upcoming and realtime challenges that you will face as QA leaders and how Continuous Testing will bring you through these changes on top. We will discuss real time experiences as a tester bringing quality into the DevOps process, with key strategies used to ensure quality is infused in every step of your process. Also I will share our journey of challenges, risks, learning and solving for implementing DevOps things for one of our project.

Target Audience

Scrum Masters, Product Owners, Team Leads, Business Analysts, Technical Leads, Managers, Directors, QA and any one who is concerned about Quality and need a kick on DevOps.

schedule Submitted 2 weeks ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Leena S N
    By Leena S N  ~  6 days ago
    reply Reply

    Hi Anuraj,

    Assuming that you are sharing your experience, can you change the outline to reflect the same to give more emphasis to your learnings?

    Also, share slides for the talk and share any videos of your presentations for us to understand your presentation style better.

    Thanks,

     

     

    • Anuraj SL
      By Anuraj SL  ~  1 week ago
      reply Reply

      Hi Leena,

           I have made a few updates. My past presentation videos are not yet uploaded in youtube but I was able to find one webinar link which I did. If possible I will try to find one video and update it by tomorrow. Also as you said am sharing my experience of implementing this within my projects and also giving an overall idea of what those technical stuffs are  through some story telling techniques. Hope these might suit your needs.

      Thanks,

    • Anuraj SL
      By Anuraj SL  ~  2 weeks ago
      reply Reply

      Sure. I will do that by monday ie. Nov 27th.


  • Liked Gopi Kallayil
    keyboard_arrow_down

    Gopi Kallayil - 9 Principles of Innovation at Google

    45 Mins
    Case Study
    Intermediate

    Since its founding, Google has created six products that each have at least a billion monthly users. Google continues to innovate rapidly, and in many new areas. The organizing principles and cultural elements that drive this monster of innovation are a hot topic among designers. So what are they? Find out in this engaging talk by Google’s Chief Evangelist, Brand Marketing.

  • Liked Jutta Eckstein
    keyboard_arrow_down

    Jutta Eckstein - Beyond Agile – Preparing for Digitalization

    45 Mins
    Talk
    Intermediate

    The digitalization calls for rapid organizational flexibility and adaptability. This has an impact on all dimensions of a company: its strategy, structure, and the processes. Agile will help implementing some of this flexibility and adaptability yet mainly in terms of processes. Thus, the digital transformation needs companies to change beyond Agile. Beyond Budgeting, Open Space, and Sociocracy provide the missing links for a company to fully embrace digitalization. The combination of these concepts enables a company not only to survive but also to thrive (digital) disruptions.

  • Liked Peter Scobie
    keyboard_arrow_down

    Peter Scobie - The Team Playbook: A Recipe for Healthy Teams

    Peter Scobie
    Peter Scobie
    Program Manager
    Atlassian
    schedule 4 weeks ago
    Sold Out!
    45 Mins
    Talk
    Beginner

    The benefits of a high performing team are endless. They are autonomous, empowered, responsible and effective.

    At Atlassian, we've pioneered the Team Playbook, which is our way of scaling teams by getting smarter, not bigger, and driving a culture of continual improvement. Utilised by hundreds of teams within Atlassian, we've made our secret sauce not so secret. Don't come to this session for a lesson on theory...come to this session to hear the philosophies and principles of the Team Playbook from Peter Scobie, Program Manager/Team Doctor. You'll leave this session invigorated, engaged and ready to take action.

  • Liked Mangalam Nandakumar
    keyboard_arrow_down

    Mangalam Nandakumar - Why story points make no sense for a product company

    45 Mins
    Talk
    Advanced

    T-shirt sizing. Fruit Sizing. Planning pokers. You might be familiar with any or all of these estimation (relative sizing) techniques. Story points based estimations (along with velocity mapping) is touted as a predictable method to plan for software delivery. Teams are expected to get a good sense of the effort needed to deliver a piece of work by comparing estimates with references of similarly complex work they have delivered in the past.

    The accuracy of point based estimates fares more or less in the same range as sheer gut feel. So, the natural inclination for software teams is to try and make it more accurate than gut feel. Thereby, we obsess with breaking functionality into smaller byte sized stories. We freak out when there is "scope creep". We debate endlessly about ideal days vs. person days. We fuss over the specific visual representation for the burn-up or burn-down.

    Does it matter anymore how many days the team spent chipping hard at a feature that added no value to the business? Have we made agile teams into mini waterfall teams by focussing on the wrong metrics? Can product companies afford this?

    Process heaviness in product companies can cost a lot. We need to find better ways to invest in success metrics. We need to change the conversation from productivity to value add.

    My talk intends to challenge prevalent estimation practices and contest their validity in product companies. I will also introduce ideas around capturing relevant business metrics and sizing stories using business value.

  • Liked Anuraj SL
    keyboard_arrow_down

    Anuraj SL / Anoop Mohan - Why Agile becomes Fragile for many ?

    45 Mins
    Talk
    Intermediate

    In Software Development, Agile is a way of developing code. It is essentially an unspoken promise of new functions, fixed bugs, automated tests etc delivered in a short period of time. Agile has became the reference approach for modern product development in the last few decades. However, we still see a lot of misinterpretation and abuse of its core values. This is so common and I would like to call this unwanted byproduct as fragile. If you don’t handle it with care, it is sure to shatter your product and loudly crash your entire team.Companies worldwide have faced many issues adopting Agile, a lot of the struggles and challenges are shared across different regions.

    As organizations embark on agile transformation, many traditional project managers or business and technical leads are thrown into the Scrum Master/Product Owner role after reading a book or two and, perhaps a few days of training. In the midst of changing environments, conflicting mindsets, and other change-related issues, they are expected to start operating within a Scrum team. The main problem I see these days with agile methodologies is that it has become a branding term, many organizations want to "do agile" not because they appreciate or even understand the benefits of doing so, but just because they want to get a sticker that says I'm Agile. You bring a team together, give them some work, and yet they don't meet the organization's or manager's expectations. At the end they fail to jell, fail to perform and fail to deliver.

    Why do so many organizations struggle to put in place mature Agile teams that can apply proper Agile principles and deliver awesome products? Some people will say, “Agile is hard” as an excuse to not do Agile or to become frAgile. Here we shall discuss the secrets to reboot any Agile team. Let's discuss why this happens and how we can overcome these to bring in a new cultural shift which will boost the team productivity ?

    This talk consist of a series of stories that hopefully can illustrate a different approach of implementing change in the right way. We shall also analyse if what you think of agile is exactly what it is or else what tweak you need to bring in to make it work for you.

  • Liked Anton Zotin
    keyboard_arrow_down

    Anton Zotin - Why your company will most probably not become Agile?

    Anton Zotin
    Anton Zotin
    Agile Whisperer
    FlixBus
    schedule 1 month ago
    Sold Out!
    45 Mins
    Talk
    Executive

    You have tried Scrum, Kanban, XP, Crystal and other even less known frameworks and methods that claim to help you to become Agile. You have applied them pure, you have tried to tweak them, and even you have made some homemade cocktails out of them. So yet you still can't say your company is Agile. Your Cxx-s are willing to change the company, and themselves. Your employees on all levels genuinely want to step into the Agile journey. Yet there is nearly no progress toward a real organizational agility.

    What is the secret? Why is it so hard? Why there are so many crashes on this way in our industry? Why most of the companies will still fail to become Agile, and yours will most probably too.

    I'm going to answer all these questions during this talk. We will figure out what aspects of a large-scale agile transformation have a mission-critical impact and how they influence each other. Where to put your efforts? How to cut corners? And moreover, how to survive on this journey.

  • Liked Lekha Susan
    keyboard_arrow_down

    Lekha Susan - Self Organization - Step 1:Kill the Boss

    Lekha Susan
    Lekha Susan
    COO
    Bridge Global
    schedule 1 month ago
    Sold Out!
    45 Mins
    Case Study
    Intermediate

    Business agility is all about getting results out in an agile pace. Self organized teams would seem like an answer here.

    An honest look into why self organization is a buzz word now. Why is it so important, why are companies shifting gears now. Is something terribly wrong with the normal top-down organizations?

    Takeaways:

    1. An answer to an important question - Do you need this shift?
    2. The bare necessities to get you started towards self organization
    3. How you should kill the boss in you
    4. From coding to finalizing a new office space
  • Liked PARUL PANDIT
    keyboard_arrow_down

    PARUL PANDIT - To Hear What Is Not Being Said

    45 Mins
    Case Study
    Beginner

    Retrospectives are hard. It’s hard to run a valuable retrospective and it’s hard for all team members to feel that the value has been delivered for themselves, the team and organisation. While facilitating retrospectives many of us has faced a problem of team lacking interest and engagement. Why is that some people embrace retrospectives as a way of getting better and some just feel alienated by it? Even with extremely capable scrum masters and facilitators we often end up with very few actionable team items and we feel not satisfied with team results.

    In my experience in retrospective facilitation one of the main reasons is that, we focus on solving the problems that are being discussed between team members and we only give attention to loudest, outspoken team members who can explain their issues very well. We forget about the whole layer of unseen communication. We forget about “what is not being said.” In my opinion that’s the big problem and challenge worth considering.

    This session will focus on discovery into non-verbal communication, active listening and enabling team members to share more openly and without hesitation. We will consider techniques for increasing team ability to listen and respect others opinions. We will discuss team and individual biases including some practical experiments that everyone can use with teams during next retrospectives.

    I will share with you a few techniques to dig deeper, to try to discover real reasons behind people's opinions and views. We will play the 5 why’s game and see how scrum masters can increase their own empathy.

    Together we will consider other aspects of communications including.

      • Body language
      • Individual and team psychological safety
      • “No problem” problems

    I will share with you different activities, games and experiments you can run to learn more about yourself and explain those issues to your teams. My talk is designed for people who work with teams on continuous improvements and it does apply to much wider applications than just retrospectives, standups and agile practices.

    At the end of the session you will learn practical knowledge how to run a better retrospective, have your team members learn more about themselves and how that knowledge can impact the team deliveries.

    We will consider ways to grow individual team members, as well as whole teams. We will also focus on helping scrum masters understand their current failures and learn from them and us. Trust me, we all have been there! At ucreate we failed more times that we can count but no matter what, we never stopped and we are still learning new and better ways to hear “what has not been said”

    As you probably realised there are no silver bullets to sort out all your communication issues. But there are practical ways to help team members share more and there are ways to learn more from them even when they don't speak. It will enable you you to focus on unheard voice of retro, to be an active listener, to hear what people want to share or simply “to hear what is not being said”.