Introduction to Agile Process Implementation

Agile Process Implementation

Introduction to Agile – Abhilash Gopi

An initial preview

To find bugs/ deviations

Migration of defects/ bugs
If the bugs migrate down the phases of the project/ product, then the cost of fixing the defect/ bug is higher.


An analysis

  • Traditionally
    # Testing has always been resigned to the end of the development phase.
    # Testing was only associated with the end product.
  • New school of thought (Agile)
    # Testing to be done at every stage, possibly everytime a feature or component is ready for release.

Pitfalls/ shortcomings of Traditional testing (in current times)

  • Pitfalls

              # Testing associated with end product, hence cost to fix the bug was higher
              # Developers assume the role of a tester hence economics and ergonomics of testing is not fulfilled.

  • End result
    # Led to huge amount of additional time and money, hence UNHAPPY CUSTOMERS.

Maturity of a tester

An organization may involve a fresher/ junior tester to assume the important role of tester without adequate training.


  • May not fully understand the application.
  • The techniques and skills may not be fully applied.
  • Hence INCOMPLETE testing.


Skilled Tester

  • A typical tester takes 2 to 3 years to graduate and mature into an experienced tester.
  • A skilled tester knows more about the application and its intricacies from the business point of view, than any other member within the project/ product team.

Shifting to Agile development

When a team undergoes a transition from a plan-driven to an Agile development process, every team is affected.
Developers viewpoint

  • Agile process value CODE Production more than plan-driven processes.
  • Where UML designs and design documents reigned paramount, there is suddenly a dearth of documents. These documents though in small number exists, they only serve to support the coding activity.
  • The programmers focus on the code production and attending meetings.
  • A small percentage of the developers will try their hand in creating their own little documents to facilitate their work schedules. If such an instance is found, do not intervene. It may percolate down to the other members and a comfortability level may be reached which augers well for the project team.
  • Some developers look at the agile process to micromanage their work.
  • To aid these developers, the managers should try to resolve issues at the earliest. This approach sends the right signals to the developer who would then respond positively to faster iterative changes.
  • Talented developers are needed for Agile process. If a developer cannot keep pace with their teammates, it is best to avoid such programmers/ developers.
  • The mantra for Agile process is “Fewer and better people”.

Author: Abhilash Gopi

Am a simple guy, loves to see the smiles on my friend's faces. So what are you waiting for? Be my friend, Guys n Gals.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s