Terrapin Agrada

Project and change management expertise

  • Home
    • About
    • Contact
  • Blog
  • Books
  • AMAZING Project Management
  • AMAZING Change Management

15 Things I wish I knew about projects before I became a Project Manager

22 August 2016 By Susan Tuttle Leave a Comment

project-1306389_1920I was recently asked for my advice about projects for someone who wants to ‘get into’ project management. I told them in all honesty, that I’d only be able to give them advice from my limited experience. Although I’ve been ‘doing’ project management for over 20 years, I’m one in a million/millions doing this. So after I shared my advice, I also encouraged my ‘new to project management’ friend to google ‘things I wish I knew before I became a Project Manager’. I hope he did. I’m sure it would add to this list.

 

Here are the things I shared. Do you agree? What would you have shared?

First off, there are really only two guarantees about projects: Every project is different and Change will happen. Having said, I still have 15 pieces of advice that are pertinent to every project, regardless of size, shape, length or complexity.

  1. Agree the details and priorities with the Sponsor / Project Board at the beginning (not the end!)

It’s too late at the end of the project to find out that the Sponsor / Project Board had ‘other ideas’ (either mentioned or not) about what the project was set to deliver. Before undertaking a project, sit with the Sponsor (physically or metaphorically – over the phone, via documentation, rounds of email or through entries into a project management system) and come to agreements about the basics for the project (who, what, why, when, how and how much) being sure to agree on time, cost and quality expectations. Most importantly agreeing which is the priority!

  1. Decide how to document (to whatever formal level required) and document to that level

Some small projects needn’t have much documentation. A lot of information can be captured in emails and meeting minutes. But just because a formal document isn’t required, understand how will this information be captured and stored. For large, complex projects, documentation is normally required. Decide on the templates, the level of detail required and the recipients / distribution lists of the information.

Once a level has been established and agreed, throughout the project abide by these documentation rules. When time pressures abound it’s easy to forget to document things. There’s always the intention, but it keeps getting pushed down the to do list until it eventually falls off. Be diligent. Keep records. And keep them according to the level you’ve determined to be correct for your project.

[Read more…]

Filed Under: Blog, Project Managment Tagged With: change, close out, documentation, issues, kick off, plan, project, Project Manager, quality check, risks, tests

Previous Posts

Everything’s a draft until it’s not

AKA: overcoming paralysis by analysis Lately, I had been feeling overwhelmed with starting some … [Read More...]

4 cognitive biases that might be impacting your project planning sessions

You plan and plan and plan and plan and yet… nothing goes according to plan. Maybe you and your … [Read More...]

Do you need a facilitator for your workshop?

Short answer: Yes. Someone with the right training AND a level of independence from the outcome of … [Read More...]

10 Exercises for finding the source of elusive Project/Programme anxiety

I hate being blind-sided. However, something, somewhere on my project was keeping me up at night. I … [Read More...]

7 ways to deal with down time for Project Managers

For many Project Managers the holidays are light (potentially very light) in terms of work load. If … [Read More...]

  • Copyright Notice
  • Disclaimer
  • Terms and Conditions
  • Privacy Policy

© Copyright 2016 Terrapin Agrada · All Rights Reserved· ·Lovingly Made By DanielL· Log in