Head Hunters/IT recruiters are Morons

SAP Head Hunters/IT recruiters are Morons

Yes, that true, all Head hunter and all IT recruiter sucks. They are one of the morons in Hiring industry. A few weeks later I was looking for some new exciting job. So I just update my profile for SAP Business Analyst on linkedin. I just make it public. With in two days I got an email from of the moron recruiter from INTEQNA in my office email account. That freaks me out. I never post my official email address on any website. That really freaks me out. How the hell he got my office email.

I’m stating as it as what the moron emailed me:

“Hi Atul,

Just wanted to touch base with you to know if you know some one who is available i the market for SAP CML PM opportunity on contract.
I got your information from Linkedin, I specialize in Senior IT Staffing and one of my clients was looking for SAP CML PM Contract.”

I reply back to him that, how the hell he got my office email, and admit yes I’m open for SAP CML/SAP BI job and send my contact number. He calls me with in 2 minutes. I was so freak out at that time, I just start snap him. He starts explaining. I take my company name from Linkedin. Google the company, get contact number from company website. He calls the receptionist, inquired about me and takes my official email from her and then sends me an email.

Man! They are really very smart. But that raise the question what should be the limit of these morons. This is not about checking the reference. If that’s a case I don’t mind where the hell they want to go for reference. But this just to tell me that I’m interested in job or anyone I know interested in job. That’s too much.

Anyhow I talk to him and tell him what the hell I do in my QA job. That the second thing I don’t like about these idiot. They don’t understand what the hell you are talking about your job, but they show off like they know everything about your job.

Morons ask me questions like, what is SAP CML? How many team members in your project? what's your daily job?

Common moron, give me a break. If you don’t know about anything about SAP CML and why the hell you are asking that question, whose answers will spin your heads? Or just damit, admit it you don’t know much about SAP. It takes me 2 hours to explain what the hell I’m doing in SAP CML project as QA. God must be crazy.

Thirds things I don’t like them is They ask for resume and your rate.

But at last I send my resume and rate and my availability, and asked that moron send me job details and clients name.

That was the last day I talk with me. There was no email, no job details, no client info, and no call. That’s it. Idiot, for the 2 days continuously call me about my resume and rate. After I send it there was no reply anything from his side. Not even an email about confirmation about received my resume.

I think I learn my lesson from these morons. Never ever send your resume or rate to head hunters or recruiters until they send you job details and client information. For fun, I email back asking him to send me the details of what he has for open positions. That was fifteen days ago and no response. I hate head-hunters morons!!

SAP BI- Alternative Plans(A,B,C)

SAP BI- Alternative Plans(A,B,C)

Hats off to Project Manager and SAP BI team. This is really great if your team and PM think above ahead. Dan is one of the PM I meet who can see the things from far ahead. The reason why I’m praising my PM is as follows:

We are pushing SAP BI in prod in this month. This will be our major deployment. This is our Plan A. We all (team) are putting lots of efforts on this Plan A. Can you believe we have Plan B and then Plan C also, if any case some thing screwed up with Plan A we jump on other alternative. This idea is our PM’s idea. He takes few resources including me, and puts us into Plan B. We few people are working on Plan B as simultaneously. I’m testing few tables extracted from SAP BW and SAP CML as our plan B part.

Here is Plan B:
The Plan B situation to produce the information from BW master data actually solves a bigger problem, as having the needed Data in a format usable by Enterprise Reporting will allow all critical month end reports to be run using current ER reporting tools. The users will see little difference from what they have now for these critical reports, and this would be an acceptable reporting solution for several month ends. The daily reports will not be able to be produced, but these are less critical. The team is very comfortable that the master data work to support Plan B will be implemented in production along with the already data.

Plan C
Our team is also working on plan C also.

Wow, this is really a very cool approach. When you have alternative options/plans team is actually working on that plan make team and stakeholder more comfortable and confident. Having Plan A, B and C and you are actually working on it is a great backup for whole team and project. But the real thing how well you communicate and coordinate Plan A, B, C with your all team members matter a lot.

So moral of story, always have Plan B and C ready. Actually work 50% on Plan B and 10% on Plan C. Communicate well about Plan B and C with your team and stakeholder. The golden rule: It’s all about saving our ass.

Who suppose to create a SAP deployment list?

Who suppose to create a SAP deployment list?

In our SAP BI project we are having this debate, who supposes to create a deployment check list. Is this Developers Job or is it Netweaver job or is it QA job. We all discuss on this topic.

As my 4+ SAP experience and SAP CML experience, it always developers who create a deployment check list with fully coordinates with QA and Netweaver. In this same organization, in SAP CML project, ours all Deployment Check lists are created by developers. So I believe in that school, that says “Deployments check list is purely developer’s job”. That we did in SAP CML go-live time.

Now this SAP BI, where all BA/PM and developer are arguing that it’s QA job. So guys in SAP BI projects now I’m creating a Deployment Check list, wow.

This is not very easy job. First get Change Review Number from CRC(Change Review Committee). After that document all changes to be happen in production. After that book a meeting with Netweaver, Developer, PM, BA, DBA.. etc. We mostly do meeting on every Wednesday. So today we have that meeting. Then document all steps need to perform during deployment in list. That includes your backup plan. After everyone agree on the list, that don’t happen in one short. You have to draft and then redraft until all agree. If all agree then finally is QA Sign off on deployment check list.

When QA finally gave sign off the list. Every thing needs to get in production move into production. One more thing you have to save this deployment check list in appropriate folder. Then send document link to whole team via email. We are saving all deployment check list in Deployment folder which is under QA folder which is in SAP BI folder. Mostly all clients do deployment on weekends.