Performance Improvement Plan – You PIP for it before they PIP it on you!

“Brother, the soil is fertile, and I see someone cultivating the seed.

It can see it is coming, and it will be here.

But I am not here asking you to help solve my problem—I only want you to listen to me and, if required, suggest something. If there is nothing to offer, it’s okay, and we can also talk later.”

I was thrilled and a bit nervous to know what would come from this man’s mouth, and I didn’t interrupt; the man continued as if he was full and wanted to get empty.

He continued…

I will be on PIP (Performance Improvement Plan) in a month or two, and I have no job offers, interviews, or freelance work. What a terrible state of feeling terrible 😦

For the past week, as I observe myself, I have had a gut feeling and a weird sense that I am ready for it. Of course, when I say it, I mean PIP and failure to meet PIP’s unreasonable demands. But at the same time, I am calm and stable to a reasonable extent, and I know where this feeling and sense of calmness and stability are coming from, and I will talk later about this! 

After spending 15+ years in the industry, why should I be afraid? What’s wrong with my understanding of my knowledge, experience, practice, capabilities, and abilities to find /crack opportunities? Why am I in self-doubt? What are my worries?

I am not afraid of all this, and this sign wave of feeling secure, then secure, then secure, then insecure is now turning into a straight line. 

At the same time, I don’t know what exactly to do. I have ideas like restarting, looking for a job, starting a business, doing this and that. Crap!

Then it was a few moments of awkward silence between us.

And as my friend said all the words in the lines I typed above, I listened to him carefully and calmly. 

I have known this man for 6-7 years now, and we have spent some good time discussing and partially solving some common and slightly tricky problems labeled as midlife crisis for a knowledge work professional(s).

This man is a critical-thinking tester and a passionate performer but still faces such performance issues. After listening to all this, I was not feeling good, but I held my horses.

Going into PIP is a painful and humiliating experience, especially when you know from the bottom of your heart and mind that it is just a trick to get you out of the door but in an ill-planned and organized manner. 

It also becomes more frustrating when you face it at a time when a large portion of the market seems to be getting into a depressed state caused by the recession.

Such conversations are not unusual these days. For example, another friend, a clean coder, and a straightforward person, was forced to leave by misusing PIP!

PIP can be a tool for getting something useful done. It shall be used as a device that a designated person in an organization decides to use when regular feedback to an employee is not yielding desired and mutually agreed upon outcomes, and there is enough reasoning and evidence to believe that it is good to initiate a PIP.

At the same time, I know that a fool with a tool is still a fool!

Nevertheless, I was there to listen, absorb, and come back to think about possible solutions for my friend.

I took his leave and started to home, guessing about a distinct PIP which looked like something below…

Prioritize and Prepare a Quick and Practical plan to avoid/handle PIP with a stable mindset. Mull your options and prioritize based on career goals, risk(s) appetite, and financial/personal responsibilities. 

Initiate – Find a trusted advisor and accountability Partner, share your  plan, kick off execution and 

Progress check is critical; stay consistent, focused, and worry-free because your first goal is to avoid and not face PIP. Suppose you are prepared enough to grab an opportunity before PIP crosses your way. 

Sandeep Garg
Student of Software Testing

The adverse impact(s) of poor testing methods – A tester’s interpretation from a newspaper report.

I am unsure if you know, but Amit Trivedi (An Indian music composer, lyricist, and singer) undoubtedly has a melodious voice and excellent music-composing skills.

His song. Pashmina, from Fitoor (2016), can give any music lover a soothing pleasure.

If you are reading this post, you may want to try the song on your favorite music streaming application, and if you choose to do so, pay attention, especially to the last few seconds where the guitar is played beautifully. I loved that.

Back now? Good

So what about the Pashmina song, and what does it have to do with testing? Nothing.

It was just for your brain’s refreshment. So thank yourself now and me later.

Now, I am a vivid reader of The Hindu (One of India’s daily published newspapers). So every morning, when I pick up the newspaper and before even opening the front page, I pray that I must see at least all pages full of news on testing.

LOL! What a lunatic thinking style. And…

Trust me (in the 21st century) or not, the God of Testing almost always listens to my prayers and gives something to read on Tests, Testing, and Testers. The lucky tester I am. No?

So one day, in December 2022, I noticed an exciting news (article) on complaints about using obsolete testing methods and techniques to detect and confirm contamination of Pashmina Shwals with Shahtoosh fibre.

See the image below as I captured a click from the newspaper hardcopy.

A news clip from The Hindu (Delhi NCR), back in December 2022

While reading the news, I started imagining the following structure

1. Mission of testing and stakeholder(s)
2. Testing process and test cycles
3. Testing results and bug and product status reporting
4. Decisions based on results

And, here are my interpretations from the statements made in the newspaper report

Mission of testing:

1. Test to find evidence of no contamination
   • Establish the difference between two materials that have similar physical properties and tangibility.
2. Test quickly and reliably.
3. Report testing results as reasonably quickly as possible so that..
   • Further testing processes and the final export approval process is quick.
   • There are no additional issues on the importing side
   • Finally, traders generate sales and revenue to remain in business

After reading the report, I found it safe to talk only about the reported observations on the Testing process, methods adopted, and consequences as mentioned in the paper because commenting on the decision process, decision-making, and decisions is not my area of expertise.

From the highlighted areas, you should be able to identify some commonalities between testing software to detect bugs and testing highly loved (at least in my part of the country) pashmina shawls to detect contamination.

I am listing down those commonalities as far as I can understand…

1. Obsolete testing methods
2. Predominantly observed limitations of old testing techniques
   • e.g. Light Microscopy and / or forensic methods, in the context of above report
   • The human expertise limitations: This may be controversial for some and require a skeptical POV, but now let’s assume what is reported as ‘As is.’
     • Increased number of false positives
3. Lack of advanced test technique(s)
   • DNA testing
   • Scanning electron microscopic tests
4. Delayed testing cycles & inconclusive results (including false positives) resulting into.
   • Loss of reputation, sales and revenue
   • Financial and criminal prosecution

Note: If you read this news closely and in iterations, let me tell you this, and I am not exaggerating (at least in my mind, LOL).

You will start appreciating that this article (news) offers great insights to a curious and attentive software tester.

1. Start reflecting on his/her testing skills
2. Understand the value of a expert tester and his tools/methods
3. Realize power of learning about testing problems in domains other than software
4. Value of context driven and good testing
5. Adverse impacts of inadequate testing methods

Now as I told you that I pray and God of Testing responds, I was praying again and this popped up on April2, 2023

See the image below as I captured a click from the newspaper hardcopy.

A news clip from The Hindu (Delhi NCR), 02 April 2023

I don’t think I need to list down the commonalities once again. But,

I repeat that you will start appreciating that this article (news) offers great insights to a curious and attentive software tester.

1. Start reflecting on his/her testing skills
2. Understand the value of a expert tester and his tools/methods
3. Realize power of learning about testing problems in domains other than software
4. Value of context-driven and good testing
5. Adverse impacts of inadequate testing methods

I enjoyed typing this post and hope you have enjoyed reading it; if not, it is okay.

Stay tuned for the next post; if I would be consistent here. LOL!

Oscillations…

They asked me to Shift Left,
I shifted and trusted them to be correct
The journey was joyful, 
But the feeling of fixation was awful

They felt they got me corrected
But I felt disconnected.
Then they asked me to Shift Right
I shifted assuming that the future would be bright.

I incepted in an utter absurdity 
For a moment
If Software Testing can be thought as a Number Line
Shifting extreme right may give rise to false positives
And to extreme right may give rise to false negatives 
I did a Values At, Within, Towards Boundaries Analysis
I sensed an 'Analysis' paralysis

I argued
I may be right or wrong some day
But, that prediction doesn’t stop me to say
That, Blinded by marketing gimmick
Probably, we forgot the Dynamics, Balancing and Equilibrium magic

In shifting to the boundaries, hours are burning
Gradually we may lose momentum and agility in learning
Nevertheless
I still have positive thoughts
Shift left or shift right,
Just don’t forget to step back
backtrack and connect the dots

Let’s not forget we are sitting on the heap of assumptions and ambiguities
Beyond shifting left or right
There is a context and there are non virtual realities

Experiment, Innovate, elevate
Just don’t fixate
Give yourself a chance
Revert and continue work with common sense

The arguments went up
They asked me to shut up
I kept myself calm
And here came a noise coming from the alarm!

टैस्टिंग करना सीखो, ओ वेरीफाई करने वालो !

इस रचना से मेरा कोई उद्देश्य नहीं की मैं किसी के टैस्टिंग स्टाइल, एजुकेशन, कैरियर, सर्टिफिकेशन या किसी वैल्यू सिस्टम से जुड़े होने पर कोई व्यंग्य करूँ या ज्ञान बांटने का ढोंग करूँ| 

वो प्रयास नहीं है. 

प्रयास बस इतना सा है की अगर कोई इसे पढ़े और उसे लगे की कुछ तो सच है, तो कुछ पलों के लिए खुद के लिए सोचे, समझे और जो सही लगे वो निर्णय ले. 

इन शब्दों को लिखने के लिये मैंने सफदर हाशमी साहब के एक बहुत मशहूर गीत (https://bit.ly/SafdarKiEkNazm) को एक जरिया बनाने की हिमाक़त की है. 

मेरी जो थोड़ी बहुत समझ है उसके लिहाज़ से मैं कह सकता हूँ कि, उनका तो बहुत ही बड़ा उद्देश्य था, कोशिश थी और एक बड़े तबके को एक बहुत मानवीय और वजनदार मैसेज देने का बेहतरीन प्रयास था. 

मेरा काफी छोटा उद्देश्य है, लेकिन है. उनका ये ओरिजिनल गीत मैं बचपन में दूरदर्शन पर सुना करता था. आवाज शायद उनकी ही थी या नहीं, ये तो नहीं पता लेकिन उन्होंने जो लिखा, पढ़ा और कहा वो उम्दा है.

उनको और उनकी रचना को पूरा सम्मान देते हुए, 
ये जानते हुए की ओरिजिनल रचना की आत्मा और भाव से जानबूझ कर कोई छेड़ छाड़ नहीं करूंगा 
और ये लिखते हुए की कुछ भी गलती होगी वो मेरी होगी।
शुरू करता हूँ 

टैस्टिंग करना सीखो,
ओ वेरीफाई करने वालो !
टैस्टिंग करना सीखो, क्यू-ए / क्यू-सी करने वालो !

प्रॉब्लम और कॉन्टेक्स्ट को जानो,
यूज़र्स को पढ़ना सीखो;
एक्सप्लोरेशन को साथी बनाकर
प्रॉडक्ट लर्निंग करना सीखो!

टैस्टिंग करना सीखो, ए-आई से डरने वालो,
टैस्टिंग करना सीखो, जी-यू-आई ऑटोमेशन में रमने वालों! 

टैस्ट केस चलाने वालों, पास और फेल करने वालों 
टेम्पलेट्स भरने वालों, साइन -ऑफ को झेलने वालों 

टैस्ट डिजाईन का फैसला अगर तुम्हे करना है
फीडबैक और स्ट्रेटेजी को अगर सॉलिड करना है,
रिस्क और थिंकिंग को हथियार बनाकर लड़ना सीखो!

टैस्टिंग करना सीखो, बस चैकिंग करने वालों 
टैस्टिंग करना सीखो, इट वर्क्स से खुश होने वालों 

पूछो डॉक्युमेंट्स की खातिर 
टैस्टर्स भटकते क्यों हैं?
पूछो खुद से 
अपनी जॉब्स ये टूल्स लपकते क्यों हैं ?

स्मार्ट, प्राउड और कॉंफिडेंट टैस्टर बनना हो विज़न हमारा 
जुडो कम्युनिटीज से, होगा लक्ष्य पूरा हमारा 
सीखो टैस्टिंग जो ‘मैनुअल’ से पाना है छुटकारा 
सीखो टैस्टिंग की हर कोई दोस्त बनेगा तुम्हारा 

टैस्टिंग करना सीखो 
ओ वेरीफाई करने वालो 
टैस्टिंग करना सीखो,
ओ वेरीफाई करने वालो !
टैस्टिंग करना सीखो, क्यू-ए / क्यू-सी करने वालो !


Hinglish Version

Testing karna Seekho, 
O Verify karne walo, 
Testing karna Seekho, QA / QC karne walo. 

Problem aur Context ko jano, 
Users ko padhna seekho, 
Exploration ko saathi banakar 
Product learning karna seekho. 

Testing karna Seekho, AI se darne walo, 
Testing karna Seekho, GUI Automation me ramne walo. 

Test case chalane walo, Pass or Fail karne walo, 
Templates bharne walo, Sign off ko jhelne walo, 

Test Design ka faisla agar tumhe karna hai, 
Feedback aur Strategy ko solid agar karna hai,
Risk aur Thinking ko hathiyar banakar ladna seekho

Testing karna Seekho, bas Checking karne walo
Testing karna Seekho, ‘It works’ se khush hone walo

Poocho, Documents ki khaatir testers bhatakte kyo hai 
Poocho khud se, 
Apni jobs ye Tools lapakte kyo hai? 

Smart, Proud, aur Confident Tester banna ho vision hamara 
Judo Communities se, hoga Lakshya poora hamara 
Seekho Testing jo 'Manual ' se pana hai chutkara 
Seekho Testing ki har koi dost banega tumhara.

Testing karna Seekho, 
O Verify karne walo, 
Testing karna Seekho, QA / QC karne walo. 


==================================
पढ़नें के लिये धन्यवाद / Thank you for Reading
समझने के लिये शुक्रिया / Thank you for Understanding
एक्शन लेने के लिए बधाई / Thanks for taking Action
कुछ पूछना हो, बताना हो तो फील फ्री फॉर कमैंट्स / Feel free to comments

थैंक यू  / Thanks
संदीप गर्ग / Sandeep Garg
स्टूडेंट ऑफ़ सॉफ्टवेयर टैस्टिंग / Student of Software Testing
==================================

होली के रंग, बच्चों के संग

H-Hate O-Out, L-Love, I-In

ये होली के रंग हैं 
इस होली पर, एक नया सा रंग है
और सोने पे सुहागा ये 
कि इस समय हम बच्चों के संग हैं!

कल शाम से
ये बच्चे 
मुझ बोरिंग से इंसान को 
कर रहें है उत्साहित ,
और जबरदस्त तरीके से 
प्रोत्साहित!

कि कल पक्का चलना है तुम्हे 
हमारे संग 
निकलो इस, लाइफ इन दी रूम, वर्क फ्रॉम होम 
से बाहर
और खेलो हमारे साथ होली 
कभी तो हो लो मस्त मलंग !

बच्चों के कुछ प्यारे से दोस्त भी, आ गये है 
शिकायत का पुलिंदा लेकर 
कि आते नहीं तुम नीचे साथ खेलने 
मोटे पेट वाले अंकल 
बाँध रखी है पैरों में 
क्या आंटी ने 
कोई संकल?

उत्सुक, आनन्दित, प्रफुल्लित 
वाह रे ये बच्चे!
क्या है जो ना सीख पाऊं इनसे?

संभाल ली है 
इन्होने अपनी छोटी सी पिटारी 
जिसमे है 
पचास ग्राम गुलाल 
इतना ही एक दो रंग 
और 
बन्दूक जैसी छोटी सी पिचकारी!

छज्जे पर तैयार रहेगा 
कुछ लीटर पानी 
एक छोटी बाल्टी 
भतीजा रो रहा है 
बिना बात के 
बगल  में बैठा, मार के पालथी 

होली के आने पर 
इस बार 
कुछ राहत है 
कि 
अपने अपने घरों  से बाहर निकल पाएंगे 
रंग खेलेंगे 
गले अपने नये पुराने पड़ोसी को
खुले मन से लगा पाएंगे

जो मन कुछ उदास थे 
कुछ जीवन जो नाराज थे 
हो भी सकते हैं ठीक 
शायद कुछ उमंगों में 
इस बार की होली की रंगों में 

बच्चों  से सीखा 
वर्तमान में रहना 
उत्सुक रहना 
ध्यान से देखना, जानना 
ज्यादा नहीं मानना

तो निश्चय है अटल 
कल बनते हैं 
थोड़े से बच्चे 
अक्ल के कच्चे 
रंगों के सच्चे!

- संदीप गर्ग
-- स्टूडेंट ऑफ़ सॉफ्टवेयर टैस्टिंग 
-- स्टूडेंट ऑफ़ लाइफ 

Would you work on a weekend?

Image Credit: https://cutetropolis.com/2020/05/23/cat-sits-on-laptop-computer/

In my work experience so far, in the IT/Software industry, the demands, urges, requests, rare necessities, instructions to work on a weekend are not new.

In fact, as an individual contributor, team lead and team manager, I have deliberately chosen, a couple of times, to work on weekends. I also planned a few working weekends for my teams as well. Sometimes it went well and sometimes it didn’t at all as far as the goal is concerned. Sometimes I regretted my poor planning decision that I made and sometimes everyone appreciated me and my team’s proactiveness.

I know that it is a delicate, debatable and controversial topic and I don’t want to write (as of now) a white paper on this subjective topic. So why this post? Let me tell you why.

Recently one of my friends threw the following question to the people on Twitter. 

How will you react when your manager asked you to #work on #weekends?

I usually don’t respond to questions / comments  / statements / polls on twitter where I do not have something reasonable to say. Above question, somehow, triggered an urge in me to respond to this question in a manner that I think that a handful of professionals may want to answer.

I first explicitly stated my interpretation, received an affirmation from her

One of my interpretations of this question is this…

‘How will I react if my manager asks (in the near future, in some situation, to achieve something) me to work on a / some weekend(s)?’. 

Then I went ahead and picked the words ‘React’ and ‘Ask’ (in the given order).

I stated my assumption that I was in a healthy mental, physical and emotional condition at that very moment when I first heard the ‘Ask’.

Here my final answer was…

My reaction to my manager’s action would be a state change, in my head, turning into the following questions to myself based on my relationship with my manager and how have we worked together so far.

1. At this moment, what does this ‘Ask’ look like? A request, demand, instruction or mere a question seeking a binary answer?
2. What is the context?
3. What situations might have caused this ask from my manager? Was I somehow unaware or ignorant of those situations?
4. Why didn’t I think of such a question popping up in my head before even the manager sees a need to ask?
5. Did I miss something while planning such that my manager is trying to point my attention towards by asking? 
6. What is special with the weekend? Is it contingency planning? Is it firefighting? Is it a proactive measurement? 
7. Is it necessary based on my experience and expert judgement?
8. Is it only me to whom the manager asked and if so why could it be?
9. Is this becoming a pattern and I am not happy with this at all?
10. Is this a pattern and I am happy to do this because of the monetary compensation, learning, opportunities, exposure?

Of-course, there were other factors and assumptions as well behind answering the question. All of those are not explicitly mentioned here. For example – assumptions around my already planned personal commitments on the weekend, assumptions around organizational culture and so on. But keeping in mind twitter’s space limits and my focus towards responding in a quicker and healthier way, I responded with above 10 points.

Finally, I wrote that I was thinking of law of conservation of energy to construct my response (or reaction).

 I also mentioned to her that I was thinking of ‘Law of conservation of energy’ while I was drafting the answer.

My friend got other answers as well and I don’t see a reason to comment on those. Everyone has an opinion and point of view, like I had and I responded the way I thought I should.

Did someone ask you a similar / same question ever before? How did / would you react?