Kickstart your career with best deals on top training courses NY10 Click to Copy

Search

Agility In QA Mindset Is A Key To Success In The Agile Era

Whenever it comes to Agile software development methodology, there are a few Manifesto and Agile Principles that comes to the mind.As we can see, Agile completely believes in“Customer Satisfaction, feedback loop, team collaboration, quick delivery, embracing change request, trust and support, face to face communication, working software, sustainable development, continuous attention, mentioning the simplicity, self-organizing team, reflect and adjust.”The intent behind coming up with Agile looks quite interesting.A quick view on Waterfall modelLet’s talk more from a QA standpoint. As we know, traditionally, in the Waterfall model of Software development workflow would typically look like this.In the traditional software development approach, the complete software development process is splitted into different phases. The output of one phase is acting as a Input for the next phase. This indicates that any phase is incomplete if the previous phase is not completed. That is the reason, the waterfall model is called a sequential model. In sequential approach, the phases flow towards the downward direction through the phases of Requirements, Design, Implementation, Verification, Maintenance as shown in figure above.  In traditional software development process, requirement would be frozen during the initial phase followed by which development of software would begin. Hence, Software testing life cycle will typically look like this-So a Qualitative Analyst (QA) would follow the below workflow-Requirement understanding -> Brainstorming -> Writing Test Scenario -> Writing Test Cases -> Verification -> ReTesting of defect (if any)The above workflow makes sense in the world of Waterfall model. However, with high Agile acceptance in the industry, a shift from Waterfall to Agile Mindset is required. In case of implementing QA Mindset for achieving Agile Manifesto, more of a ‘Shift-Left’ testing is embraced. The entire team is highly involved right from the  Requirement understanding phase to Delivery/Maintenance phase.So the bifurcation between the Software Developer and QA is not there in a team which truly follows Agile. The entire team works together towards a defect tracking instead of finding them and verifying during the verification phase.Steps Towards Developing QA Mindset for Successful Agile ManifestoLet’s talk more from Ground 0 now.During the Grooming phase, Developer and QA pair up with each other and come up with their set of understanding and discuss among themselves around the requirement. Once the brainstorming is done, a list of Open questions are posted to the client for clarification around the same.Post Grooming, the Sprint planning phase kicks in, wherein, based on the answers given by the client, the teams have a better visibility around the requirement. Hence, realistic estimates are given for the User Stories inclusive of Development/Quality Analyst/Business Analyst pairing.Post Planning, the QA starts with writing Test Scenarios/Cases activity. During the course of documentation, QA and Developer team collaborate with each other to ensure they are on the same page. In case of any scenarios that were missed by either of the team, they take care of the same during the Coding/Documentation phase itself. It helps in eliminating the late defect cost.Once the developer is done with Coding and is about to get started with dev testing, a QA member pairs up with the Developer to ensure things are working as expected at a high level.Once the Code is ready and is deployed to QA environment, QA starts with the end-to-end verification of the story. Hence, the possibility of discovering a defect decreases exponentially.QA in Waterfall vs. QA in AgileIn the Waterfall model, QA used to get appreciated based on the number of defects that were found during the verification phase. As a result, somehow teams use to work in a silo which would result in the change of the entire codebase, sometimes the architecture itself. As a result, cost of project would go up significantly as described in the below image.On the contrary, in case of a team which follows Agile truly, a Developer/QA gets appreciation based on Minimal code changes and less number of defects found. There is a high acceptance of Shift-left testing in the industry because of the amount of benefit it has brought in terms of effort saving for rework.So, Agile Testing is not a unique way. It needs to integrate successfully QA Mindset into Agile Manifesto. It is a kind of change in the mindset which does not happens overnight. Along with that, it requires knowledge, skill-set, and proper coaching. Hence, a shift in the Agile QA mindset is required to ensure a high throughput from a team. This article is focused on changing a mindset to Agile by providing the tips for implementing QA Mindset into the Agile Manifesto.Please share your thoughts in the comment section, we can connect on LinkedIn and talk more. If you enjoyed this post, it would be great if you’d help it spread it to your connections on LinkedIn or other channels.
Rated 3.5/5 based on 2 customer reviews

Agility In QA Mindset Is A Key To Success In The Agile Era

683
  • by Suraj Sharma
  • 07th Aug, 2018
  • Last updated on 18th Feb, 2019
  • 4 mins read
Agility In QA Mindset Is A Key To Success In The Agile Era

Whenever it comes to Agile software development methodology, there are a few Manifesto and Agile Principles that comes to the mind.

As we can see, Agile completely believes in

“Customer Satisfaction, feedback loop, team collaboration, quick delivery, embracing change request, trust and support, face to face communication, working software, sustainable development, continuous attention, mentioning the simplicity, self-organizing team, reflect and adjust.”
The intent behind coming up with Agile looks quite interesting.A quick view on Waterfall model

Let’s talk more from a QA standpoint. As we know, traditionally, in the Waterfall model of Software development workflow would typically look like this.
In the traditional software development approach, the complete software development process is splitted into different phases. The output of one phase is acting as a Input for the next phase. This indicates that any phase is incomplete if the previous phase is not completed. That is the reason, the waterfall model is called a sequential model. In sequential approach, the phases flow towards the downward direction through the phases of Requirements, Design, Implementation, Verification, Maintenance as shown in figure above.  

In traditional software development process, requirement would be frozen during the initial phase followed by which development of software would begin. Hence, Software testing life cycle will typically look like this-
So a Qualitative Analyst (QA) would follow the below workflow-
Requirement understanding -> Brainstorming -> Writing Test Scenario -> Writing Test Cases -> Verification -> ReTesting of defect (if any)
The above workflow makes sense in the world of Waterfall model. However, with high Agile acceptance in the industry, a shift from Waterfall to Agile Mindset is required. In case of implementing QA Mindset for achieving Agile Manifesto, more of a ‘Shift-Left’ testing is embraced. The entire team is highly involved right from the  Requirement understanding phase to Delivery/Maintenance phase.

So the bifurcation between the Software Developer and QA is not there in a team which truly follows Agile. The entire team works together towards a defect tracking instead of finding them and verifying during the verification phase.

Steps Towards Developing QA Mindset for Successful Agile Manifesto
Let’s talk more from Ground 0 now.

During the Grooming phase, Developer and QA pair up with each other and come up with their set of understanding and discuss among themselves around the requirement. Once the brainstorming is done, a list of Open questions are posted to the client for clarification around the same.

Post Grooming, the Sprint planning phase kicks in, wherein, based on the answers given by the client, the teams have a better visibility around the requirement. Hence, realistic estimates are given for the User Stories inclusive of Development/Quality Analyst/Business Analyst pairing.

Post Planning, the QA starts with writing Test Scenarios/Cases activity. During the course of documentation, QA and Developer team collaborate with each other to ensure they are on the same page. In case of any scenarios that were missed by either of the team, they take care of the same during the Coding/Documentation phase itself. It helps in eliminating the late defect cost.

Once the developer is done with Coding and is about to get started with dev testing, a QA member pairs up with the Developer to ensure things are working as expected at a high level.

Once the Code is ready and is deployed to QA environment, QA starts with the end-to-end verification of the story. Hence, the possibility of discovering a defect decreases exponentially.
QA in Waterfall vs. QA in Agile

In the Waterfall model, QA used to get appreciated based on the number of defects that were found during the verification phase. As a result, somehow teams use to work in a silo which would result in the change of the entire codebase, sometimes the architecture itself. As a result, cost of project would go up significantly as described in the below image.
On the contrary, in case of a team which follows Agile truly, a Developer/QA gets appreciation based on Minimal code changes and less number of defects found. There is a high acceptance of Shift-left testing in the industry because of the amount of benefit it has brought in terms of effort saving for rework.

So, Agile Testing is not a unique way. It needs to integrate successfully QA Mindset into Agile Manifesto. It is a kind of change in the mindset which does not happens overnight. Along with that, it requires knowledge, skill-set, and proper coaching. Hence, a shift in the Agile QA mindset is required to ensure a high throughput from a team. This article is focused on changing a mindset to Agile by providing the tips for implementing QA Mindset into the Agile Manifesto.

Please share your thoughts in the comment section, we can connect on LinkedIn and talk more. If you enjoyed this post, it would be great if you’d help it spread it to your connections on LinkedIn or other channels.

Suraj

Suraj Sharma

Blog Author

Suraj Sharma is working as a Full Stack QA Engineer with leading IT farm and is striving for bringing change in Industry. Strong believer of "Learning or Decaying" mantra. Technology explorer, Blogger and part-time cyclist by passion. Connect with him on LinkedIn.

Join the Discussion

Your email address will not be published. Required fields are marked *

Suggested Blogs

Built Instability Fosters Innovation New Product Development

As funny as the Calvin and Hobbes comic is, it conveys an important message about how creativity and chaos almost always go together. In 1981, when Honda was developing Honda City – the innovative first-of-its-kind compact car – an executive in charge of its development remarked, “It’s like putting the team members on the second floor, removing the ladder, and telling them to jump or else. I believe creativity is born by pushing people against the wall and pressuring them almost to the extreme.” Haven’t most of us experienced this at some point in our lives? The idea of “built-in instability” was first published in a 1986 Harvard Business Review paper, which kicked off the Agile movement. The paper names built-in instability as a top quality of new product development at leading companies such as Honda, Fuji and Canon. Well, what does built-in instability mean? Why is it important? How does it help teams succeed? Let’s address these questions one by one. What built-in instability means When a company’s top leadership does the following: establishes a broad but extremely challenging goal, does not provide a product definition or a work breakdown structure, AND offers the project team ample room for experimentation and failure … this is called built-in instability. The leaders have basically created an environment of constructive chaos to serve as a catalyst for creative output. Why built-in instability matters Honda’s leaders instructed the Honda City project team to develop “the kind of car that the youth segment would like to drive.” Do we see a goal here? Yes. But is the goal well-defined? No. Do we see what kind of product is expected? Uh, maybe. But do we see the steps to get there? No. With a goal like that, the only way leaders can expect the team to succeed is by letting them fail – to fail early, fail often, and fail forward. When a team has the freedom to fail and knows there isn’t a firing squad waiting down the road, it begins to break traditional boundaries. And companies that thrive beyond decades or centuries with avant-garde products do not get there with traditional thinking. This is why built-in instability matters. How built-in instability fosters success Look at the Honda City team’s goal again: to develop “the kind of car that the youth segment would like to drive.” A broad goal like this naturally demands cross-disciplinary work across a broad spectrum of organizational functions – market research, finance, planning design, production, testing, sales and service. When the team wants to succeed while having the luxury to fail, the built-in instability fosters collaboration among individuals from various functions. In the words of a member of the Honda City team: “You then start thinking in terms of what’s best or second best for the group at large and not only about where you stand. If everyone understands the other person’s position, then each of us is more willing to give in, or at least to try to talk to each other. Initiatives emerge as a result.” In sum, what we today use as Agile/Scrum or other modern methodologies essentially relies on built-in instability. By giving teams the freedom to fail, the process encourages a DNA of experimentation, learning, innovation and continuous growth.
Rated 4.0/5 based on 20 customer reviews
1597
Built Instability Fosters Innovation New Product D...

As funny as the Calvin and Hobbes comic is, it con... Read More

Progressive Elaboration

All projects begin as a concept. A project concept, to create a new product or service, typically includes a broad vision of what the end result of the project will be. The temporary project results in the unique product or service through progressive elaboration. Progressive elaboration is the incremental design and refinement of the initial concept toward the project plan. As a project management course moves closer to completion, the identified needs that launched the project are revisited and monitored. Complete understanding of the needs-and the ability to fulfill those needs-comes from progressive elaboration. Progressive elaboration is an iterative process designed to correctly and completely fulfill the project objectives. This is evident in how the planning and execution processes each contribute to one another. A similar example can be seen in the process to create a Work Breakdown Structure (WBS). The WBS begins with the project vision, which is then elaborated upon to create the project scope, and then expanded again into the WBS, and so on. Consider a concept to build a new building that would handle the manufacturing and shipping of blue jeans. It would begin broadly, with materials delivered, the assembly equipment, and the outward-bound shipping bays. As the project team continues to research the needs and expectations of the project, the project vision would be refined, honed, and polished to a detailed outline of what the project would deliver. As you can see in Figure, through incremental steps, the project plan is developed and the unique project deliverable s are created.
Rated 4.0/5 based on 0 customer reviews
Progressive Elaboration

All projects begin as a concept. A project concep... Read More

11 Reasons Why You Should Do CSM® Training Today

A hardworking team stands on the success of the Agile project. Scrum Master is the only responsible person to stand behind the hardworking team and put Scrum processes on a right track.Definition of the Scrum MasterThe Scrum Master acts as an facilitator to an Agile development team. Scrum is a framework that implements the Agile methodology. The team members become self-organized and allow changes quickly to accord the Agile principles. The Scrum Master manages the process in exchanging the information.According to the State of Agile report 2018, the top five reasons for implementing Agile are:75% Accelerate software delivery64% Enhance ability to manage changing priorities55%Increased productivity49% Improved business/IT alignment46% Enhances software qualityBut, there is nothing to worry about as these shortfalls can be declined by becoming a professional in Scrum and the chances of finishing a project successfully within a time can be improved as well.Nowadays, organizations across various industries started implementing the Agile methodology. Considering these benefits of Agile like delivering quick results along with the reduction in the budget by performing endless iterations, organizations are paving their way towards successful Agile implementation.The reason to get the Scrum Master Certification (CSM) is the rising popularity of the Agile and Scrum certified individuals in the IT industry as well as in non-IT sectors. A widely pursued IT certification is the CSM certification, that is being recommended across all the industries. However, you need to know the basic concepts of Agile and Scrum methodologies to gain a CSM certification.If you are implementing Agile in your project and is being broadly used in your organization then Certified Scrum Master (CSM) deserves to be your first choice as it entails the Scrum fundamentals. This matters a lot in case if you are playing any role from the Scrum team member.Below is the graph from Google trends, representing the rising demand for CSM certification between the year 2017-2018. Following Scrum best principles and practices requires a thorough understanding of its concepts and values that can be obtained through credentials such as the Certified Scrum Master (CSM)—a course that provides professionals with knowledge and skills that help them in the long run.Why you should do the Scrum Master Certification (CSM)?In reality, we know that certifications provide an additional value once we acquire some experience. The CSM certifications act as an add-on to your career. Listed below are the reasons to get your Scrum Master Certification and the advantages of pursuing the CSM training:1) Have a strong knowledge of ScrumIf you are not familiar with Scrum, knowing about the certification will educate you with the required skills to utilize it effectively. If you are in the initial stage of using Agile methodology for your project, the CSM certification will provide you the basic knowledge.2) Update your mindsetTo work with the Agile methodology with Scrum effectively, we need to develop an Agile mindset. The Agile mindset is a key factor for the teams to achieve successful Agile and self-sustaining approach. Industry-oriented certification and training will benefit this kind of mindset. As a member of Scrum team, you will think in an Agile way, that will lead to a decrease in disagreements, more successful projects and a better team collaboration.3) Knowledge of Scrum ArtifactsThis certification includes the concepts like the product backlog, sprint backlog, burndown charts etc. which are the pillars of a Scrum project. These Scrum concepts will be an advantage for the organizations to deliver the project in iterations.4) Be admissible and catch your marketThe certifications will provide you an in-depth practical knowledge to improve your career. It makes you relevant and marketable in your field. CSM certifications will improve your career growth across any organization or industry that engages with Agile values. This certification proves that you have an Agile mindset and knowledge of Agile concepts.5) CSM certification benefits your organizationIt is difficult for any organization to adopt a new methodology as it affects the entire structure of the organization including:ProcessesManagementPeopleClientsIn this regard, it is quintessential for all the customers to achieve some tangible and real benefits in the early stage with self-managing teams and incremental iterations. If you are not a certified member, you might miss the opportunity to establish yourself as a Scrum master in your organization.6) Influence your organization to adopt Agile your organization already has well-trained Agile professionals, the management would be more comfortable to invest in adopting the Scrum methodology. The CSM certification shows the management that you have the knowledge to work with Scrum and implement its approach.7) Strengthening teamworkWe have a few organizations that consider Scrum master certification for different departments over different people. This certification generally has a positive result when it comes to working with your peers. As a certified Scrum Master, you will have the potential to build and strengthen the core understanding of Scrum while working together with your peers. With multiple Scrum experts along with all departments, the organization gets benefited with Scrum experts in all departments with an instance of knowledge that can lead to the successful execution of Agile and Scrum methodologies.8)  Establish your basic Scrum knowledge to peersThe Certified Scrum Master (CSM) certification shows your efforts and knowledge of Scrum that makes you capable of working within the organization. You don’t need to waste your time to show your credibility in your workplace, your certification speaks about that. 9) Join the society of scrum expertsOnce you are a Certified Scrum Master (CSM) you will earn the stature to mingle with a society of authorized Scrum experts committed to ensuring continuous improvements with an Agile approach. Scrum Alliance is an authenticated site that has Scrum features in a global network. This community will actively provide knowledge in a way to discover events and provide instructions.10) Qualified employees get success in projectsIf your Agile project is successfully done then a team member of certified Scrum Master will benefit from a huge reward. And also, the clients would recognize the potential value of a Scrum team that work together to apply Scrum in a productive way.11) One more feather to your career cap?Certification indicates a sign of honor. If you are being a part of the management, allowing employees to get certified proves your acumen and commitment to enhancing their skills.Who should take up the CSM course?Certified Scrum Master training is helpful for everyone who wants to become smart in implementing Scrum in their organizations. Doing a certification course in Scrum strengthens the Scrum Master's experience.This learning event is highly productive and effective for both leaders and members. As the course is completely revolving around the Scrum Master role, individuals who are planning to take up this role will get benefited more from this course.There is one reputed company in Denmark that sends all the employees from receptionists to senior management to the Scrum training, in order to make them knowledgeable about Scrum concepts and enhance operations throughout their company. There is no such fixed set of the target audience for the Scrum Master Certification course. It is designed not only for Scrum Masters but also for the complete project or product delivery teams and anyone interested to work with the Agile teams. The target audience can be a-Software EngineerProduct ManagerProject ManagerTeam LeaderBusiness AnalystDevelopment team memberTesters, etc.Conclusion These are many key benefits for obtaining Certified Scrum Master (CSM) training. Unless we have a basic knowledge of the responsibilities of the Scrum Master, we can’t move to the advanced levels in CSM. In the end, Certification is the best platform that will help you to become an Agile Leader. Click here If you are really curious to know about each and every certification in detail towards your Agile leadership journey.
Rated 4.0/5 based on 1 customer reviews
5600
11 Reasons Why You Should Do CSM® Training Today

A hardworking team stands on the success of the Ag... Read More

other Blogs