HR issues in project management - when not to let go of an employee

If a popular employee or a intelligent person in the group is to let go, the effect seems to be that credibility of management goes down bcos it gives out the sign that management did not want to hear such a person.

Considering the psychological effects of letting go of a person or, in general, of any decision is very crucial to the success of the decision.

People see trends in everyday occurences.

Republishing a PMP

Problem in republishing PMP v 12.0.6 :

If Appraisals are created and then PMP is republished then scorecards cannot be edited bcos an appraisal id is already created.

Hence a good practice is to avoid resetting appraisal dates : have a good gap between the objective setting period and appraisal start date if possible

quirks in implementation

The problem in implementations comes not from business rules but rather from the exceptions that users want to have to the rule. eg...HR specs that a manager shud be able to view only his hierarchy. No problems. But then the manager for many reasons does not make changes themselves so they give access to their secretary or second level leadership to do the menial jobs.....that is where issues start coming in....

pride goeth before a fall

There is nothing wrong with learning new stuff in apps. But what is shortsighted is to not share it with anyone and becoming proud of your niche. Some other fellow who knows more than you will come along and that will be the day you meet your maker.

code to get the supervisor id and employee number for certain employee numbers

select ppf.employee_number,

---code to get supervisor's emp number

(select employee_number sup_number from per_all_people_f ppf

where ppf.person_id = paaf.supervisor_id

and TRUNC(SYSDATE) BETWEEN ppf.effective_start_date AND ppf.effective_end_date

) super_number,

paaf.last_update_date,

paaf.effective_start_date , paaf.effective_end_date

from per_all_assignments_f paaf, per_all_people_f ppf

where TRUNC(SYSDATE) BETWEEN ppf.effective_start_date AND ppf.effective_end_date

AND TRUNC(SYSDATE) BETWEEN paaf.effective_start_date AND paaf.effective_end_date

and paaf.last_update_date = (select max(paaf.last_update_date) from per_all_assignments_f paaf where paaf.person_id = ppf.person_id )--and ppf.employee_number = 2794

and ppf.person_type_id in (1120,1121)

AND ppf.person_id in ( select ppf.person_id from per_all_people_f ppf where ppf.employee_number IN (

2796,2794,2791,2797,2784,2799,2801,2802,2803,2806,2800,2815,2819,2818,2823,2824,2829,2825,2827,2836,2841,2833,2112,2830,

2843,2831,2845,2839,2832,2848,2828,2847,2844,2849,2846,2850,2852,2854,2853,2858,2855,2856,2851,2862,2863,2857

)

)

and paaf.person_id = ppf.person_id

order by ppf.employee_number

Customizations - make or break

Customizations are either the devil or angel depending on stage of the project. It also depends on who is implementing the project - techno or functional person.

A techie prefers to customize while a functional person prefers to have minimum customizations. An inexperienced manager thinks that a techie is superior whereas the functional person maybe wiser. If so any functional solution is taken personally to be against the project. 

Pre-CRP when the pressure is high to put a solution in place and the client is scratching your back off, its so simple to offer to customize and close the issue.  

However once a customization goes live you are stuck with it since data is manipulated around the customization and oracle doesnt support it. It will be a mini reimplementation then.

Change (Mis)Management

Ever seen a 4*100 relay race where the pneultimate runner drops the baton just as the last person is taking off ? ERP rollouts remind of that often these days.

It ceased surprising me why so many ERP's are hated by users.  Of course I would hate it too if I am trained half heartedly for less than an hour, do not get hands on practice and am expected to perform correctly on PROD instance. The least planned part of any software rollout is the user training. No one has time to read thro fat manuals. No one has time to figure out each form. And first impression is the only impression on a user.  And neither HR nor IT departments plan for training at all.

Functional consultants should not anymore be creating user manuals. Instead they should use

gotomeeting, microsoft live meeting and other live video recordings to train their staff. 

A smart client of mine with a 40,000+ user base first implemented OLM and then used it to train every other rollout on oracle !