Sunday 25 February 2018

Project Management - Blog 3 - What is a Work Breakdown Structure (WBS)?





A Work Breakdown Structure (WBS) is a super tool as it presents a visualisation of the total scope of a project. It enables management to determine, prioritise important tasks, estimate efforts in order for the team to accomplish project goals and deliver the desired outcomes. According to The Project Management Body of Knowledge (PMBOK), a WBS ‘’is a hierarchical and incremental decomposition of the project into phases, deliverables and work packages’’ (Project Management Institute, 2018).  In a WBS, the deliverable is the end goal and it can be a thing, a service, or an activity, and that depend on our project.  



Elements 

Figure 1 Simple WBS Chart


There are many methods to partition or break down project work, the most popular is a form of visual demonstration of the project’s activities, phases, and deliverables in one single chart. The team determine project milestones, deliverables and break them further down into smaller components, called activities, required to complete the deliverable or milestone.

Typically, the WBS chart looks like a tree-structured diagram, but it can also be in the form of hierarchical tables or numbered lists. Regardless of the format, a WBS normally consist of Terminal elements (aka work packages), WBS coding and dictionary. Work packages are the lowest or smallest units of work. WBS coding includes outline numbering of WBS elements in decimal sequences to represent the sequential order of each level and activity. Finally, to complete the WBS, a related dictionary may be created. This will contain detailed information about each element of the project. The dictionary includes definitions of each work package, effort level, duration of tasks, and resources. A WBS dictionary is generally presented in a table or spreadsheet format.

Purpose
The primary goal of a WBS is to make a large project more manageable. It aids to transform project activities into less complicated tasks, so it is easier for the team to understand the scope of the project and work related. By breaking down activities into smaller chunks it means work can be done simultaneously by different team members, leading to better team productivity and overall easier project management.

Work Breakdown Structure analysis
A good way to identify the potential risks is to analyse our WBS. The team draws a diagram and questions each and every element, which eventually will give a valid list of potential risks for the project. As they are connected to the appropriate work packages this means the team will be in a better position to handle the risks.




References:

Practice Standard for Work Breakdown Structures (Second Edition), published by the Project Management InstituteISBN 1933890134, page 8


Images





Saturday 17 February 2018

Project Management - Blog 2 - The Project Definition Phase


Providing the Groundwork for Project Planning - The Project Definition

The second blog will primarily be about the phase, project definition. This will be section from the project management (PM) process that will enable the groundwork for the essential project planning. Some may say that a project has a defined end complete with a defined start and has a one-time set of activities. The Project management process is defined as the combination of knowledge, skills, techniques and tools applied together in order to meet the project requirements. There are five phases of the project management which are essentials on how to plan and accomplish project goals (Esposito, 2015).

5 Phases of Project Management

5 phases of project management



Phase 2: Project Definition & Planning

This phase plays a critical role in planning a project as it provides the roadmap for everyone to follow. This roadmap should assist in making the understanding of the project more durable. During this phase, a project plan and project scope, are defined. This definition is usually put in writing so the project management plan can be developed. The PM team will prioritize the project, identify costs, determine what resources are required, and establish a schedule in order to determine if the project in on track (Esposito, 2015).

At this stage or phase, all project team members will know their roles and what they’re accountable for in order to deliver a successful project. There is a number of documents this phase requires to create, such as:

Scope Statement -- a document outlining project’s needs, objectives, deliverables, identifying the constraints and key success factors.
WBS (Work Breakdown Schedule) – a key deliverable of visual representation of the team work divided into manageable sections.
Milestones – these are high-level goals that the team want to achieve which are represented in the Gantt Chart
Gannt Chart – provides a visual illustration of a project’s planning and scheduling of specific tasks.
Communication Plan – involves a plan for instant communication and proper messaging around the project. It is based on a deliverable and milestones.
Risk Management Plan – here we identify all foreseeable risks. Typical risks may consist of lack of finances, impossible time frames, slashing budgets, requirements forever changing or a shortfall of resources to name but a few.

All projects have risks, it is how the PM deal with the risks that will make a project stand out. Making sure they’re identified, early in the project planning is a must. Phase two provides help to PMs in identifying risks. This action aims to minimise the risk of a failure, costs associated with it, and avails to avoid unnecessary activities that reduces time and energy.

References:

Comprehensive Guide to the 5 Phases of Project Management . [Online] Available at: https://www.smartsheet.com/blog/demystifying-5-phases-project-management. [accessed 16 February 2018].

Sunday 4 February 2018

Project Management - Blog 1 - Why Do IT Projects Fail

My initial blog post for the module Project Management consists of analysing the article, "Gartner Survey Show Why Projects Fail" by Lars Mieritz where he discusses specifically why IT projects fail concentrating on the following categories sizes, small, medium and large. Each classification is determined as per the graphic below (Mieritz 2012). 



According to Mieritz, the fundamental reasons for projects with a budget greater than $350,000 flounder are due to uncontrolled budget costs and not tracking the budget throughout the duration of the project were small IT projects, like any project for that matter, are very much straight forward to manage and accomplish on time. Below is a table created showing the percentage rate of successful IT projects and failure rates for IT projects (Mieritz 2012).


Source: Gartner (June 2012)

So why do certain classifications fail? What are the primary reasons for these failures? Is it as simple as the graphic below, small IT projects are simple and large IT projects are complex, maybe there is other factors to take into consideration on why IT projects fail.





Small Projects
Small projects have a smaller time frame for completion, therefore this type of project could be rushed, hence having poor quality or cancelled after launch as they do not meet the standards of the shareholders. But why do smaller IT projects have a higher success rate over the other two types, their iteration process is quicker, estimations of the budget can be more accurate, more time for analysis of historical data from similar small projects.

Medium Projects
Successful project management offices (PMO) tend to keep projects small in order to keep a clear criteria in regards to limiting the project size to allow for quality assurance, planning, testing. Medium IT projects tend to be greater than 6 months, therefore communication could break down, keeping stakeholders within the iteration processes is harder over lengthy time periods, therefore delivering high quality medium and large projects could prove to be more difficult and cancelled after launch.

Large Projects
Due to larger IT projects and the difficulty in gaging how long the project will take to complete is highlighted in the article of substantially late projects, with a knock-on effect of cost deviation, hence why the failure rate for Large IT projects is the highest out of the three classifications.

Anything we do, any experience, whether it is a failure, mistake, or a success, is a learning curve for the project manager and team. It is up to the PMO on how to get there, where the project meets all criteria and becomes successful. Successful projects are the ones with a great overall planning, thinking out of the box to come up with better and/or new solutions. When we enjoy what we’re doing we also become more productive and effective, engaging better with the teams. Likewise, positive attitude, good communication and creative work also count for the project success (Almakajeva 2014). 

References:
Gartner Survey Shows Why Projects Fail | thisiswhatgoodlookslike. 2018 [Online] Available at: https://thisiswhatgoodlookslike.com/2012/06/10/gartner-survey-shows-why-projects-fail/. [accessed 01 February 2018].


10 reasons why projects fail or common mistakes to avoid. 2018 [Online] Available at: https://www.slideshare.net/MariannaAlmakaieva/10-reasons-why-projects-fail-or-common-mistakes-to-avoid. [accessed 02 February 2018].



Project Management - Blog 7 - Organisational Structure

Project Management Structure Figure 1  Typical Project Organisation Chart An organisation with an excellent CEO, super h...