• Authors

  • Calendar of Posts

    May 2018
    M T W T F S S
    « Dec    
  • Enter your email address to follow this blog and receive notifications of new posts by email.

    Join 7 other followers

  • Advertisements

Can I be of service?

We’ve been looking at the integration management and how it relates to initiating and planning. With planning out of the way, we can look at Directing and Managing Project Execution, which occurs simultaneously with Monitor and Control Project Work.

Directing and Managing Project Execution is not the same as the executing process group, exactly. The executing process group is getting the work done. Directing and Managing Project Execution is integrating all of the efforts into a finished project. So, Directing and Managing Project Execution is the overview of the entire project (Mulcahy 118).

Mulcahy makes two critical points here: 1) Directing and Managing Project Execution involves managing people, doing the work (and therefore managing people doing the work), and implementing approved changes. And 2) it’s about ‘being of service’ (118).

In my opinion, these really become the two critical pieces of running a project: ensuring a common understanding, and being of service.  I think the picture I posted last week clearly sums up what happens when you don’t ensure a common understanding. As for being of service, look at that post I just linked to. Down there at the bottom, in the game plan: Everyone is your customer. Are we afraid to get our hands dirty to help keep a team member on track? Are we out in front of the risks, trying to remove roadblocks to keep things on track?

Tied with Directing and Managing Project Execution is Monitoring and Controlling Project Work. This is best seen as balancing the demands of the different knowledge areas to control the project (Mulcahy 122). The output is change requests, project plan and document updates .

As we’ve been saying repeatedly, in discussions about planning and discussions about process groups, all projects must be controlled. Controlling a project is about ensuring that the work is proceeding according to plan, and when it is not, creating change to push it back on track. Taking corrective action is, according to Mulcahy, the correct answer for what to do when a task takes longer than expected.

One method of keeping work on schedule is the work authorization system. As we get into more detail about work packages, we’ll be in a better position to discuss this, but essentially, this is signing off that someone should begin work, because the prior dependency is complete. Mulcahy gives the example of building contractors needing to work in the same place, but it also applies to formal sign-off from the developer that QA can proceed in reviewing the IT code (Mulcahy 122).

When you compare the work authorization system with the concept of being of service, it feels, on the surface, almost contradictory. On the one hand, you’re trying to remove roadblocks, and assist the team members. On the other, you’re standing the way of starting on a work package until formal approval is given. But, in the long run, when you have 100+ people working on a project, how much more helpful is it to make sure no one is tripping over each other?


Planning the plan

First, an apology about not posting often enough. It’s been the holidays, much of my spare time has been eaten up. So, I haven’t posted much. Sorry.

Second, I am officially registered to start the PMP exam prep course offered through the PMI chapter in Baltimore beginning on 1/7/12. I suspect that the first session or two will recover everywhere that this blog has been so far, so I should have more notes on how to refine my understanding.

Third, I’ve been trying to write this blog entry for a couple of weeks now. 2 weeks ago, we launched a change to our IT systems at work, which required me to oversee testing on the weekend. I was kept just busy enough that I was able to read a couple of pages of Rita, but not write my notes about it. So here goes.

We’ve been looking at the Integration Management area of knowledge over the past few weeks, which encompasses virtually all of the the Initiating process group, some of the critical steps of the Planning process group, and a little of the Executing and M&C groups, and resurfaces with much of closing. In the last post, we looked at how Integration Management is integral to Initiating.

In the table that Rita provided with the elements of the process groups associated with Integration Management, she identified planning the plans as the first Integration Management piece within the Planning process group (Mulcahy 98). So, every project has management plans (duh!). “Management plans are the strategy for managing the project and the processes in each knowledge area (Mulchay 112).”

More specifically, management plans  answer the question of “how will I define, plan, manage, and control scope, schedule, cost, quality, HR, etc (Mulcahy 112)?” Because of the work we’ve already done in understanding the business case, the company’s culture, resources, and procedures, we have an idea of how these plans will be modified to accommodate this specific project. No 2 sets of plans are identical, and even which plans are used varies depending on need.

Of course, the organizational assets dictate how the plans are created; for instance, if there is an existing change control procedure within the company, then the change management plan will mirror that (PMBOK 80).

Each of the Management knowledge groups has plans specific for it. Integration Management is focused on: Change management, configuration management, requirements management and process improvement (Mulcahy 113).

The project management plan integrates all of the other plans into a unified whole. It includes the baselines for the project. It also includes the project management tools that will be used on the project (for instance, which additional plans are being used); a requirements management plan; a change management plan (yes, it really includes this!!); a configuration management plan and a process improvement plan (remember, improving the process is a critical piece of the M&C process group) (Mulchay 113).

The development of the project plan mostly occurs through the use of expert judgement (PMBOK 81). This is when you circle the project team, and start working with them to define how to tailor the process to the project need, determine resources you have available and make sure their skills meet the needs.

Baselines: The project management plan includes baselines for the work that is going to be done. It includes the scope baseline (project scope, work breakdown structure and WBS dictionary- covered later in Scope Management), schedule baseline (scheduled start and end times for milestones), and cost baseline (time-phased budget) (Mulcahy 114). Why are baselines critical? Without baselines, it’s impossible to tell what is being accomplished on track. The project manager needs to track these baselines to identify deviations. When the work is deviating and the project cannot be adjusted to meet the baselines, then the change management process kicks in (Mulcahy 114). Most critically, deviations to the baselines usually stem from inadequate risk assessment, since it’s a risk that the baselines are changing.

Requirements management plan: We’ll discuss this more indepth as part of scope management.

Change Management plan: I like Rita’s statement: “…you need to stand as a barrier to prevent unnecessary changes and to plan the project in a way that minimizes the need for changes…Changes should not be undertaken lightly (Mulchay 114).” I think this summarizes what a change management plan is. How can you prevent unnecessary change (while acknowledging that projects will always change). The plan should contain the change control procedures; what the approval levels for changes are; the creation of the change control board; the plan outlining how changes will be managed; and the organizational tools used to track change (Mulcahy 115).

Configuration Management plan: I have to admit, this plan is new to me. The configuration plan “defines how you will manage changes to the deliverables and the resulting documentation, including which organizational tools you will use (Mulcahy 115).” Got that? This is the convoluted way of saying, ‘have a plan for version control of the documents, and the deliverables’. I think it’s a great idea.

Finally, Process Improvement Plan: exactly what this sounds like. This is the opportunity to discuss what processes will be used for executing the project, and discussing how these processes will be reviewed and improved up0n as the project progresses. This plan helps streamline costs, resources and time constraints, and, if the process is already one that the company uses, it would help improve best practices.

With all of these plans in place, it’s now time to start the project, yes? No! The important piece that PMI sees when it comes to project planning is that the plan must be able to be met. It must be realistic, it must be able to be achieved. Therefore, it needs to take into account conflicting priorities for the team members. It needs to only include scope that can be achieved, and the stakeholders have to be aware of what cannot be achieved. And, most critically, the plan needs to be signed off on by the team. Everyone has to be on board with the plan before the rest of the project can start. This is why the planning process group looks at the iterations of the Plan. The Plan needs to be reworked until its final (Mulcahy 115-117).

This raises a real-life issue about planning, which I’ll raise in another post…


Business Case selection

Over the weekend, the local PMI chapter announced their Winter 2012 courses. Included with them is a 6 session PMP Exam Prep course. I spoke to my manager at work, and while I need to front the $850, I got the commitment that the company will reimburse me, so it looks like I’ll be taking the class throughout the month of January and into February.

We’re continuing on about Integration management. We’ve already looked into what goes into a project charter, which is part of integrating activities into the unified whole of the project. One of the inputs to integration management is the statement of work (PMBOK 75). Essentially, this is the narrative description of products or services to be delivered by the project. This includes the business need, the product scope description and the strategic plan.

The second critical input to the charter is, a a rather circular manner, the business case (PMBOK 75). It’s in a circular manner in that the SOW includes the business need description, which is identified in the business case. So, the business case is required because it’s required for the SOW. It seems a little repetitive, but I’m finding that there are times that PMBOK documentation is like that.

Anyway, the business case! It “provides the necessary information from a business standpoint to determine whether or not the project is worth the required investment (PMBOK 75).” The business need and the cost/benefit analysis are included here. The business case argues for the project, and could have ramifications on the project implementation.

Rita Mulcahy goes on to describe methods of selecting projects, by breaking them down into ‘benefit measurement methods (comparative methods)’ and ‘constrained optimization methods (mathematical methods)’ (Mulcahy 106). She provides a lot of detail about economic models, which are categorized under comparative methods, but then indicates that all you need to know is the difference between benefit measurement and constrained optimization methods. So, I won’t go into worrying too much about the Present Value and Net Present Value calculations.

Finally, the last two inputs for the project charter are essentially the same thing: the working environment. We saw these in the initiating process group: 1) Determine company culture and existing systems and 2) Collect processes, procedures and historical information (Mulcahy 43). These, which are listed here as enterprise environmental factors and organizational process assets, are directly linked to 1) and 2), above (Mulcahy 111). The modify how the charter is drafted, and even how the business case was selected.

Thank goodness this post was about the Initiating phase. If it was about the Planning phase, I would be screwed. Why? Because I had intended the post to be about project selection methods. Instead, I wobbled to a number of different topics, because I didn’t plan how I was going to write it, or how I was going to have the time to finish it. Sorry.

Closing Process Group

Finally, finally, we’ve gotten to the fifth process group of the 5. Closing. This is the shortest list of steps. This is the one no one likes. This is the one that gets the short shrift (and you thought Planning was undervalued!).

We close the project now. We verify the work was done, and done to the original requirements. We close the procurements, and sign off on those. We sit down with our customers and make sure they agree with us that the original requirements were met, and that the changes were implemented as approved. We DOCUMENT that they sign off on this. We store all of the documents and lessons learned in a single location, so that when you start the next, similar project you have some historical process to refer back to in the  Initiation process group.

Then, we wipe our hands of it. Operations takes over the running of the unique, shiny new thing that was built with the project, and we send our project team back into the wilds from whence they came (Mulcahey, PMP Exam Prep, 6th Edition, 43).

I think it’s this last 2 portions that I most dislike about the Closing process group. I always feel that the deliverable widgets don’t look all shiny and new, or like they’re half-formed, and giving them to Operations, they are going to not appreciate them.

Then, with the releasing of the team, it means that the PM (me) gets released too. Then, you are left with this impression that Ops didn’t like your results, and no one will ever assign you to a project again. And then Monday rolls around…

Executing Process Group

It’s late on a Sunday night, and I’m looking over the list of activities for the Executing Process Group (Mulcahy’s PMP Exam Prep 6th Edition, 43). Unlike with the Initiating and Planning process groups, there is no clear line of logic with these steps. Maybe because it’s late, or maybe because every project is different, and the execution takes a different path every time.

I have to say, I love the first task: ‘execute the work according to the PM plan’ (Mulcahy 43). Great. Thanks for that clarifying statement. Or the regular refrain from the guy who lead my first PM course, 2 years ago: “Plan the work, then work the plan!”

Like the rest of the groups, it’s fairly clear that the activities are lumped into categories. Actually, the categories coincide with the upcoming chapters. The first section is integration management, which entails integrating the work of the whole team into an outcome. This includes ‘executing the work according to the PM plan’. It also includes staying within the defined project scope.

The second section is quality management. Yes, some of this will come back to haunt us in the Monitoring and Controlling process group, but quality management needs to take place at the time of executing. Quality audits can occur. Processes can be performed, and improved. This will make the monitoring piece go a whole lot smoother.

Third is Human Resource management. People are doing the executing, so managing the worker-bees falls under the Executing stage. Evaluting their performance, praising them for a job welldone and incentivizing them to work harder. Working with them to identify issues and tracking them to avoid risks.

Finally, there is vendor management. Hey, if you have to manage the internal worker bees, you have to manage the folks at the outsourcing company who are managing their worker bees, right? Having just wrapped up a project that was 6 weeks late, in part because the vendor didn’t finish all of their work on time, I can attest that the vendor can be as critical as the internal staff.

Also, sprinkled throughout the list of steps are communications. Meetings, emails, status reports, risk assessments from weekly team meetings.

The short summary of this phase, which is proving incredibly hard to summarize, is that if a task involves producing anything that was already on the project plan, it’s in the execution process group. If it’s making sure the project is on time, on scope and on budget, it’s in the next process group: monitoring and controlling.


Planning Process Group

Last week, I started narratives for the process groups, based on the Rita Mulcahy chart of process group steps, by beginning with Initiating a project. The next process group is planning.

For this process group, Mulcahy insists that there is a set order to these steps. Down the line, I’m sure I’ll figure out the logic to why these are in a set order.

So, after the project is initiated, one begins planning, and in a totally cyclical fashion, one begins Planning by planning how to plan. Seriously. Once the plan for planning is in place, you can finalize the requirements and begin creating the project scope statement (Mulcahy 43).

I would like to take a moment to express my surprise that the project scope statement is here in planning and not in initiating. While the project charter document discusses what the project will be including and not including, I suppose you can’t finalize the scope statement until the requirements are finalized, which happens in planning. I could see strong arguments made for the scope being in the Initiating phase, but oh well.

Following the completion of the scope, and I would suppose, building off of the analysis of the existing systems from initiation, you determine what will need to be purchased. Since making the determination to purchase some aspects trims those pieces out of the in-house work, after you decide what’s being bought, you can determine who is on the team, in-house. If you’re outsourcing the weaving, then the staff weavers don’t need to be part of the project team, nor do the loom-setup staff.

Now that you have staff, you can plan what work to assign them, in the WBS (Work Breakdown Structure) (Mulcahy 43). The WBS is everyone’s favorite part, at least if you work in my company, since it’s the most readily accessible portion of MS Project. More (much, much more) on this later.

So, tasks broken out in the WBS, you can create an activities list, and string them along into a network diagram. With the work diagrammed out, you can estimate the resource requirements to assign to the work, estimate the time needed to complete the tasks, and with time linked to tasks, you can see which tasks take longer and which define the critical path (the series of interrelated steps that define the total timespan of the project). If you take the critical path of 25 weeks, add it to a start date of tomorrow, you get a completion date, which means you have a schedule! Schedule x overhead= estimated expenses=budget.

So, now we have a network diagram, a schedule, and a budget, we have to plan to stick to this set of guidelines, so we build some quality metrics and processes to measure them. I like to think that this part should be easy, but it seems to be easy to skip, in my opinion.

Looking through these steps of the planning Process Group, I can kinda see phases going on here. Phase 1: Planning the Planning (the anal-retentive part of this). Phase 2: Building the execution plan (WBS, activities list, schedule, budget) (the concrete part of this). Phase 3: The Monitoring of the plan. Phase 4: Documenting the planning. We’re in Phase 3 at this point.

Notice how these 4 phases mirror the Project Lifecycle? It’s like a crazy project fractal.

Anyway, on to phase 3 of this: so, we have the quality metrics portion of this down. Now, if we don’t adhere to the quality metrics, we need a process improvement plan. Then, knowing how we are going to measure things, and what activities we want to complete, we can assign roles and responsibilities. This must be, logically, more than just “Bob, you’re responsible for overseeing the loom pattern development” but also, “Bob, you are responsible for submitting the weekly loom pattern development audit checklist that was documented in the quality metrics plan.” Responsibilities are more than just concrete tasks to get done.

Now that Bob needs to get the audit checklist to the project group, we need to plan the method of communicating that. So, communication plan (to monitor the quality metrics which monitors the work). Makes sense, right?

And with a communication plan, a quality plan with process improvements, a schedule, a budget, an activities list, a critical path, a network diagram, a WBS, and a list of things that needs to be purchased, what could possibly go wrong? Everything on the risk list that you can now develop and start planning for, too.

And, as we plan for risks, we need to tweak the WBS to account for Bob’s potential quality audit findings that could delay loom setup, which could delay prototype production, etc, so we have to repeat some of the above steps. Until we’re happy, we need to repeat phases 1-3.

Now, for phase 4, which is really the same as the Project Closing process group, as we’ll see later: we finalize the plans (including procurement documents), gather all the documents together, and get signoff from the stakeholders, and we’re done. Oh, no, wait, we’re done planning. Now, finally, we can kick off the project and get underway.

Lessons learned notes

Lessons learned are a collection of things that went right, things that went wrong, and things that should be done differently. They can be collected at the end of each phase, and at the end of the project. (Mulcahy 32)

Lessons learned should include technical aspects of the project, tying them to reality. They should look at project management, including planning and risk prevention. And they should look at management, including communication. (Mulcahy 32) The documentation looks at the causes of the issues, the reasoning behind the corrective action (PMBOK 261).

Lessons learned should be shared throughout the organization, probably through a PMO, or whatever the existing structure for sharing this information is.

During the initiating phase, lessons learned from other projects should be reviewed as part of identifying risks. They should be certified during the Closing phase of the project, and stored.

I had identified back a few weeks ago that I would be conducting a lessons learned exercise for a CRM project I was working on. That exercise is finally scheduled for next week.  More to come.

Initiation process group

Happy International Project Managers Day! In honor of it, and because I’ve been very burned out at work, I took the day off. I made some progress reading into Chapter 3 of Mulcahy’s PMP Exam Prep, 6th edition.

The focus of this chapter is to review the project process groups and the activities in each one. The process groups are Initiating, Planning, Executing, Controlling and Monitoring, and Closing. In the book, she provides a table of all of the process groups, and the activities. I’m working on memorizing, or at least working out the overarching narrative of the project, for each one.

I’m writing out the steps in a spreadsheet that I can reach back to when necessary. I’m not going to post that here, because it’s fairly well copy-writed. What I will do is try to describe the process group’s narrative flow, so I can internalize it better.

Before a project gets into the initiating phase, the organization has already determined it’s strategies for what it wants to accomplish. It identifies a goal, and decides that to reach that goal, a project needs to be performed. A business case is developed for reaching the goal and documenting how that goal will further the organizational strategy.

Once the business case is finished, the project initiation can begin. The first step is to hiring a project manager. The project manager needs to first understand the culture of the organization and its structure, to determine how the project will be ultimately shaped. This goes back to the post about organizational structure (functional, matrixed, projectized). Coupled with this phase is also determining what the organization’s processes for projects are, and the history with similar projects  (Mulcahy 43).

Knowing this background information, the project manager can dig into the business case, viewing it from within the context of the organization. Sensing the scale of the business case, the project manager can also determine if the project will need to be divided into phases. When reading the business case, you can determine the initial requirements for the project and potential risks  (Mulcahy 43).

It’s important to note, that these requirements are still within the context of the organization’s strategies. So, instead of just focusing on ‘completing this system’, there are larger questions at stake, about other pieces of the strategy, including vendor selection, long-range plans that this system are a part of, etc. (Mulcahy 44).

From the requirements, measurable objectives become clear. These are the hows and whens of the project. No longer are we interested in ‘growing market share’, but in ‘growing market share by 20% through streamling Customer Relations’.

With measurable objectives come, a sense of the requirements, and an overview of the risks, a project charter can be built (Mulcahy 43). From the charter documents I’ve drafted, I can identify that the history of both this business case, and the company’s history with projects of this nature are included, as are 30,000 foot overviews of timelines and budgets. The business case may have identified these already. But, this charter is the first of the project documents.

And finally, there is the question of stakeholders. Mulcahy lists the identification of stakeholders, and developing a stakeholder management plan at the end of the phase, though she does identify that these steps don’t need to be in order (42-43). I disagree with keeping these at the end. Stakeholder identification is often included in the charter, based on the business case, and the initial requirements. Stakeholder buy-in can be critical for getting approval for the project charter, and for ensuring the project is properly supported and resourced. I would opt to include identifying stakeholders before completing the charter.

While she doesn’t identify it here, I would suggest that approval of the charter indicates the end to this phase.

Finally, this phase appears to be the most cut-and-dry, and the one that most seldom is returned to. I could be proven wrong, though.


Project Management Definitions

To begin studying for the exam, I am beginning with Chap 2, in Mulcahy’s PMP Exam Prep 6th Edition, which focuses on some of the ground concepts. I’ve thrown in additional info from the PMBOK 4th edition (specified below).

Definition of a Project-

  • Temporary
  • Has a beginning and an end
  • “creates a unique product, service or result.” ( pg 21)
  • “The end is reached when the project’s objectives have been achieved or when the project is terminated because its objectives will not or cannot be met, or when the need for the project no longer exists” (PMBOK pg 5)
  • “Can involve a single person, a single organizational unit, or multiple organizational units (PMBOK 5)
Definition of Operational work-
  • Ongoing, no clear beginning and end
  • Follows existing procedures (PMBOK 5)
Example: ‘can you figure out what is wrong with this broken process, and fix it?’ This is 2 projects- 1)figuring out what’s wrong (has a beginning and end) and 2) fixing it (has a beginning and end, but only after project 1 is complete).
34% of projects are successful, so a project needs to be finished on time, on budget, and within scope.
For the exam, questions focus on large projects, with “200 people on the team, last[ing] longer than one year, and [having] a value of $1,000,000” (pg. 22)
What is Project Management?
   5 Process groups:
  • Initiating
  • Planning
  • Executing
  • Monitoring and Controling
  • Closing
   Knowledge Areas (PMBOK 6)
  • Scope
  • Quality
  • Schedule
  • Budget
  • Resources (human and otherwise)
  • Risk
  Knowledge Areas (Mulcahy 22)
  • Project Management Framework
  • Project Management Processes and integration
  • Scope
  • Time
  • Cost
  • Quality
  • Human Resources
  • Communications
  • Risk
  • Procurement
Project Management, Program Management and Portfolios
  A project has a beginning and an end, and creates a unique product.
  A program is a collection or projects that are managed together to create value.
  A portfolio is a collection of programs and projects that are organized around a strategic business goal. (PMBOK 8-9)
An example from my work: the implementation of a new Medicaid plan is a project. The coordination of all new Medicaid expansions is a program. Government-funded insurance initiatives, as a whole (Medicaid, Medicare Advantage, Insurance Exchanges if we get there) make up a Portfolio.

The PMI Code of Ethics

I’m keeping this as a separate entry from the PMP Handbook entry for a couple of reasons:

  1. I want to be able to come back to reference this.
  2. I know that the Code of Ethics is on the test. The price of the exam is not.
  3. It’s probably important.
So, as part of being a PM, you have to adhere to a code of ethics. Not the end of the world. Looking it over, it’s actually kind of the standard stuff you would expect.
The purpose of [the] Code is to instill confidence in the project management profession and to help an individual become a better practitioner. We do this by establishing a profession-wide understanding of appropriate behavior. We believe that the credibility and reputation of the project management profession is shaped by the collective conduct of individual practitioners.
The code applies to PMI members [so me, for instance]. It also applies to applicants for PMI certification [theoretically not me, until I actually apply], PMI certification-holders [me soon], and PMI volunteers.
The core values: responsibility, respect, fairness and honesty
  • Responsibility
Aspire to take actions in best interest of society, public safety and the environment
and accept only assignment consistent with your background, experience, skills and qualifications.
     [The comment on these aspirations indicates we should notify project sponsors when the completion of a project requires us to exceed our qualifications. Notice how these are the aspirations?]
Aspire to fulfill commitments that we make; take ownership of errors and omissions to correct them promptly. We accept responsibility and consequences of errors and omissions.
Must uphold policies, rules, regulations and laws that govern our work activities. We must report unethical or illegal conduct to appropriate management. We bring violations of the code to the appropriate body.
  • Respect
We listen to other points of view. We approach people we disagree with. We conduct ourselves professionally. We negotiate in good faith. We do not exercise power of our position for personal gain. We are not abusive.
     [This seems to be the easier of the two to maintain so far.]
  • Fairness
Demonstrate transparency in our decision making process. Reexamine our impartiality. Provide equal access to information when allowed. We disclose potential conflicts of interest. We don’t participate in favoritism, nepotism or bribery.
    [Later, there is a discussion of the need for these codes to level the playing field across cultures. I suppose that’s reflected here.]
  • Honesty
Seek to understand the truth. Are truthful in our communications. Provide accurate information in a timely manner. Make commitments in good faith.
   [Maybe it’s just my upbringing, but this entire core value is embodied in the ‘Respect’ value. I suppose they felt it necessary to carve this out specifically. Remember that. It’ll be on the test.]
One last note on the Code of Conduct. In August of this year, the test was changed. There used to be a Code of Conduct section of the exam. Now, the Code of Conduct is embedded in all of the other sections. Guess I’ll need to pay attention to these things, then.
%d bloggers like this: