Last week i was getting mixed response on the earlier blog. But i was quite happy bcoz the main purpose started writing the blog is to tell my views. I use this blogger as a mirror and Prasanna is talking to himself (yeahhhh hoooo... the reason behind the name of my blog.... :-))
Comin back to the point where i stopped....
Process is a good word that can be used for any of the work that you do. If anything that needs to be repeated, then people will say "lets have a 'PROCESS' here, to make sure that we are not making any mistakes". It is well implemented manufacturing industries with the help of various tool/methods (six sigma/kaizen method). If you had read Jack welch's biography, then you can really feel how important a process for an organization (for those who dont know Jack, hez the person who was giving the new face for GE, was CEO for GE for about 2 decades).
Now coming to process in our industries. All the companies are having a tool to make sure that all the project management related activities are tracked. These are developed by set of really good people who are expert in process of software world.But when it comes to day to day implementation, our delivery specific managers simply delegates it to the team. So, it will be on the hands of team member who is really doing the development. Look at this, a process which is created by set of experts, is being directly used by developers. Now tell me what will happen here. Whether he will work on the development or work on the process. Why the managers/leads are not ready to understand these process and try to explain to the team memebers how exactly they can be used.
On the other hand, the team who are in charge for ensuring the quality will get in to the delivery to review the activities/deliveries, to check whether the projects are as per milestones defined. These people (another team member of other project :-)) dont know much about the requirements, developments, so they will have defined static questions/checkpoints. Like if a document is having the proper formatting, whether a document is as per the standards.If it is there then the project will be considered as a project that adheres the process.
I am not sure how this helps in meeting the business requirement. To my understanding all the technical members work for 2 set of people. One is the external business and other one is internal business (process team).
All the technical team members are recruited for technical work, the leads are recruited for technical and process work, and the managers are recruited for process and delivery work. Actually some of the managers are recruited bcoz they have PMP certification. But end of the day, leads and managers delegates everything to team members, who are mostly doesnt have the resistance and doesnt say NO. Bcoz all these team members are mostly toppers in their college and school days. These toppers have a simple attitude, that whatever they do is correct, bcoz they studied and wrote exams, and as per the exam results they are the toppers.Companies recruiting them bcoz they are toppers. So, when a task(s) assigned to them they will think that they can complete the task(s) without issues. But in reality they cannot perform it considering the real work involved in it ( i mean to say perform the development and perform the process work). Slowly they will start to compare their friends, they may be doing good in some companies which leads them to think that they are overloaded in this company. Now another victim is getting ready for the hopping of jobs :-)
I understand what is your question here. What i am trying to say here.....
My point is simple, let the people do their work!!! Dont delegate anything and everything. Everyone is being paid for the work that they are expected to perform.Have a simple processes in place (which can be inducted in to your big orgranizational level process defined by experts). Define that process (eg: perform review for each delivery, perform testing on each delivery with a senior person of the team), train the team for these processes, implement the processes, review the processes periodically, enhance/change the process based on the situation.
But Most of the deliveries are not happening like this, so each project has one or two person(s) who are burning their midnight oil for the successful delivery. Bcoz the system will be ready to share the success of anything, but if it is a failure then there can be only one person to receive it at the end :-) :-)
Meanwhile on the delivery that i was working, the UAT was successful with just 2 defects.
Hey look at this, even i am not good in testing, i still missed something during my testing:-) :-)
So, what do you say??? Now read my blog's title!!!!
No comments:
Post a Comment