Vicki James, PMP, CBAP, PMI-PBA, CSM

formerly of Professional Project Services, LCC

Category Archives: Project Manager

Document Your Project History

How often have you been called upon to remember past projects? Are you prepared to respond to “tell me about your favorite project and why it was your favorite”?  If you are pursuing professional certification, a new job, or promotion, be ready for this question. If your brain is like mine, it is an overflowing file cabinet with some of the best material buried in the back corner. It is not always easy to access the things you have done in the past, especially when new projects are always sitting on the forefront of the mind. As a result, you will likely shortchange yourself by relying on the more accessible recent experiences that may be less relevant in the context of the position. Perhaps you come up short on needed hours experience for that professional certification because you had forgotten about that part time project you worked on when in a different position. There is a remedy for this. That is your Project Portfolio History.

I created my Project Portfolio History when applying from Professional Project Manager Certification from the Project Management Institute.  It was a necessary step for completing the application, but I quickly saw a multitude of uses for this listing. The list includes:

  • Project Title
  • Start Month
  • End Month
  • Number of Months
  • Organization
  • Project Description
  • Role
  • Responsibilities

Image

Customize your Project Portfolio History to meet your specific needs. You may add a column for percentage of work time spent on the project, the project sponsor, team members, project methodology…whatever makes sense to you.  This is your reference and a supplement to your resume, not a replacement. You may opt to share with recruiters in which case it might make sense to keep a “private” version in addition to the “public” version with the private including key words or signals that you want to remember without sharing. My private version has notes to remind me of my favorite projects, least favorite projects, projects where I learned the most, and many of those other common asks when discussing your project past.

The project description should help describe each project and what made each unique. What technologies and methodologies where used? What was the team structure? Who were the users of the solution and how the accessed it? You do not need to answer each of these questions – rather you are looking for what about this project sets it apart from others.

This document has helped me in describing experience in resumes, cover letters, and in interviews, as well as document hours for both the PMP and the Certified Business Analyst Professional (CBAP®) certification.  I use it when customizing my resume to the job I am submitting for, developing my cover letter, review prior to an interview for a fresh look, and I even request to keep the document out and handy during an interview. I have yet to be refused to have my “cheat sheet” handy. Recruiters and interviewers have requested a copy. Remember to have a public version available. One recruiter I worked with said, “This is great! Every project professional should have this.” Start putting your together today. I have linked a Project Portfolio History template so you can get started on yours today. Start with your current project and work backwards. You can always add rows to fill in gaps if you miss something along the way.

Please share your experiences with this or a similar document by commenting on this post.

An Ounce of Prevention – Agreement and Documentation of Project Roles

Have you ever been on or lead a team where confusion over who should do what existed? Maybe there was a ‘roles and responsibilities’ document or even RACI chart on the wall, yet team members struggled. Struggles commonly persist when a task was not included in the document or the team members did not accept the assignments. Have they even seen and reviewed it? Unclear expectations and lack of communication leads to team conflict, something we all want to avoid. Below is one exercise I have done with teams that has resulted in a better understanding and respect in team members’ roles.

Purpose

Generate team discussion and agreement on who is responsible for the completion and quality of project tasks.

Participants

All team members for a small team or a representative of each team discipline for larger teams.  No discipline should go unrepresented. For best results, ask for an independent facilitator so that the project manager can be a full participant.

Time

Two-hours

Materials

  • Large index cards or sticky notes
  • Empty walls for posting cards
  • Felt pens

Preparation

  • Write out a team task, one task per card (may be hand written with felt pen or creating labels to stick to the cards may save some time) – Sample Set of Labels
  • Create a card for each project team discipline (e.g., developers, business analysts, test team) including single person roles (e.g., project manager, sponsor)
  • Use the team discipline cards to create areas for columns, or groups, of tasks on meeting room walls. Additional groupings for “ALL” or “TBD” may also be represented.
  • Leave some blank cards and felt pens around the room for team members
  • Organize your pre-written cards so that can easily get to the most controversial tasks easily

Meeting

  • Explain the goal and process for the meeting to team members
    • Goal – Assign all tasks to project sub-team or members with full team agreement
    • Process – Ask the meeting participants where each task belongs as far as who do the task. Encourage discussion of “why” when there are differences of opinion. There are no right or wrong answers. Whatever the team agrees to is correct. The project manager may suggest best practice, but not dictate the final assignment.
  • Start with a few more obvious tasks such as “write program code”
  • Post the card in the in the group that the team agrees
    • Where differences of opinion, ask those most directly affected to explain why they choose that role or discipline
    • See if team members agree after hearing explanations
    • If still no agreement, offer the project managers view on where the assignment belongs
    • See if team can agree to the project managers view, specifically those most affected
    • If still no agreement put task aside or post in “TBD” to come back to
    • Limit the time per card to about 2 minutes
  • Move on to the tasks that are likely to generate the most discussion once team members have a handle on how the process works
  • Team members may propose new tasks for discussion by writing out a card
  • Stop about 10 minutes before the scheduled end time to get agreement for handling remaining tasks. Possible options include:
    • Extend meeting time
    • Schedule a follow-up meeting
    • Assign delegate to propose assignments for any remaining tasks and send to team members
    • Inform the team how the results will be documented and where available for future reference

This exercise focuses on who does the work. There is still a need to document who reviews, who approves, and so on. This can come in a RACI-type chart later. Another option is to mark each card as team members discuss the assignment. Choose whatever method will get to team acceptance the quickest.

I mention a RACI-type chart for a reason. When creating a matrix of roles and responsibilities use the terms best represents how work is approved in your team and organization. “Responsible”, “Accountable”, “Communicated”, and “Informed” may not hold a lot of meaning to your team members where “Leads”, “Approves”, and “Informed” may be clearer. Let the team help decide on the categories to capture so that the resulting document is meaningful.

Closing

I hope this exercise, or some variation of it, will help to avoid confusion and conflict in your project teams. Please comment or email me if you use this exercise on your project. I am interested in how it went for your team; especially any adjustments made that provided even better results.

Happy International Project Management Day 2012!

It’s that time of year again. The first Thursday of November is International Project Management Day. Frank Saladis of the International Institute of Learning founded the day to promote project management as a professional and show appreciation for those who have chosen it.

This year I am very pleased to announce Women in Project Management: Leaders in Charge. It was an honor to take part in this pre-recorded panel discussion with Naomi Caietti, Deanne Earle, and myself, moderated by Martin Chernenkoff. This 1 1/2 hour webinar is good for 1.5 PDUs  in Category C. Visit www.pduotd.com to qualify for Category B.

Please watch, listen, enjoy, share, and comment.

http://internationalpmday.org/ipm-day-women-in-project-management/

6 Easy Ways to Earn PDUs for your PMP

Are you up to date on your PDUs? Is your renewal deadline fast approaching? Here are some ideas, in ease to earn order, to help you get your PDUs in time for your certification renewal. Full detail for categories is available in the PMP Handbook. Refer to your copy for additional information to plan for and record your PDUs.

Category F* – Working as a Professional In Project Management

You can earn up to 5 PDUs per year, 15 per certification cycle, for working full time as a project manager. Your 25% on your way to re-certification!

*Subject to maximum of 45 credits combined in categories D, E, and F.

Category C – Self Directed Learning

Anything you read, watch, or discuss related to project management may count towards your PDUs. Keep records of the time you participate in these activities along with any notes and record your PDUs. One PDU per hour of activity up to 30 PDUs in your certification cycle is allowed.

  • Webinars
  • Podcasts
  • Articles
  • Books

There are hundreds of self-directed learning opportunities on the web. Check out these links to find out more. Sign up for their email lists to get notice of opportunities directly in your inbox.

  • pduOTD.com – PDU of the Day provides PDU opportunities from all categories. Many are self-directed activities. Opportunities listed provide information includes category information, recording requirements, and anything else you need to know to make the most of the opportunity provided.
  • PDUInsider.com – This is a portal to many PDU opportunities of various categories. Find an event calendar of opportunities or browse for on-demand activities that are available. Also includes a link to information on the PDUPodcast.com, an opportunity to earn PDUs through recorded podcasts.

Category E* – Volunteer Service

Have you volunteered with the PMI, maybe within your local chapter, or reviewing an upcoming standard on PMI.org? This also provides PDU credit. Find out more on volunteering at the PMI Volunteer page.

Volunteering is not just a great way to get PDU credit, it also is a great way to expand your network and your skills while benefiting PMI and project managers everywhere. You earn 1 PDU per hour up to the 45 PDU limit in your certification cycle.

*Subject to 45 credit limit for activities in categories D, E, and F.

Category B – Continuing Education

Did you know that you get credit for all project management training, not just training provided by PMI Registered Education Providers? That’s right! That is what category B is all about. Participate in any formal training session and get credit for that time of the curriculum that is project management specific. So go ahead and sign up for the project management workshop you want. It does count!

Category D* – Create New Project Management Knowledge

Do you write or train on project management? Well give yourself credit. PMI grants PDUs for sharing knowledge through writing, presenting, and training. You get PDU credit for preparation and presentation time hour for hour.

*Subject to 45 credit limit for activities in categories D, E, and F.

Conferences, Congresses, and Seminar Events

This is perhaps the most fun and efficient way to earn PDUs. Not only do you get a large selections of topics to see presentations on, but you get to meet project managers from around the world and see what is happening in the world of vendors and tools. You might not even have to record your PDUs  for PMI.org sponsored events as they will often do this for you from your registration and attended sessions.

A Final Note

Make managing your PDUs easier by recording as you as you earn them. This will make the overall task easier and provide an easy to follow view of where you are in your certification cycle. Record your PDUs online on the Continuing Education Requirements System. Got too many? No problem…you can roll over up to 20 PDUs for your next cycle.

* Categories D, E, and F are grouped as “Giving Back to the Profession.” PMI has placed a limit on the number of PDUs allowed in these categories to 45 per certification cycle.
Image credit: nikolaev / 123RF Stock Photo

Number One Benefit of Achieving the PMP

I taught my first week long PMP Exam prep class last week. I recall when I first learned of these boot-camp style classes and my original thought. “Great, you learn how to pass a test. Did you learn anything about project management?” I often comment on my study experience that I learned more in studying for the PMP then I did in a 9-month university certification course and prior experience. The challenge for this course became to incorporate true learning into the crash course – to motivate the students to see how the processes, inputs, tools and techniques, and outputs would make their projects more successful.

I scheduled one-on-one briefings on the last day of class. One student, Marcus, talked of his father who had recently passed the PMP while in a long career in project management. We also had a few “seasoned” project managers in the class. Marcus questioned the value of the PMP for these folks with the reasoning that they had been successful project managers in their careers without the PMP. “Have they been successful with a reported project failure and challenged rate of 65%?” The bottom line is that even a successful project manager can learn new ways of doing things based on industry best practice and increase the chance of project success. There is no room for complacency in managing projects with millions of dollars at stake and an unstable economic market. Learning is the number one benefit of achieving the PMP.

Marcus went on to asked about case studies to support the benefit of PMP. I suggested that PMI would have plenty of information published through pmi.org and offered up the two following books for further exploration.

Remember this next time a non-certified project managers claims that a PMP is not beneficial –

Never become so much of an expert that you stop gaining expertise. View life as a continuous learning experience. Denis Waitley

Disclaimer: I do not profess that someone who has a PMP is superior to someone who does not. Only that one will have learned and demonstrated more knowledge than before attaining the PMP. See The  Chef or the Cook: Choosing the Right Candidate

Additional Resources

Related articles by me

Achieving Success through Business Value

I am thrilled to announce ModernAnalyst has published my article on Achieving Business Value – check it out and pass it on. I look forward to your comments on the ModernAnalyst site or here.

Business value is a new indicator for project success. Huh? You may be wondering what ever happened to the good ole scope, schedule, and budget. They are still there and measured, but what the 2012 trends have been pointing to is that a project completed within scope, schedule, and budget and not be successful. The opposite is also true. Read complete article

I just ran across this excellent supporting video on Twitter.

Tim Banfield, APM, Project Managers should define project success “in their own terms”

Full article

 

 

Rescue the Problem Project Book and Study Guide Reviews

I am pleased to announce that I have published reviews for both Rescue the Problem Project: A Complete Guide to Identifying, Preventing, and Recovering from Project Failure
by Todd C. Williams and A Learning Guide For “Rescue The Problem Project” (pduOTD Primer Series) by Martin Chernenkoff.

Click the links above to find full reviews and purchase your own copies!

Do Not Miss This Critical Piece of Information for Project Success

I have a new appreciation for a specific project need after teaching a Mastering Requirements course earlier this week. I had asked the participants to come up with examples of goals or requirements for a situational software product. However, I did not offer them the two most important pieces of information, the project vision and objectives. It was an oversight on my part. I erroneously thought that they would automatically have the same vision as I if I provided a clear project title such as Classes Registration System. Two things happened.

They had a hard time getting started on who the users and their goals would be for the system. There wasn’t a clear place to start without knowing whose problem they were trying to solve or what the objectives of the project were. Instead they would tentatively put an idea out and look for clues that they were on the right track. The ideas were rolling once I said “the project is…” and “the objectives are …” You could see the light bulb turn on, “oh, so that’s what we’re doing.”

Another exercise was to take a stakeholder statement “I want full details on students” and interview me to get to the real need. I inadvertently tripled the size of the project by adding requirements related to a Customer Relations Management (CRM) system. Lucky for all of us, one clever participant spoke up, “I thought this was a class registration system. It sounds like you want a CRM solution for marketing.”  Oops…busted! Yes, I was the scope creep.

It is much easier to call “creep” on an instructor in a classroom setting then it is an executive manager within your organization. You are likely to run into “just do it” even if you do say something. Your best defense…a clear, documented vision and objectives for the project to serve as a guide and negotiation tool.

Vision – a description of how the world looks after project implementation.

Students will be able to sign up for designated classes and the organization will have a record of who has attended what classes.

Objectives – expected measurable results from project implementation.

  • Reduce overall staff time required per student registration by 75%
  • Time to complete inquiry of student participation is not more than 10 minutes (from opened to responded)

Responding to ideas outside of the vision and objectives become much easier with this context. Now the BA can respond with “how will that help us meet the objectives of the project?” when the business owner says “I want the student’s home address so that I can send a Christmas card”. While having other features may be nice and add value, it clearly does not fit into the intent of the funded, schedule project. Scope creep diverted – schedule and budget saved.

How many “quick, little projects” have you worked on where the vision and objectives were assumed rather than documented? I’ll admit it, I’ve seen a few. It won’t happen on my projects, or in my class, after seeing the difference that simply documenting and agreeing to these makes. That doesn’t mean I won’t try to trick students so that we can practice scope negotiation in the future.

More information on this class is available at https://project-pro.us/2012/04/17/master-requirements/. Contact me to bring this class to your area.

The Project Manager vs. the Business Analyst

I have a hard time deciding whether “versus” is a good word to compare the two roles. On one hand, the project manager and business analyst should be working collaboratively. On the other hand, the two roles do offer a healthy contest in project related decisions. The issue at hand is that there is a lot of uncertainty about the difference in these roles. The result of this uncertainty is cases where one person plays both roles without enough skills for each, and other cases where the team members do not know who is responsible for what. Hopefully, we can clear this up.

The core of the difference is in the title.

  • The Project Manager manages the project – “The application of knowledge, skills, tools, and techniques to provide activities to meet the project requirements.”
  • The Business Analyst conducts business analysis – “The set of tasks and techniques used to work as a liaison among stakeholders to understand the structure, policies, and operations of an organization, and to recommend solutions that enable the organization to meet its goals.

One source of confusion is the activities in both sets of tasks according to the relevant Body of Knowledge[i]. The intent is that planning and monitoring tasks within the BABOK® are limited to business analysis activities as indicated by the task title.

PMBOK® Task BABOK® Task
  • 4.2 Develop Project Management Plan
  • 2.3 Plan Business Analysis Activities
  • 2.5 Plan Requirements Management
  • 2.6 Manage Business Analysis Performance
  • 4.4 Monitor and Control Project Work
  • 2.6 Manage Business Analysis Performance
  • 5.1 Collect Requirements
  • 2.5 Plan Requirements Management Process
  • 3.1-4 Elicitation: Prepare, Conduct, Document, Confirm
  • 4.2 Manage Requirements Traceability
  • 4.4.5.1 Requirements Documentation
  • 5.2 Define Scope
  • 5.4 Define Solution Scope
  • 5.3 Create WBS
  • 4.1 Manage Solution Scope
  • 5.4 Define Solution Scope
  • 5.4 Verify Scope
  • 7.5 Validate Solution
  • 8.3 Perform Quality Control (Testing-monitoring and recording results)
  • 7.6 Evaluate Solution Performance(Results analysis and recommendation)
  • 10.1 Identify Stakeholders
  • 2.2 Conduct Stakeholder Analysis
  • 10.2 Plan Communications
  • 2.4 Plan Business Analysis Communication
  • 10.3 Distribute Information
  • 4.5 Communicate Requirements
  • 10.5 Report Performance
  • 2.6 Manage Business Analysis Performance

* Thank you to Elizabeth Larson for review and advice to the PMBOK® / BABOK® process mapping.

Stakeholder analysis is one good example of collaboration between project manager and business analyst. The business analyst focuses on stakeholders specific to the requirements and scope of the project. The project manager is looking beyond this to stakeholders whose interest is outside of the project scope. Perhaps the project manager is recording a competitor as a stakeholder to aid in the identification and tracking of potential project risk. The stakeholder analysis is a joint effort. Assign items resulting from the stakeholder analysis to either the project manager or business analyst based on stakeholder interest and influence.

Another point of confusion is in the PMBOK® task of Collecting Requirements. It looks as though the project manager is responsible for collecting requirements. When you look further at the PMBOK® tasks you also find Perform Quality Control, yet we know the project team has members responsible for product quality. The intent of the PMBOK© is that project managers take responsibility to ensure activities for collecting requirements are covered in the project management plan and monitored along with the project. Not the project manager collects the requirements.

Section 5.1 of the CBAP® Handbook does a great job of differentiating “analysis” activities from other activities. Download the CBAP ® handbook from the Certified Business Analysis Professional™ (CBAP®) website for detailed examples of these activities.

Volunteers from both the International Institute of Business Analysis (IIBA®) and Project Management Institute (PMI©) joined in a collaborative project to “facilitate a shared understanding of the roles.” You can read more on this effort and results at http://pmchat.net/2012/06/the-bapm-partnership/.  The conclusion –

Both the PM and BA play leadership roles—the PM for leading the team and delivering the solution and the BA for ensuring that the solution meets the business need and aligns with business and project objectives. And both roles, equally, are required for project success.

You will get decisions based on full information of the impacts to the project and the benefit of the solution when you have both a strong PM and BA playing leadership roles on your projects. The result is a project that brings greatest business value to the organization.

I had the distinct pleasure of joining Elizabeth Larson, PMP, CBAP, CSM, as guest experts on PMChat (a weekly Internet radio show/Twitter web chat) to discuss the BA and PM roles on June 1, 2012. Listen here to catch our interview hosted by Robert Kelly and Rob Prinzo for more on this subject.

September 2015 Update: Please check out my book, Leveraging Business Analysis for Project Success Book Cover Image (Business Expert Press 2015), for more on the role of the business analysis and discussion of the Power Project Team.


[i] Project Management Body of Knowledge (PMBOK® Guide) 4th Edition

A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide) Version 2.0

References

http://www.blogtalkradio.com/btrplayer.swf

Listen to internet radio with KellyProjectSolutions on Blog Talk Radio

Project Managers vs. Business Analysts

Event Announcement

Friday 6/1/2012 – PMChat Topic is Project Managers vs. Business Analysts 

I will participating in this event at the invitation of Robert Kelly and Rob Prinzo, PM Chat hosts. This is a great forum to share information and ideas with project peers. Find more information and archives to past topics at www.pmchat.net.
I am thrilled to announce that Elizabeth Larson will be co-guesting with me. The supporting article from Elizabeth is now online at http://pmchat.net/2012/06/the-bapm-…tnership/.
%d bloggers like this: