Test Leadership without a Title

When Musk told Mayank about his promotion and how he can now lead in testing, Mayank couldn’t resist highlighting how he was also of the same opinion. He then highlighted about the concept of “Leadership without a Title” and in Testing. We do see multiple testers complain about various things everyday and forget that everyone has the power to provide at least 15% of solution to any problem (Liberating Structures).

Let us hear about Mayank’s journey through the lens of Rahul and Ajay.

You don’t need a title to be a leader. A leader is someone who leads the way, adds value continuously, accepts things that they don’t know and is ever learning. More importantly, people respect, follow and grow by working together with the leaders. Applying that to testing, how can one lead without a title? 

• Where are the opportunities in testing
• How titles might not solve these problems in the long run
• Leadership in testing
• Framework to be a leader in testing

The entire talk will be filled with real life stories of testing leadership and strategies to be successful. Irrespective of your overall experience, you can also be a leader in testing, without necessarily having a /so-called-title/

Bug Advocacy& Beyond!

Overview & Purpose: The key goal of any bug reporter is to provide high-quality information, well written, to help stakeholders make wise decisions about which bugs to fix. Although most testers find and report bugs in their day-to-day work yet only a few are very good at it. This workshop is designed to help you be a Good Bug Advocate. 

Principles Driving This Workshop: 

1. Bug Advocacy is a persuasive skill that requires thorough investigation, analysis, and clear reporting.

2. Bug Investigation and Reporting Skills can be made systematic and faster using suitable resources, oracles, heuristics, and tools.

3. Bug Advocacy is one of the Core Foundational Skills for any tester who want to be good in this field.

Why someone should care about this Workshop: 

1. Become an influential tester of your project.

2. Learn how to effectively convey risks and meaningful information using Clear & Credible Bug Reports.

3. Learn how to use Tools, Oracles, Cheat sheets, & Other Resources to be good at advocating for bugs & quality.

Overview of Topics to be Covered: 

1. Basic Concepts: Explore “quality” and “bugs” in detail. Anatomy of a Bug Report.

2. Persuasive Bug Reporting: Making People Want to Fix the Bug: Creating reports that clearly communicate bugs in their honest light so that decision-makers can make a quick well informed decision.

3. The Content, Clarity, and Credibility of Good Bug Reports: How to structure reports in more useful and credible way for better decision-making by others.

4. Tools & Tips: Tools & Tips to be moreefficient at bug reporting.

Targeted Audience:

1. Testers: Who deal with finding and reporting bugs in their day-to-day work.

2. Leads & Managers: Who want to train their team to be good at bug advocacy.

3. Developers: Who want to save their day-to-day time by guiding testers to provide them with clear and concise bug reports.