Entries Tagged 'Agile Testing' ↓

Agile Retrospective Meetings – Why It is Necessary and Some Fun Ways to Conduct It

Agile Software development is  a set of methods and practices that are based on the Agile Manifesto. Agile methodology emphasizes team collaboration and frequent delivery of a product.

One of the 12 principles listed in the in Agile Manifesto is:

“At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.”

Continue reading →

Agile Testing On The Rise – Boon or Bane?

Agile – has become the trend of IT. Most of the projects are AGILE nowadays and the role of a tester is very significant.

Even before we touch on Agile Testing let us understand the concept of ‘AGILE’.

------------

Agile is a methodology that evolved from our Iterative or Incremental methodology of development – Almost 2+ decades of Agile Manifesto. Over these decades, Agile has a very comfortable place in the hearts of Developers, PM’s and Customers.  Continue reading →

How to Make Agile Estimation Process Easy with Planning Poker

An art of estimation is known to all.

We estimate every day in our lives. Most of us can estimate the weight of the vegetables just by holding them; we can also gauge the ripeness of a fruit by its aroma.

In today’s article, we will learn about Planning Poker also known as Scrum Poker Cards, an agile estimation and planning technique, which is very popular, easy, and simple technique in current days.  Continue reading →




What is Technical Debt and Why QA Testers Should be Concerned About It?

Technical debt is a metaphorical idea which argues that just as one may run into debt problems in finance, software organizations encounter something similar in the buildup of unfinished work during past projects and version releases/sprints.

What is Technical debt?

It represents the effort needed to fix the issues/defects that remain in the code when an application is released. In simple words – it’s the difference (in terms of bugs) between what is expected and what is delivered.

When a development team is busy working on a project and fixing bugs unfortunately, many new bugs appear. Out of Continue reading →

How to Improve Software Quality Using Continuous Integration Process

In the first part of the article series, we understood the nuances of Continuous Delivery (CD) where we have production ready software at any point via continuous feedback loops. Continuous integration (CI) is the real meat behind the CD process and is the reason that makes Continuous Delivery possible.

To understand CI, let’s take the terms at face value and deduce a basic definition. The first word means “ongoing” or “frequent” and the second “merged” or “made part of”. So CI is a process where something is being “merged”-“frequently”.

Logically the next question is: What is the something being merged and where is it merged?

Continue reading →

Continuous Delivery: How to Have the Reliable Software Releases to Production at Any Time

In this two-part article series, we will focus on Continuous Delivery (CD) and Continuous Integration (CI), starting with an at length discussion on Continuous delivery today.

Software development has seen a steep outlook and approach difference to keep up with the current market trends and consumer needs. While the traditional waterfall approach was more sequential and planned, it has setbacks in terms of satisfying customer expectations of the final product.  Continue reading →