3 ways Agile testers can use Walkthroughs

A walkthrough is a great review technique that can be used for sharing knowledge, gathering feedback and building a consensus. Typically, walkthroughs take place when the author of a work item explains it in a brief review meeting — effectively walking the team through the work — and gathers people’s feedback and ideas about it. These meetings may be as formal or as informal as needed and may also be used as a knowledge-sharing session with many relevant stakeholders at once.

In my article published at https://blog.gurock.com/tester-agile-walkthrough/ , I have discussed three ways agile testers can make use of this type of review for their sprint- and release-level test plans and test cases to get the entire team involved in the quest for quality.

I have also discussed how I have used walkthroughs in my agile team as a mechanism to review our sprint test scenarios with the entire Scrum team. The main areas of application are-

  • Defining Scope
  • Generating Test Ideas
  • Building a Consensus

Click here to read the complete article–>

Walkthroughs are a quick and easy review technique to adopt, and they can be especially useful for testers on an agile team to get reviews on their test plans, test cases, and scripts. Give this technique a try, even if in an informal sense, and see how beneficial it can be!

I am speaking at ‘Targeting Quality 2019’ , Canada

I am super excited to be speaking at this grand event TQ2019 being organised by KWSQA on 23-24 Sep in Canada!

On top of that I get to present not one but 2 talks!! My topics are

“The What, When & How of Test Automation” 45 mins

In this I will talk about preparing robust automation strategies. Agile means pace and agile means change. With frequent time boxed releases and flexible requirements, test automation faces numerous challenges. Haven’t we all asked what to automate and how to go about the daily tasks with the automation cloud looming over our heads. Here we’ll discuss answers to some of these questions and try to outline a number of approaches that agile teams can take in their selection of what to automate, how to go about their automation and whom to involve, and when to schedule these tasks so that the releases are debt free and of best quality.

“Gamify your Agile workplace”    15 mins

In this I’ll present live some innovation games and have audience volunteers engage and play games based on known scenarios. Let’s Play and learn some useful Innovation Games that can help you gamify your agile team and workplace, making the team meetings shorter and communication more fun!

Both these topics are close to my heart and I am looking forward to sharing my thoughts with a wider audience.

I am also excited to meet all the awesome speakers at the event , as well as get to know the fantastic team of organizers behind this event!

Check out the detailed agenda here – https://kwsqa.org/tq2019/schedule/

Follow me at @testwithnishi, @KWSQA and #TQ2019 on twitter for more updates on the event!

Also check out & support other initiatives by KWSQA at https://kwsqa.org/kwalitytalks/

Wish me luck! 🙂

Scrum, Kanban & Scrumban – What’s the difference?

Agile is a big umbrella that covers a number of different approaches, and there is always scope for more. There are so many flavors because agile is a mindset that allows flexibility in its processes. Two of the more popular approaches are Scrum and Kanban.

Scrum and Kanban apply agile principles in their own way to empower effective delivery cycles. “Scrumban” is a term coined for a hybrid approach making use of both Scrum and Kanban principles.

In my article published at Testrail , I have explore the differences among the three methodologies – Scrum , Kanban and Scrumban. Check it out and see which of these methodologies may be right for you. https://blog.gurock.com/scrum-kanban-scrumban/

Here is a brief about the 3 methodologies –

SCRUM

Scrum is the most popular agile framework. It is iterative and incremental in nature and focuses on tight delivery timelines. The release time frame is split into small iterations called sprints. Work items are planned for each sprint in the form of user stories and tasks, which are prioritized based on value. Teams are small, cross-functional and self-organizing, with a product owner, a ScrumMaster and the development team.

Scrum provides channels for communication through ceremonies such as the sprint planning meeting, the daily standup meeting, the sprint demo, and the sprint retrospective, all of which contribute to the overall pace and a flexible approach to software development.

Scrum Task board

KANBAN

Kanban is focused on continuous delivery based on lean principles. It’s based on the flow of work and just-in-time delivery and promotes process improvement. Kanban aims to eliminate waste, increase productivity and efficiency, and have flexibility in production. The main goals are to limit work in progress (WIP), avoid multitasking and recognize bottlenecks.

Read More »

4 ways Task boards can help Agile teams

A task board is a physical or virtual chart containing all current team tasks at hand and their progress over time. For an agile team, all sprint tasks can be represented on the task board, and their flow over various stages can be tracked in the daily standup meeting. Task boards are a great way to visually representing pieces of work and their status.

Besides helping to organize and track work and being the focal point of the iteration and relevant meetings, task boards can have numerous more benefits for an agile team. In my article published @Gurock, I have discussed four additional ways in which Task boards can help an agile team-> https://blog.gurock.com/agile-task-boards/

Different styles of Task boards

Main points discussed–>

  • Customize the process
  • Visualize their Scrum
  • Improve Commitment and visibility
  • Facilitate Team interactions

Click here to read more ->

My talk @Playscrum Meetup by Leanpitch- 20 July’19

I was invited to present a talk at this month’s @Playscrum Meetup at Bangalore, hosted by @Leanpitch technologies on 20th July

It was a small event with a great set of delegates who gathered to hear me talk about Gamification in Agile teams. Agile teams rely heavily on communication and collaboration among all team members. In this session, I talked about about ‘Innovation Games’ which help make all agile meetings and ceremonies shorter, crisper, more visual and open involving all team members.

It was an interactive session wherein we played many Innovation Games with the audience volunteers, which was a big hit with everyone. There was good participation, many great ideas and discussions in the group. Overall a good experience at my first Playscrum meetup in Bangalore. Would love to collaborate again soon!

Here is a glimpse of the event-

https://www.meetup.com/PlayScrum-Bangalore/events/262475507/

‘Co-opetetion’ Among Agile Team Members

Agile focuses on motivated individuals acting together toward a common goal. Consequently, agile needs people to collaborate and requires complete transparency, communication, and cooperation, within and across teams. But at the same time, individuals instinctively try to outperform others in order to stand out in their teams.

This transition from individual responsibility to collective ownership is often the hardest part of the cultural shift that teams face when adopting agile. I have looked at ways to encourage healthy competition, more cooperation, and a sense of community among agile teammates in my latest article for Gurock – TestRail blog, the main points being-

  • Showing People the part they played
  • Have Co-workers appreciate each other
  • Measuring personal growth
  • Motivating with extra initiatives
  • Encouraging Collaboration and healthy competetion

Check out the complete article at – https://blog.gurock.com/agile-co-opetiton/ to find ways to encourage healthy competition and better team dynamics in your agile teams!

Using Mind Maps for Agile Test Planning

Mind maps are a creative way of gathering ideas around a central theme and categorizing them in concrete branches. Mind maps can be useful for both personal and professional life as an organization and visualization technique. They’re descriptive, easy and even fun.

In my latest post for Gurock blog, I showcase the usage of mind maps as a technique for test planning and test design. This tool’s capabilities make your documentation leaner and ideas more visual, which benefits the whole agile team.
https://blog.gurock.com/agile-mind-map/

Be it test planning in an agile team which needs entire team’s insights and collaboration, or categorization of product features, test areas and backlog, Mindmaps can be used for all aspects and phases of the project.

Testers can generate their test ideas and have them categorized in a mind map around the central theme of the feature. The visual nature of a mind map helps them find more scenarios, see which parts are more heavily tested, and focus on main areas or branches. Once done, they can have other stakeholders take a look at it and get their opinions. This fosters brainstorming together and gathers the maximum number of ideas from the entire team.

Find useful tips to create your own mindmaps, as well as some samples for your reference in agile test designing as well as test planning. Read the complete article here ->
https://blog.gurock.com/agile-mind-map/

To learn more about the basics of Mind Mapping and its benefits, read this comprehensive guide that will uncover your mind’s potential and let it soar on the wings of creativity. Mind maps offer an incredibly flexible, accessible, and applicable way to memorize new information. You should try this effective tool for organizing ideas if improving your productivity and the quality of your academic achievements is something you’re interested in.

Share your thoughts!

Making the case for Usability Testing in Agile

My first experience with usability testing was on an agile team where the product we were building was being designed with the help of an in-house usability expert. He helped design the user interface (UI) of the application and conduct usability study on the beta version of the software to determine the ease of use of the application.

Though the experience was limited in terms of the interaction we had with the user representatives and the sessions conducted, the feedback we received opened up lots of new avenues for the tester in me around the learnability, understandability and attractiveness of the application I was testing.

Usability has matured a lot over the years. It’s now an essential software characteristic in today’s web and mobile applications. In my article published at the TestRail blog, I discuss ways of performing Usability tests and developing a mindset for Usability in an agile context.

https://blog.gurock.com/usability-testing-agile-projects/

We also discuss about Usability Study , how to set it up and achieve maximum benefits from it.

To read the complete article — (opens in a new tab)”>Click here –>


Prevention is the Best Cure- for Defects in Agile

The agile methodology focuses on building in quality from the very beginning of the software lifecycle. That is why we aim to find and fix defects early on: A defect found and fixed in an earlier lifecycle phase is a multitude cheaper than the same defect at a later stage.

But how can we more easily make it possible to prevent defects from percolating deeper in the software development lifecycle by fixing them in their nascent stages?

This is the main theme of my latest article for @Gurock TestRail blog – where I explore and explain ways to foresee, analyze and thwart defects in an agile context.

The main points discussed are-

Communication

Conduct Reviews

Demonstrate Often

Static Analysis and CI

Click Here to read the complete article –>

Please support by liking / commenting and sharing the article!

Cheers

Nishi

Look Back to Plan Forward – Learnings from 2018

Every year we see the software industry evolving at a rapid pace. This implies changes in the way testing is conducted within the software lifecycle, test processes, techniques and tools, and the tester’s skill set, too.

I’ve been into agile for more than a decade, and I’m still learning, changing and growing each year along with our industry. Here are five of my key lessons and observations from 2018. I hope they help you in the coming year!

https://blog.gurock.com/lessons-for-agile-testers/

In my article published on Gurock blog, I talk about the 5 key learnings for Agile testers from the past year and how they will be key in planning your road ahead in 2019. The key learning areas discussed are —

Testing Earlier in DevOps

Getting Outside the Box

Increasing Focus on Usability Testing

Enhancing Mobile and Performance Testing

Integrating Tools and Analyzing Metrics

Click Here to read the complete article — >