employee burnoutEmployee burnout is every project manager’s worst nightmare. Burnout leads to productivity drop, lessened enthusiasm in the team and can lead to lost business. As project managers we not only need to ensure that we do not get burned out but our team members are protected against it too.

While there are many factors that contribute, anything that makes people not enjoy their work might eventually lead to burnout. Some of the factors are identified under three buckets in this post, and focusing on them should help you safeguard your team against this workplace epidemic.

Defining Burnout

Maslach and Goldberg, two UC Berkeley researchers in their article in Applied & Preventive Psychology describe employee burnout as including symptoms of exhaustion, frustration, and anger, as well as feelings of ineffectiveness and failure.

Let us look at 3 categories of Employee Burnout Busters you can focus on to have productive and happy team members in your team. [continue reading…]

PMESN Facebook contest winnerIt’s been another eventful month at PMESN!

Facebook contest winners

Facebook contest ‘PMP Question Of The Day’ has seen 40% increased participation and although questions have been marginally tougher than previous months, more of you are attempting them and getting right answers. Which is fantastic!

We have a new winner this time – Hayat Khan! Congratulations, Hayat!

Two people have jointly taken second place – Lalit Sharma and Muhammad Zulqarnain – both tied up with 17 answers each!

The third position goes to – Koshy George!

Congratulations to Lalit, Muhammad and Koshy! [continue reading…]

productive project meetingsLet’s start with a question –

Which activity is the biggest productivity killer in a project?

Ill-conducted Project Meetings.

If you lost an hour doing some activity that wasn’t productive, well you lost 1 hour. What does a 20 member team meeting delayed by just 10 minutes cost? At least close to 3 and an half hours of lost productive time!

Meetings are necessary. There are all types of meetings – snap meeting, daily stand-up meeting, end-of-phase sprint review and retrospection meeting, weekly customer meeting, monthly all-hands meeting, regular meeting with Quality Assurance team, weekly status reporting meeting higher management, technical review meeting – a zillion special and general purpose meetings.

Meeting is part of communication management domain knowledge area of product manager. No wonder that project manager spends on an average 90% of time on communication related activities. If these meetings are not made effective, a project manager you will not have time to do rest of her work.

Well, you will not have control over some of the meetings as a participant, but the ones you hold within your team and with customers you can definitely make sure that they are done well. A well-conducted project team meeting can do wonders for team’s productivity and project success. [continue reading…]

ITTOsQuick note from Shiv: I’m happy to announce that this post was included in one of the PMP books published by Cornelius Fichtner recently. Yay! 🙂

Trying to remember ITTOs (short for ‘Inputs, Tools and Techniques, and Outputs’) is most stressful task for anyone preparing for PMP exam.

For my study I was trying out different means of doing so, including mnemonics, mind maps and so on – till I realized that it is a futile exercise.

There are 49 processes (much lesser when I prepared for my exam) and on an average say 10 ITTOs per process, making it around 500 ITTOs (I haven’t ventured out to count really).

So, I went around various online forums looking for a solution and discussed with several people who have passed PMP.

What I learned is that it is not necessary to try to remember all of them.

As I thought through more, it made sense to me. PMI wants to test whether we have internalized the processes and what it takes to accomplish certain project management activities.

PMI’s intention is not to test whether we can remember every input, tool and technique, and output from 49 processes.

PMI only tests if we are able to apply our understanding of a particular process.

With this realization I went about understanding each process, what is it supposed to accomplish, how it relates to previous and next process in sequence (in the same Knowledge Areas as well as across other Process Groups and Knowledge Areas).

Next, I found another nice way to understand ITTOs.

That is to understand the Data Flow Diagram of every process.

In PMBOK you will find a DFD at the beginning of each process. It shows where does the input for the current process come from and which processes do the outputs go into. This is a great way to understand the flow of project management work in a process across PGs and KAs.

A caution though – don’t try to do this for too many processes at one time. One way to approach PMP study is to take one process at a time and study it across all of the study resources you have chosen (PMBOK, PMPrepCast, PMESN blog notes, Rita, HeadFirst…– but hopefully not more than 3, for the best returns on your investment of time, efforts, and money.)

The best way that has worked for me is to study DFD as part of the study of a particular process itself.

For instance, during my first round I focused on understanding one process every day, so I would spend a good amount of time on DFD of that process. Just understand and them move on, don’t stress yourself to remember it.

You will be able to deduce it quite easily once you do a couple of rounds of study.

During the exam I realized that our knowledge of ITTO is tested in a way that if you have understood the process you will be able to deduce the right option among the 4 options.

In essence, the 3 ways to remember ITTOs –

  1. Understand the process and its preceding and succeeding process in the KA as well as across PG and KA
  2. Understand DFD of every process as part of its study, do not skip it. It might look a bit overwhelming at the beginning, but once you spend few minutes with it, it starts to make sense.
  3. As you study a process, think how you can apply the same to your own project (or previous projects). If possible even implement what is possible at your work. This practical aspect of the study makes it quite easy to remember the ITTOs.

To summarize,

My suggestion is NOT to try and remember ITTOs of 49 processes, it will stress you out. Rote way learning is a stresser.

Understand the process, its DFD, its relation to other processes across KAs and PGs – this should be sufficient to tackle any ITTO related questions on the exam.

Do you want to use the same PMP preparation products that I used to pass my PMP exam? Click here to get them and a PMP prep course I am giving away for Free!

Note –

You might find these posts useful in your PMP exam preparation:

Do not hesitate to write to me at(at)shiv@pmexamsmartnotes(dot)com if you need any help with your exam preparation.

Good luck!

Cheers and all the best,
Shiv

[SneakyAffiliate sneakyaffiliateurl=”https%3A//www.pmexamsmartnotes.com/pmprecast-myposts” sneakyaffiliatecookiexpdays=”1″ sneakyaffiliatesplash=”Are%20you%20sure%20you%20want%20to%20leave%20before%20you%20checkout%20special%20PM%20PrepCast%20sale%20by%20Cornelius%3F”] [/SneakyAffiliate]

PMESN Contest Winners Feb14Winners announced for the ‘PMP Question A Day’ contest for February 2014.. and this time there is a surprise – We have joint winners!

Big congratulations to Asmara Rahat (third time winner in a row) and Faisal Shahzad!

We have Lalit Sharma on the second position and again a joint winners at the third place – Koshy George and Munir Hossain Auntu!

Here’s the tally of correct answers.
PMESN Feb-14 winners names

Let us see some tough fight to the chart toppers in this month!

Achievers in the PMESN Community

One of our community members, Syed Ali passed PMP on 28the Feb 2014.

Hi Shiv
I have just passed pmp today , just want to acknowledge that I have used your notes and found them useful.
thank you.

Congratulations Syed, and all the best!

manage complex projectsIt is generally believed that if you use Agile project management methodologies managing complex projects becomes messy and unmanageable.

This is due to the incorrect belief that large projects with complex platforms, upfront delivery schedules, and large project teams are hard to manage in the dynamic project environment.

In this post let us examine the Agile and Traditional project management approach to managing large and complex projects.

First, take a moment and answer this question –

What is the most critical skill required for the project manager to manage complex projects?

  • Technical skills,
  • Business management skills,
  • Leadership skills,
  • Project management skills

You’d be surprised to know the answer: [continue reading…]