Welcome to the Travels of a PM Pioneer.. feeling alone in that tunnel?

Hi. Welcome to my blog. This little website is intended for PM's who are on the leading edge. Are you pioneering on your own? In an organization? Or out in the industry? Read on!

Thursday, March 12, 2009

Kath's jaunt with Context Diagramming to PMI GT ISLIG in January 2009



Hi everyone. Back in January 2009 I was invited to present the new Context Diagramming for Projects method to a local chapter of the Project Management Council, the PMI GT ISLIG (PMI Greater Toronto Information Systems Local Interest Group). Now there's a mouthful of acronyms!


Everyone working merrily away ... it was a wonderful evening of discovery for the whole audience.

Here's a link to the event description, presentation and feedback.

http://www.gtislig.org/DinnerEvent200901/DinnerEvent_200901.htm

The feedback on the material was excellent. Someone sent me this link of summary and pictures. If anyone is interested in a repeat of this lecture, they can contact me directly.

NEW EMAIL ADDRESS AS AT 2010-03-30 - kathleen.gillis@gmail.com


Go ProjectGirl!

Friday, March 6, 2009

Projects as models, not sequential task lists

I had an interesting discussion with one of our SME's here this morning. She's working with a tool called SEER made by Galorath, which predicts estimates to a level of accuracy, based on scope, inputs, risks, and methodology choices. It's fascinating.

What was new to her was that actuals which occur, vs. the estimates she creates -- the Cost Management points on the Project Baseline -- are affected by any changes in the 9 knowledge areas.

  1. Project Integration
  2. Project Scope Management
  3. Project Time Management
  4. Project Cost Management
  5. Project quality Management
  6. Project Human Resource Management
  7. Project Communications Management
  8. Project Risk Management
  9. Project Procurement Management

For example, if the Organizational Strategy changes, it affects Project Integration, which can affect the whole model.

If Resources are not present from the business while requirements are being gathered, it will causes gaps in scope, and therefore increases effort and ultimately costs, and likely quality.

If Resources are switched, pace can slow down due to learning curves.

If a schedule is "crashed", it can cause costs to skyrocket because resource needs change.

Everything that happens on a project can cause forecasts to rise, which is why performing Risk-Based Project Management is so very important. It's also important to use Earned Value techniques to continually retrack your project, and predict cost overruns or delays before they drive a project off the rails.

It's also important to see projects as an integrated model -- all the points attached. If you change one thing, it affects the other 8 areas, and ultimately wlil cause variance against the baseline.

Variances must be planned for with good Contingency planning.

More on this, another time ...

The ProjectGirl, Kathleen!

Thursday, March 5, 2009

What I'm working on...

A little bit about who I am in the world of Project Management. This entry may be updated repeatedly throughout the life of the blog.

CURRENT ROLE: Employed by a large Canadian FI (30,000+), running the Project Management Centre of Competency. We have a number of responsibilities in this shop. We:

  1. Perform R&D work to ensure our organization is aligned with Industry standards
  2. Drive industry standards, in some cases, by "raising the bar"
  3. Set the standards for project methodology
  4. Write the processes for how the standards will be executed
  5. Develop and document the competencies expected in the PM role
  6. Develop and ensure consistent delivery of PM Education and Accreditation in the organization
  7. Anything else our director assigns us :>)

That being said, a lot of the position is a happy mix of technology, methodology, research, and change management.

PROJECT CONTEXT DIAGRAMMING: This is such a fun thing! I attended a business analysis course which included techniques for eliciting Product Requirements. With a shift in thinking and some modifications, it was easy to apply it to Project Requirements. This has produced a whole new perspective in Critical Thinkins tools, and I've been presenting this new idea at PMI Chapters and some conferences lately. You can see your whole project on a page complete with roles, responsibilities, information flow. A whole new perspective on project stakeholder identification and management. Stay tuned for my upcoming lectures and workshops at ProjectWorld in Toronto, May 2009.

PRINCE2 CONCEPTS DEVELOPMENT: I recently attended a conference where I was seriously impressed with PRINCE2 Concepts. Developed by OGC, the same people who developed ITIL, it's got a lot of the issues solved in the methodology, that PMI didn't address in PMBOK. For example, it sets a project up for success immediately by positioning it as a vehicle for change, and puts in a governance triad at the front of projects that ensure it's seen wholistically by the organization, with the right players at the table. I believe that incorporating some of the basics of PRINCE2 by embedding them in our internal cultural change management messages, even without actually changing our processes, will help us to move our organization ahead quickly, and pic up the pace. For more information on PRINCE2, contact http://www.procept.com/.

PM INTERNAL ACCREDITATION REFRESH: This year, my focus is on revitalizing and refreshing our internal accreditation program. It's interesting because one of the challenges is to have people understand that "Accreditation" does not equal "Education" or "Certification," although these things may be components of Accreditation. This project will involve some radical changes to the curriculum, and some intense change management of culture to ensure that the changes are embedded, accepted, and *championed* by all levels of management. This will be a monumental task, but we're up to it! (I use the "Royal We" here. Yes, it can be enough to drive any Extreme Project Manager such as me, crazy.) The best reference I have on this is the "Project Manager Competency Development Framework" by PMI.

RISK ASSESSMENT CONTENTS EXTENSION: Other projects I am currently working on involve the extension of our Project Risk Assessment Model to include content and questions from our Operational Risk department. It's very important that Risk Assessment contents be kept updated, and the contents aligned with the of the parts of the organization that actually are concerned with Risk. Developing a Risk Taxonomy is the eventual goal.

COST MANAGEMENT AND EARNED VALUE: The other major focus this year, is about setting better controls in the Cost Management knowledge area. We're looking at a simple way to roll out Earned Value Management by gently framing it as "good business sense" and removing all the accounting-formula-speak in the foreground. It's a pretty innovative, low cost solution to a very high-cost problem. Stay tuned for more on that. The standard I am reviewing for this, is PMI's Earned Value Management standard. I've reduced the whole thing to a one-page user-friendly Excel model (no easy feat have you seen this stuff?) which boils down to the entry of just 4 fields. Whew! And they test us on what? In order to support this initiative, we're rolling out WBS and PERT tools to ensure that people are developing appropriate project models which are defendable, and easy to manage. "Dynamic Scheduling" by Eric Uyttewaal is the reference and course materials we're studying to develop a solid prototype for the required Project Template for our organization.

Stay tuned for more updates on initiatives under way!

Inaugural Entry - March 5, 2009

Hello everyone. So much is going on in my little corner of Project Management, I thought it was important to start keeping a blog. I run across so much useful information, it's important to share it with a larger community.

My intention with this blog is to provide insight into Project Management as an evolving profession. I'm working on so many interesting things that are really pushing the envelope, and having the Lessons Learned recorded for others about things I run across would be really helpful.

Someday, the notes I record here will be part of a larger book. But for now, consider this my little Project Manager's diary of interesting things.

Consider the information you find published here, copyrighted. I'm happy to share, just ask my persmission first. I will be keeping track of that for sure.

Welcome, readers!

Kathleen Gillis, PMP