Search This Blog:

Thursday, April 8, 2010

Lesson 14: The Work Breakdown Stucture (WBS)

Building on the previous lessons and taking the case study as departure point it is possible to move further and do detailed scoping for the project. Although the exercises in the previous lessons did not require full development of the Project Charter, let us assume that we have been able to define the final deliverable and high level deliverable's of our aircraft assembly project as follows:

Final deliverable:

Assembled Airbus, ready for its first airworthy inspection prior to first test flight (from here on we will just refer to this deliverable as - "Assembled Airbus")

High Level Deliverable's:

To keep it very high level and not complicate our case study, our high level deliverable s will be very general. However, remember that the high level deliverable should be such that it produces the final deliverable:

  • Assembly plant secured
  • Workforce appointments completed
  • Component delivery check-in completed
  • Sub-component assembly completed
  • Interior fitted
  • Final assembly completed
  • Handover of aircraft completed

With the above clarified (albeit at a very high and general level) the next phase of the project can be embarked upon. In this next phase (the Planning Phase of the project) one of the first tasks would be to define the scope of work. This is achieved by developing a Work Breakdown Structure (WBS).

Per definition the WBS has two main elements:

  • A hierarchical outline (map) that identifies the products (deliverable's) and work elements involved in the project
  • This map defines the relationship of the final deliverable to its sub deliverables' and in turn, their relationships to work packages (collection of elements related to work that must be done)

Wednesday, April 7, 2010

Lesson 13: Quiz For Charter Case Study


Lesson 12: Charter Case Study

In order to exercise our skills in defining the project let's use a practical case study (admittedly a bit superficial, but done for the purposes of teaching). Embedded in this BLOG is a time lapsed video that provides an overview of how an Airbus A380 gets assembled. Let us further assume that we are the team responsible for the assembly, but only the assembly. To make sure it is a project, also regard this as the first prototype that will be tested. Doing this at a very, very high level (after all few of us are aeronautical engineers) the client put the following conditions to our involvement:

  • We are only responsible for assembly  and  branding (major components - fuselage; wings; landing gear; navigation equipment, interior and painting)
  • We are assemblers not engineers, definitely not design engineers
  • The assembly plant will be provided, but not the support staff, who you need to appoint and manage them
  • Final quality check prior to first test flight will be done by external contractor


Now watch the video and move on to the next lesson and answer the multiple choice questions.



Lesson 11: The Project Charter



This BLOG essentially starts the skills building part of this whole series. From this point onwards focus will be on developing skills to master the techniques required to complete each phase of the project cycle. As such this first BLOG in the series deals with the initiation phase and provides a detailed overview of what elements the Project Charter will address. Reflect back on Lesson 9, where the project phases were discussed. In this regard it was highlighted that the Initiation Phase is where the project is defined, the main tangible output being the Project Charter. Let's look at how the detail of the project Charter enables clarification and definition of the core elements of the project:


STRUCTURE OF THE PROJECT CHARTER (DOWNLOAD TEMPLATE HERE)

Lesson 10: Organizational Context

This BLOG provides answers to three important questions related to projects and project management. The first is where do projects typically originate? The second, who are the key role players and the third how does the organizational culture influence project outcomes? The paragraphs that follow provide more detail in this regard:

Where do projects originate?

The question, where projects originate is important in that it provides insight into what should be regarded project work and what not. This is best illustrated through and example. Consider the management team of a company that manufactures mid-sized vehicles for the urban commuter. Further assume that this company do their annual strategic planning and realize that they will have to contribute to reducing carbon emissions. Based on this they decide to investigate ways to adjust their production processes to accommodate the new strategy. Thus, a new initiative is born, while at the same time the normal production work continues. However this broad strategy is not a project yet . An optimal solution needs to be found, feasibility tested etc, prior to this. The important point however is that in most cases projects originate from new strategies initiated by top management . Further, that prior to launching a specific project the new initiative needs to be prioritized, and potential solutions need to be investigated. It is here where research is done, and feasibility of the potential solutions modeled. Once an optimal solution is found the project moves into the cycle to produce the final deliverable

Key Role Players (Stakeholders)

In the previous lessons the importance of managing expectations were mentioned. It needs to be realized that, for stakeholders to have a clear sense of what the benefits will be from producing the final deliverable, they need to be kept "in the loop" .This also implies they need to be identified as soon as possible. While authors differ about the exact definition of what a stakeholder is, it is useful to identify those role players who have an interest ('stake') in the project and can influence its outcome. The main stakeholders in this regard include the following:

  • Project Manager - the individual responsible for managing project work
  • Customer/User/Beneficiary - the individuals, group or organization who will use the product or benefit from the solution
  • Sponsor - the individual or group who represent those who provide finance and also "owns" the business case
  • Performing Organization - the individuals, groups and organizations who would probably be involved in the planning and execution of the project as well as ongoing maintenance following delivery
Organization Culture

It should always be remembered that projects are not planned and implemented in a vacuum. The culture of the organization is a strong force that needs to be navigated to ensure that the final deliverable is produced. Per definition the organization culture is a set of assumptions (learn t over time) upon which organization behavior is based. While culture is difficult to identify it is also true that it affects everything that happens in an organization. In terms of this think about the "artifacts" like the building, what the boardroom looks like, etc. What does is say about "the way we do things here"? It is this way things are done, that needs to be taken into account and the only way to negotiate through this and deliver is to ensure that you keep control of the Iron triangle and manage expectations effectively.

Tuesday, April 6, 2010

Lesson 9: The Project Cycle In More Detail

While Lesson's 1 to 6 provided an overview of the basic definitions and core concepts related to project management this BLOG provides insight into the core techniques that need to be mastered in each phase of the project cycle. This BLOG also answers the question - from a management perspective, what do we do in each phase of the project cycle? he paragraphs that follow highlight this in more detail:

Initiation Phase:

In the initiation phase the main task is to define the project. The aim is to ensure that we have the basis for what needs to be done in the other phases of the project cycle. The tangible output of this phase is the so called project charter. It is the charter that, once approved, provides a mandate to officially start - thus, following approval of the charter we have a project...

The outputs of this phase include the charter, clarity about the problem, the final and high level deliverable s as well as other aspects that forms part of the basic definition of the project - important in this regard to identify the key stakeholders as early as possible

Planning Phase:

The bulk of the work of scoping out the project, sequencing, scheduling and budgeting takes place in this phase of the project. There are also very specific techniques that need to be mastered here, notably how to create a work breakdown structure (WBS), a network logical diagram, calculate a critical path (CPM) , as well as developing the schedule bar chart and budget.

The main outputs of this phase are clarity about the technical/functional specification (albeit not strictly a project management output), the scope of work (in the form of the work breakdown structure, the network logic diagram, the schedule bar chart and the budget.

Implementation Phase:

In the implementation phase the project manager essentially drives execution, manage changes to the scope (change control), and make sure that the expectations of the stakeholders are aligned with the benefits the final deliverable will produce. Remember your success as project manager depends on your ability to manage expectations!

The main outputs of this phase include:

  • Tracking status - this includes tracking the schedule, managing action items (actions too small for the schedule but often gets scheduled items done) and issues (problems that could escalate)
  • Reporting status - this includes reporting on the above but also providing evaluations/interpretations to the client and recommending strategies and actions
  • Driving execution - this includes keeping an active pulse on the status, making status visible, taking corrective action and keeping the customer "in the loop" (the last forms a huge part of expectations management)
Close Out Phase:

The close out phase is where the project team makes sure that an independent audit is conducted, the client system is capable to sustain the benefits derived by the final deliverable, debriefing, project accounting and redeployment of team members are done. The main outputs here would be the final payments, commissioning, and a close out report signed off by major stakeholders

Lesson 8: Flashcard Review