Skip to main content

Whole-Team Approach in Agile

Whole-Team approach is the major feature of Agile development. It promotes team chemistry by daily interactions and progress sharing. In this post, I am going to discuss about whole team approach and its benefits.
The whole team approach means involving different people with specific skill set and knowledge which are required for project success. An ideal agile team includes testers, developers and business representatives. The idea is to have a small team, anywhere between 3 to 9 team members per agile team who would work on the same workspace. As I mentioned in my previous article Role of a tester in agile team, co-location is really important to facilitate daily interactions and effective communication.
Daily stand-up meetings are conducted in whole-team approach where all the team members communicate and analyze the work progress. They also mention all the roadblocks or concerns in daily meetings which required to be handled in order to meet the sprint deadline. Below are some of the benefits of whole team approach:

  • It promotes more effective and efficient team dynamics
  • Enhances collaboration within the team
  • Provides a motivational and supported work environment
  • Leverage the different skill set of team members in project success
  • Ensures that the quality is a shared responsibility
Here, tester's responsibilities include:

  • Collaborating with business representatives to help them in creating acceptance test cases
  • Working with developers on test strategy
  • Working with developers on test automation approaches
  • Transfer and extend testing knowledge to other teams
The whole team is involved in all the meetings related to analyzing the product, estimating the work efforts and new features to be added. The whole team approach not only benefits the team at the behavioral level but helps in success of the project by ensuring that every team member takes care of the quality.


Comments

Popular posts from this blog

Remove Blanks from Excel Sheet when Excel doesn't recognize field as blank

This is one of the tricks which always helped me in removing the blank fields from an Excel sheet especially when the values are copied from other sources. I have added screenshots of a sample data to show you all the actions step by step. Here are the steps to remove blanks by using one of the special functions in excel: 1. Select your data-set (Select the column which has blank values) 2. Press F5 3. Select "Special". You will see below screen: 4.Select Blanks and click Ok as shown 5. All the blank fields are now selected, you can proceed and delete all of them by selecting "delete" from the home menu.   Here is the final result: I hope this was helpful. Share this with your colleagues and friends to help them out.

The Agile Manifesto Values and Principles

Agile manifesto refers to the set of rules or values used in an agile project. It contains mainly 4 values: Individual and Interactions Working software Customer collaboration Responding to change Over (in traditional project): Processes and Tools Comprehensive documentation Contract negotiation Following a plan Let's discuss these four values in details: Individual and Interactions : Agile development follows a whole team approach and is very people centered. Development team builds software through communication and interaction among different teams and people instead of depending on tools and processes. Individual team member offers a specific skill set and whole team involves in planning the development and testing strategies.  Working software : It is always beneficial to see the working software instead of heavy documentation. It also helps developers in getting early feedback from the clients which in turn cuts down the cost of accommodating c...

How to write a detailed Bug report?

Welcome to Software Testing Techie Blog! Bug report sounds familiar, right? As testers, we all create one or more than one bug report in our everyday work but what mostly matters is how detailed do we create them? What details we put in and how other teams get benefit out of it. BUG!! I am going to share an example related to detailed bug report and how it affects the quality. Detailed bug report is one of the best gift you can give to your and also to development team. Let's see how: A detailed bug report should have 4 major things namely severity, steps to reproduce, expected result and actual result. There could be other fields depending on what defect tracking tool you are using for example, testing estimate, test cases reviewer etc. Consider an easy example where user logs into a website and found that home screen is distorted. So Let's define all above 4 major areas: 1. Severity: Since it is related to Home screen which is the most important part of ...