8 Common Errors in Change Management


“Change Management is hard.”
“It is error prone.”
“Difficult to predict outcome”.

If you say “Yes” to all above statement, then I recommend you to read “Leading Change” by John. P. Kotter at least once. It provides valuable input to do successful change management in your organization.

Here is his list of 8 common errors in change management.

8 Errors in Change Management

8 Errors in Change Management

“Super” Productivity = Not To-Do List


Productivity = To-Do List
“Super” Productivity = Not To-Do List
Yes. It is important to have a clear, long “Not To-Do List” saves hell lot of time which you can use for productive tasks. Here is simple list inspired by Four Hour Work Week Blog by Tim Ferris.

Increase Your Productivity by Not To-Do List

Increase Your Productivity by Not To-Do List

Lot more great ideas by blog readers are available in comments section of this blog post – http://fourhourworkweek.com/2007/08/16/the-not-to-do-list-9-habits-to-stop-now/

Roles and responsibilities of a Project Manager


Key Leadership Skill – Competency


No human being will work hard at anything unless they believe that they are working for competence. – William Glasser

After my induction in my first job, first work assignment I got was to help my corporate trainer in a training program. Trainer sent me a participants question paper & asked me to print 30 copies of it.

The problem was – I didn’t have enough skill to take print out – I don’t know how to connect my machine to printer, how to print a document and even I don’t know where the printer is situated. I was so shy tell him I don’t know this job or ask him right questions to do the activity. I stayed late in the evening & do something about it, but my mind filled with fear & I was not ready to face the trainer next day without completing the job.

I took time-off next day & returned the job the day after. I was hiding here and there to escape from the trainer. During lunch, he met me and asked me “why did you do like this?” I stood in front of him quietly. He told me “If you don’t know the job, tell you don’t know it & ask for help. People will help if it is possible or if it is so urgent, they will get help from others in right time. You wasted my time” & went off.

Though printing is a simple activity, it requires certain basic & sufficient knowledge and skill to produce the printouts. I can read books to get basic knowledge but that is not enough. I need to get the skill to perform the activity by doing it or by trying to do it. Like printing, every activity requires the sufficiency in skills to produce the right outcome.

Sufficient Knowledge & Skill to perform an activity is called Competency. One of the important factor that divide an experienced from an inexperienced is Competency. In a job, Expected Level of Competency varies based on role & tenure in the job (experience). In Project Management, HR Management closely deals with competency. Competency is one of the required Leadership Skills for leaders which I listed in Leadership Champions – Leadership Rubik Cube.

Let me close this post with apt quote from Roosevelt.

“Whenever you are asked if you can do a job, tell ’em, ‘Certainly I can!’ Then get busy and find out how to do it.”
― Theodore Roosevelt

Project Management Process Driller


Play with PMBOK ITTO – Interactive Mind Map in PDF aligned with PMBOK Guide® – Fifth Edition(English)

Project Management-5thEd – Knowledge Area Wise 

5th KA-wise

Project Management-5thEd – Process Group Wise

5th PG-wise

Project Management Process Driller Based on PMBOK Guide® – Fifth Edition(English)

–> Project Management Process Driller Excel Workbook Link <–

In this Excel workbook, there are 4 sheets.

In first sheet(Name:KAs Vs Process Groups), I presented detailed information of Processes in different Knowledge Areas grouped under five process groups in ready-to-print table format.

Image

In 2nd Sheet (Name:Drill-down), I presented an interactive drill down which displays ITTO information based on your selection of Process groups & processes within the process group. Here VB Macros are used to make the experience more visually pleasant and greatly understandable.

Image

We see PMBOK arranged its content based on Knowledge area. So 3rd sheet(Name:Drill-down2) is just a different dimension for the information presented in 2nd sheet. The key driving factor here is Knowledge area. This view helps you to review ITTO PMBOK chapter-wise.

Image

In fourth sheet(ITTO Drill-down), 191 ITTO in all processes are provided with drill down facility. With this pivot, one can readily get –

Which are all processes using particular ITTO?
Which process group that process belongs to?
Is the given ITTO item a Input or Tool & Technique or Ouput?
In how many processes an ITTO item used?
Is an ITTO item, output to which process & input to how many other processes?

Image

This excel workbook provided for personal use like PMP Exam Preparation or PM activities & DON’T share this in common forum or web sites. As this one is part of my training guide and project management book

By the way, I one last thing before I close this post: This document is password protected. Use “leadershipchamps” as open password for the document. I prefer keeping it Read-Only to keep the integrity of the excel, so select “Read-Only” button in subsequent dialog that asks for Write Access password. Also, select “Enable content” to enable the Macros. Though I ensured it virus-free, but still I strongly advise you to virus scan before you open the document.

In case you found any errors (or) you have any comments, suggestions or questions, please contact me through my blog

Issue – Demystified


 

Every time when I encounter an issue – I think a lot about the issue, lose time, undergo lot of emotional change till I finish it. Once I move it out of my plate, I feel happy and wish not to get a issue like this in my life. But issues in life is not having any end to it and the cycle continues. Today I decided to write my thoughts about issue. Issue is something you feel disruptive when you expected to lead the life in defined routine.

Issue

An issue has a description, root cause, pattern, mindset, its time bound and have solution. Here is a single line explanation about each of those components.

  • For any issue clear description is the key. Well defined issue will get well defined solution
  • Issue is just an effect & every issue has a root cause for it
  • Patterns can be derived if the same issue occurs frequently. Pattern applies to solutions too
  • Size, complexity & situation depends on mindset and not in the issue itself
  • An issue is an issue only for a particular period of time which may diminish or vanish or resurface after sometime
  • Urgency & priority depends on time of the issue occurrence
  • Every issue has solution & there could be multiple solution options for single issue which may be suitable for different situation

Work Performance Information Cycle


Project information collection & dissemination is a cyclic process & vital one for project success. I collected few points here about project information cycle & thought it is worth sharing with all of you:

•Data collection for a project starts very early in project life cycle

•Lot of information collected in projects from various sources within and outside the project

•Data collection is a continuous process throughout the project life cycle

•Collecting & organizing data and transforming them as information (i.e. project performance) helps in decision making & effective communication

•Data/information can be a written document or verbal statements

•Organizational process assets is repository of information for previously executed projects & provide valuable inputs to other projects

Project Information Cycle

Due to confusion over terms like data & information, PMBOK came up with crystal clear definitions for each of those terms.

•Work Performance Data – data collected on day-to-day basis in project work execution (Example – % of work completed, # of defects)

•Work Performance Information – data collected from controlling processes that are used to analyze the project performance (Example – status of deliverables)

•Work Performance Report – way of representing the project work performance information that delivers intelligence for decision making (Example – status report, project dashboard)

Work Performance

Work Performance Flow