During My PMP preparation I was always looking for some interactive way of studying but was not able to find any. The only thing which didn’t bore me was Head First PMP. I love their full series and I have a couple of them. So I cut th long story short, I wanted an easy way to remember all the PMP processes and flow of processes.
The stature of projects have changed in the last decade. Project costs have gone from millions to billions of dollars, from 100 members to 1000s of team members,from one office to global. With the humongous sizes of project its easy to commit a mistake or overlook some important aspects of a project. The point which may look trivial at one point in the project could lead to a total catastrophe and damage the outcome.
CIO.com surveyed a lot of project management gurus and companies for the common project management mistakes and found that there are some common mistakes to every project. Based on the list here are some of the common project management mistakes and you should avoid those for the success of your project.
I Want to Manage Large Projects.Every Project Manger
Be careful what you wish for.
Managing a large project is a complete different story than managing multiple small projects. For eg. managing a deck project at home is completely different than making a dam. Imagine the number of stakeholders, the risk factors, cost, political and environment factors etc. It takes several years of experience to effectively manage a large project. Some of differences I have explained you in above lines but there are more which makes large projects different and more complex to manage.
Monday morning – I open my email and see an email from Tim, business analyst hey saying “Hey AKASH we have bagged another Mobile application project and by the sounds of it, is going to be the next big thing”. The e-mail gave tears of happiness to accounts team, the sales manager and business development manager. I was also in tears but not happiness but what I call is tears of fear. To be very honesty every project manager gets those tears of fear irrespective of the experience they have in their pocket.
There is an old saying, which I guess everyone must have heard it before. The saying is “Learn from your mistakes”. Never knew that this saying which I heard from my grandma will be an important part of my project management and business analyst career. On the other side PMBOK actually clearly specifies it as a best practice. PMBOK says to document the lessons learnt for each project and make it accessible to other project managers as well for future use. So I am following the code of PMBOK and writing all the things that I have learnt in my career as a business analyst, developer and a project manager. You can call them as lessons learnt or best practices, but I prefer to call them lessons learnt as these things I have learnt on my own as I am not as smart as CHUCK NORRIS.
If you would have served as a business analyst or a project manager you know the importance of workflows. Coffee/wine loaded client meetings (if you are not using cisco webex or skype) you jot down each and every point of discussion, record the session but in the end when you try to do the knowledge transfer to your team errrrrrrrr.. That is a situation every analyst faces or has faced in the past.
In last 4 years I have worked in different roles, I have moved from being the database guy, then the core I.T. / Programmer to a management person. That core experience has given me a lot of insight and an upper hand in my role as an analyst and a project manager when compared to managers who just came out of school with their MBAs. I find myself better with understanding the requirements of the clients, creating the charter with team, creating the Work breakdown structure and assigning the team/resource to those tasks.
As we all work in an environment where we are responsible for tasks that we perform, we might also be accountable for those task/s. We might be consulted in for a task or two or might just kept in loop for some tasks. This when tabulated in a sheet is called the RACI matrix pronounced as RACEY or it is also called the resource allocation matrix (R.A.M.)