Software Testing Life Cycle for Agile

-
Software testing life cycle consist of the set of activities which are being carried out while performing testing of some software or product. There will always be some operations, be it Waterfall model, V- Model or Agile. The methodologies are more or less the same except that the quality and delivery of the product is differed. This article talks about the Software Testing Life cycle for Agile specifically.

Software Testing Life cycle for Agile-
It is imperative that the Agile Team members are align on the same page, so various activities are being promoted while working in an Agile project such as having Daily Stand up call, retrospective meetings, Program Increment Planning(PI Planning), Story grooming and so on. All of these activities are being performed as to have a clear communication between the Agile team members and the business.

As shown in the diagram above, Let's discuss about the Life cycle of Agile -


  1. Impact Assessment - This is relative to the introduction of New Feature as in what features might get impacted from Regression functionalities, so a QA team member has to analyse and work accordingly.
  2. Agile Testing Planning - PI planning is the event where the story sizing takes place and the scope of testing is decided until confidence vote is gathered from the board members. So, proper planning is followed for the successful delivery of the product.
  3. Release Readiness - Team member decides if the product or the software is fit enough to move into the production or the changes gets roll back for more testing to be carried out.
  4. Daily Scrums - Daily scrum calls are being conducted to make sure the progress and the timelines are met as per the planning. Daily tasks or weekly tasks are being discussed and rolled out.
  5. Test Agility Review - Risks are being discussed after the stakeholders and RTE's gather.  Process is improved continuously to mitigate the risk for the upcoming PI's/ Releases.
The mindset of stake holders are now changing and they are adopting Agile methodologies for the quicker and reliable delivery of the software product. One needs to learn different levels and processes include in Agile.

Hope this article was informative. Keep Learning! 

Comments

Post a Comment

Popular posts from this blog

Azure Tutorials Series - Azure Networking

-
Image
In this article, we will learn about Azure networking concepts such as architecture, microservices, virtual networks, VPNs, subnet, VPN gateways and most importantly Network Security Group(NSG). All these terms are to be understood if you appearing for AZ900 Microsoft Azure Fundamentals exam. Azure Networking In previous articles we have learnt about Micro- services and how they work, these are alos loosely coupled architecture. Some of the features includes Independent components interact with each other with the help of queues Can be updated and deployed independently Highly scalable Supports Asynchronous messaging N-tier Architecture Supports loosely coupled architecture Application divided into multiple tiers such that higher tier can access lower tier but not vice versa Tiers are re-usable and can be updated or replaced easily without any hassle. Three-tier in general Web Tier(front end) Application tier(back end) Data tier(Storage) Virtual Network Isolated network shared by few g...
Read more

Testing in CI/CD

-
If you are part of testing fraternity you would have heard CI/CD numerous times by now. It's the talk of the software testing town. In this article, we will cover the basics of CI/CD, what actually it is and how it is implemented in software testing. What is continuous integration? In simple terms, development teams can integrate their code into a shared repository. This helps in maintaining code quality and identifying potential issues with the local version of the code at an early stage. What is continuous delivery? Everything that is being continuously merged by the development team, is continuously deployed to the live environment. Continuous delivery is often coined as ‘Continuous Deployment’ as well. Since most developers work in parallel, continuously integrating their code into one repository would mean that the master branch is continuously updated with new features. In order to ensure that there is no compromise in the code quality with so many changes...
Read more

Azure Tutorials Series - IaaS vs PaaS vs SaaS

-
Image
We already have covered Public vs Private vs Hybrid differentiation in the previous article. In this article we will be covering three categories of cloud computing with relevant examples and details. Most of you might already be using these services in your daily day-to-day tasks unaware of the face that your organisation has already started the transition into the cloud. For an example, Office 365 is a active SaaS(Software as a service) that most of us uses, VMs are examples of IaaS(Infrastructure as a service) and Azure SQL Database is PaaS(Platform as a service). Now how do we differentiate between the three categories as a user? Will cover the details below. Infrastructure as a Service(IaaS) Service provider provides you the hardware User gets some control over the hardware, can customise operating system, storage and VMs. Ensuring service is up and running is shared responsibility While cloud provider makes sure that the hardware is functioning correctly, user needs to make sure ...
Read more