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

Benefits of Early and Frequent Feedback in Agile development

One of the reasons why Agile is preferred over traditional development method is "Early and Frequent Customer Feedback". This is not only helps customer to get what he wants but also helps development team to understand the requirement better. There is no room for misunderstandings and delays. so no BAD CUSTOMER SERVICE! In this post, I am going to discuss about some of the major benefits of early and frequent feedback in Agile. One way to get the early feedback is "CI" or Continuous Integration. There are many tools available in the market like Jenkins which help in running automated tests when a change is introduced in the build and give the feedback on the build performance or quality. Below are some of the advantages of early and frequent feedback: Early and regular feedback helps in clearing out the misunderstanding of the requirements. Unlike in traditional method, fixing the issues or requirements change is a lot less expensive. Customer get to see the...

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.

All About Continuous Integration in Agile

In my last post, Benefits of Early and Frequent Feedback in Agile development I mentioned how Continuous Integration helps in early and frequent feedback. In this post, we are going to go deeper into the concept and see what exactly it does, how it does and its benefits and challenges. Continuous Integration is an automated system which wraps configuration management, software build, deployment and testing into one repeatable process. The best practice is to run the whole set of set into the new build (with all the new code check ins) at least once a day. This gives a feedback on the build quality. If all the automated tests passed then the build can be used to perform deeper testing. Below are some of the activities carried out by CI: Code analysis Compilation of code and generating an executable file Perform Unit testing Deploying the build onto the testing environment Performing integration testing Generating reports In our project, nightly build and...

Software Testing Techie

Search This Blog