Agile Testing- What is my success mantra??

As more and more organizations are transitioning to agile, it’s inevitable that Agile testing is not just a concept any more. It is also not just about placing a tester in every team. What is so radically different now? How to be successful at agile testing? How to be an effective cross-functional team that embeds and honors all specialties including testing?

In this presentation, I am going to share my teams’ success with Agile testing and how we incorporated these 3 aspects – people, process and tools/techniques. This talk will benefit any members in an organization who has a stake in the product quality. It is also highly beneficial for those agile testers (from aspiring to veteran) to understand the 3 main aspects as it relates to testing and why we need to embrace- not just one, not two, but all these 3 aspects to be successful in Agile testing. 

 

 

 
40 favorite thumb_down thumb_up 7 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

  • What is agile testing?
  • Introduction to 3 aspects
  • Discussion on "People" aspect
  • Discussion on "Process" aspect
  • Discussion on "Tools" aspect
  • Why do we need all 3 to be successful?
  • Wrap up

Learning Outcome

Let’s learn what the 3 main aspects are when it comes to successful testing in an agile environment. Attendees for this presentation will be able to learn about

  • What is Agile testing?
  • Introduction to 3 aspects
  • What is the “People” aspect as it relates to testing?
  • What is the “Process” aspect as it relates to testing?
  • What is the “Tools” aspect as it relates to testing?
  • Why do we need all these 3 aspects?

Target Audience

Tester, developer, business analyst, coach, manager, Test lead, or anyone else with a stake in delivering high-quality software

schedule Submitted 3 years ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • AgileSattva Consulting LLP
    By AgileSattva Consulting LLP  ~  1 year ago
    reply Reply

    Would like to know if "People, process and Tools" with respect to TEsting means you would refer to the "importance of it", "Or integrating these three within development teams", or "What type of pepole, what process and what tools in testing". 

    I understand all three "People, process and tools" are essential (and also generic) in building any product. I see you have mentioned "People aspect in testing" would be interested to know what "aspect" of it would you cover?

    DD

     

    • Pradeepa Narayanaswamy
      By Pradeepa Narayanaswamy  ~  1 year ago
      reply Reply

      Hi Deepak,

       

      Thanks for your questions. Please see my clarifications and replies below.

      Would like to know if "People, process and Tools" with respect to TEsting means you would refer to the "importance of it", "Or integrating these three within development teams", or "What type of pepole, what process and what tools in testing". 

      As a testing specialist how you would need all these 3 aspects to be successful. For example, from people aspect, you need to collaborate with other team members, from process aspect, how you can incorporate testing in parallel to development, from tools/techniques aspect, what are the appropriate tools and techniques that will help with faster feedback.

      I understand all three "People, process and tools" are essential (and also generic) in building any product. I see you have mentioned "People aspect in testing" would be interested to know what "aspect" of it would you cover?

      I have mentioned one such example(collaboration) out of many in my clarification above.

       

      Hope this helps.

       

      Regards,

      Pradeepa

       

  • Joel Tosi
    By Joel Tosi  ~  3 years ago
    reply Reply

    Same comment on the Workshop on behaviours - please help me understand why the links for content is the same across 3 submissions.  If it is to provide context as you as a presenter, that is fine, but I would also like to see how these individual sessions have been presented before.

     

    Thanks much,

    Joel

    • Pradeepa Narayanaswamy
      By Pradeepa Narayanaswamy  ~  1 year ago
      reply Reply

      Thanks Joel. I corrected the links section. I moved my "past presentation and blogs" list to the Abstract section.

      Regards,

      Pradeepa

  • Sachin goel
    By Sachin goel  ~  3 years ago
    reply Reply

    Hi Pradeepa

    Are you in position now to share the propsed content / presentation material for the team to understand how are you driving the learning out comes.

    Thanks
    Sachin

    • Pradeepa Narayanaswamy
      By Pradeepa Narayanaswamy  ~  1 year ago
      reply Reply

      Hello Sachin,

       

      Unfortunately, I do not have the presenation material to share at this time. But, i will be more than happy to answer to any specific questions you may have regarding this topic.

       

      Regards,

      Pradeepa

  • Apoorv Saxena
    By Apoorv Saxena  ~  3 years ago
    reply Reply

    This is just a test.


  • Prasanna Vaste
    Prasanna Vaste
    schedule 3 years ago
    Sold Out!
    20 mins
    Experience Report
    Beginner

    On Agile projects we estimate user stories in order to allow team to

    1. 1. Track velocity
    2. 2. Decide scope for the Iteration
    3. 3. Help Prioritize stories
    4. 4. Help Release planning

    But most of the time we faced issues with estimation. It takes lot of time in estimating user stories, managers tend to relate estimate to number of days it will take to complete the story, in some teams estimate is equal to deadline. Most of the teams which use story points to estimate the work face these issues. This results in lack of confidence on development team when stories are taking more time to complete.

    Here I am going to talk about better alternative for both the suppliers of software products (financially and ethically) and their customers (internal and external). This alternative is being used in real companies delivering to real customers with great effect where team uses count of stories completed in an Iteration as measure of progress. Will talk about how this alternative can be used to track velocity, prioritize stories, planning Iteration and for release planning.

    I will share some exmples from my past projects where team did not use story points/velocty but used count of stories completed in Iteration to measure progress and also as best indicator of future performance.

  • Liked Allen Rutzen
    keyboard_arrow_down

    Nokia Maps Agile Journey.....(Agile Transformation, Scaling and Overcoming Challenges)

    Allen Rutzen
    Allen Rutzen
    Sunil Roy
    Sunil Roy
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    We (at Nokia Maps Division) began our Agile Journey in 2009, with a Top Down approach for Agile Transformation. The formation of an Agile Working Group (with members having Agile experience behind them) at two major sites was instrumental in shaping the transformation and scaling and also overcoming the challenges from time to time.

    The challenges were huge, but our spirit was bigger, and the high level strategy was decided. Interestingly, the Agile Working Group itself ran the whole Transformation and Scaling program using Agile values and Scrum frame work. Scrum was also used as the preferred framework for the agile projects (after success in our pilots), except where Scrum would not work. Kanban or hybrid methods were used in those few teams.

    What were the challenges faced, and how did we overcome them? What values helped us in our transformation journey?

    How did we migrate to the Scaling phase? What helped us in scaling and stabilizing?

    Can we rest easy now? Of course not!

    What are the next steps? And of course, the challenges ahead?

    Let us share our Nokia Agile journey with you, and help you all be successful too, in your Agile journey!

  • Liked Jayaprakash P
    keyboard_arrow_down

    Agile doesn't improve quality. Can we release a world class product?

    Jayaprakash P
    Jayaprakash P
    schedule 3 years ago
    Sold Out!
    45 mins
    Tutorial
    Intermediate

    There is a common concern by management that Agile doesn’t make a difference to the product quality. How do we release a product of world class quality?

     Problem is two folded:

    1. 'Definition of Done' is not created with Quality in mind, nor is it measured against the quality set at the beginning of the project.
    2. Quality Goals and subsequent adherence ensures quality is met and not just meeting 'Definition of Done' (DOD) criteria. For example DOD may be met, but quality may still be poor if not managed appropriately. How – lets discuss this through the session.

     Once the quality goals are defined for a project, Definition of Done should align with these quality goals.

    At McAfee, we have released world class quality products through Agile Methodology and Quality Best Practices together. One exceptional method we practice is by defining and tracking "Effective Quality Goals" for each sprint, and at every release.

    By driving agile projects through quality goals, we have products with ZERO defects deferred / logged by customers, 90+% code covered through automated test, 70% defects found early through development practices. This magic was not in just one project, but close to a dozen projects in the last 3-4 quarters.

    In this presentation, we will explain about how we changed the paradigm in the last 2 years and released world class quality products in a short span of time.

  • Liked Pradeepa Narayanaswamy
    keyboard_arrow_down

    WORKSHOP- Defining Behaviors as a team

    Pradeepa Narayanaswamy
    Pradeepa Narayanaswamy
    schedule 3 years ago
    Sold Out!
    45 mins
    Workshop
    Intermediate

    In lot of agile teams, often times, all the team members will be doing the grooming and planning exercise as a team. Often times, defining the behaviors is either ignored, overlooked, skimped or done by individuals on their own without a common understanding as a team.

    To solve this problem, I have used this hands-on time-boxed activity for all of my teams to define behaviors as they move along in the sprint. This will help all the team members to have a shared understanding on their users and their behaviors as it relates to their user story. This is an activity that any agile team member can take and implement the next day at work.

     

     

  • Liked Ankush Sabharwal
    keyboard_arrow_down

    Step-by-Step Process for Release Planning and Release Level Retrospectives

    Ankush Sabharwal
    Ankush Sabharwal
    schedule 3 years ago
    Sold Out!
    45 mins
    Tutorial
    Intermediate

    In the session two processes will be explained viz. Release Planning and the Release Level Retro. Step by Step approach will be discussed so that the same can be readily used in your Agile Projects.

    I have created these approaches of conducting effective Release Planning and Release Retrospectives in Agile projects. I have used these processes in various successful Agile projects.

     

    Note: Please refer to the Links section below to see the steps invoved in both of these processes.

  • Nasser Hadjloo
    Nasser Hadjloo
    schedule 3 years ago
    Sold Out!
    20 mins
    Case Study
    Beginner

    In the global village, some talks inEnglish the others in their own local langauge, when it comes to the global websites with international users, their users should be able to interact with the website with their own language.

    The process of internationalization for a large-scale application (website) is usually time consuming; I'll show you how to split the internationalization process into different sprints and implement a successful internationalized application.

     

  • Liked Kanchan
    keyboard_arrow_down

    Come! Take a plunge with us into the world of Self Organization!

    Kanchan
    Kanchan
    schedule 3 years ago
    Sold Out!
    90 mins
    Workshop
    Intermediate

    In agile teams there is a belief that the teams self organize. But do we really understand what this really means? The scrum guide simply says three things autonomous, self transcendent, cross functional.

    In this interative workshop we will experience what self organization is all about via a fun filled game. You will go back with key learnings through your own experience. 

    This session will be a combination of audience participation in activities, discussions combined with presentations and loads of fun!

    This interactive game session is for anyone who wants to learn more about  being self organized and what makes the self organized teams tick.

  • Liked Pradeepa Narayanaswamy
    keyboard_arrow_down

    We're Moving to Agile: What Do I Do with My testers?

    Pradeepa Narayanaswamy
    Pradeepa Narayanaswamy
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

    As more and more organizations are transitioning to Agile, there still exist a lack of understanding on how testing fits in the Agile teams. Is it just about placing a tester in every team? How can we realign the team members including testers from being on silos to an effective cross-functional team? Pradeepa Narayanaswamy shares her insight on the key basics of Agile testing along with understanding the Agile testing mindset and testing goals. Pradeepa also shares her ideas on how to manage defects, what to measure as metrics and what to document. Learn what you need to know as a tester who are new to Agile. If you are an experienced Agile tester, review these important basics and realign the concepts that may have been overlooked or forgotten in your teams.

     

     

     

  • Tushar Somaiya
    Tushar Somaiya
    schedule 3 years ago
    Sold Out!
    90 mins
    Workshop
    Advanced

    Have you ever thought why scrum works? That too from NeuroScience perspective?
    We all acknowledge and understand that we have moved beyond and past machine age or service era and are living in what is called “Knowledge Era”. Focus of current times is shifting from behaviours to values. From people to brain. Yet, we know very little about people or brain or its working.
    Through this talk, I will attempt to link hard neuroscience to scrum and its practices to see why it works or does not work. Also we would look at practices required beyond scrum to create an environment where scrum can flourish. Or even exists!

  • Liked Mohan
    keyboard_arrow_down

    Developing a Culture of Leadership through Lean for Organizations

    Mohan
    Mohan
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Advanced

    The goal of this topic is to look at Lean from an Indian Context and what aspects are critical for  Leadership especially while implementing Lean in their Organizations. Few concepts of how Organizations wade through their challenges to implement a Pyramid of Agile Practices both in Software and Non Software will be discussed here. This will also focus heavily on how to develop a culture of Leaders within the organization using relationship techniques of Senpai(mentor) and Kohai(protege) and also of a Sensei(teacher) .

  • Liked Naveen Indusekhar
    keyboard_arrow_down

    Enticement for Agile Team and Metamorphosis of Managers

    Naveen Indusekhar
    Naveen Indusekhar
    schedule 3 years ago
    Sold Out!
    45 mins
    Workshop
    Beginner

     

    What does productivity mean to the team? What does sponsor want from a team? What happens to Leads and Managers? A ROLE PLAY by JP and Naveen

    The topic assumes that the organization is medium or large sized (about 2K+ employees) and has recently migrated or is in the process of transitioning to Agile methodologies. Further, stakeholders are aligned to the idea and they are wholly in understanding of what and why they want to go (gone) Agile.

    Do you see a scenario in the corridor where a Manager is talking to another Manager – “What happens to us in future? Where do we go? Are we required in this organization? Agile is killing us.”

    Do you see Leads (by designation) saying to his Manager “Hey my career was set to take off – I was to become a Senior Lead, and a Manager in 4 years. Agile has made me an average team member and stalled my growth.”

    What about a team member to another saying “Man, there is no point in increasing the velocity – that becomes a bench mark for us and we need to sprint at that pace for the rest of our lives! I also had lot of time for myself in chunks when other functional group was slogging and I could read a book, attend a training, catch-up with my friends, blah, blah, blah. Let us add substantial buffer in estimates to have a comfortable life and commit on minimal ideal hours. Let us rock as a team!!!!”

    Or a Manager talking to HR “I’m unable to hit the bell curve as an entire team is involved in successful delivery of the project” and HR saying “Sorry, but you are violating global HR policy by not doing so – there ought to be a superior performer and a poor performer.”

    You may hear a team member saying “I was headed to becoming a super DBA and now you are asking me to pick testing tasks, web development task, etc. If I don’t spend 100% of my time in my domain, I will be termed as jack of all trades and master of none. This is not aligning with my career development plans.”

    A VP saying to another “Not sure if Agile has increased our productivity, how do I know it is productive? I understand teams are empowered and self-organizing, but are they self-productive? And what is this fuss about Managers’ not happy with “no-role”. Nothing should change for them.”

     

    A workshop where JP and Naveen play various characters to address these challenges in an Indian office context. Welcome to an enthralling way of presenting the core human challenges in Agile adoption and implementation.

  • Liked Joe Zachariah
    keyboard_arrow_down

    Can India be truly Agile?

    Joe Zachariah
    Joe Zachariah
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

    It's Indian Independence day today as I work on this proposal. As I read newspapers today, I understand the importance of the IT and ITES Offshore business, which has almost single handedly provided employment to millions of technically suave and English speaking folks. One question that repeatedly comes to surface is whether the Indian IT industry will be able to up its game from the servicing mentality which started the boom of IT in India. As Agile and Scrum began to become the flavour of the worldwide IT industry, many firms in India also went out on the Agile path, many of them out of pressure from their Western clients. Some of them were successful, but there are also numerous examples of failures of the Agile model and also half hearted adoptions, which have led Western businesses to believe that maybe India is not adept enough to take its game to the next level where teams can follow the Agile framework.

    My talk would be driven by my experiences of following Agile in different ways in my different teams over the last 6-7 years. My forays into the Agile ways of software delivery in India have been largely successful and I cannot see a reason why Agile will not work in India.

    In my talk, I would focus on the reasons on why Agile would work in India. Right from the way we approach diversity and inclusivity, to the way we approach our post election coalition party governance model, the Indian way of living is rife with finding innovative ways to quickly adapt to change, which essentially is the Agile mantra.

    I plan to start with a simple example. Of the Western way of cooking & dining as compared to the Indian way of cooking & dining. A traditional Indian kitchen is a sacred space. It is decorated with auspicious signs. Sometimes, it doubles up as a puja room. In many households, you are not allowed to enter the kitchen with footwear, you are expected to bathe before lighting the kitchen fire, you are not allowed to eat unless you have taken a bath - these can be metaphorically compared with the Ceremonies that an Agile team practising Scrum follows - the daily standups, sprint planning and reviews, etc. However the core delivery is the food. And no matter what ceremonies you follow and what your menu for the day is, the food comes out daily at the same time and is served everyday with the same set of stakeholders. There aren't as many tools and supporting equipment that you might see as in a Western kitchen, but at the end of the day the practices followed in a typical Indian kitchen are very Agile at heart.

    There are many other examples from Indian culture and mythology that one can refer to understand that Indians are essentially Agile at heart. Open source product groups, many of which are largely Agile, can also find a reference point in Indian culture and mythology. That which is timeless is referred to in the Indian context as Sanatan. It refers to wisdom that has no founder and is best described as collaborative and open source freeware. Every idea is accepted but only that which survives the test of time, space and situation eventually matters.

    There are many myths circulating in the IT industry that Agile cannot survive in India, since Indians cannot be trusted to be self governed and always require direction. Also Indians don't know how to have fun at work. Through my presentation I seek to dispel those myths drawing from Indian mythology and culture and essentially try to make folks understand that reasons for Agile not working in India is the same as Agile not working elsewhere. What you need to make Agile work at the end of the day, is just the belief that it will work.