Basic Management Skills
Basic Management Skills
Basic Management Skills
Delegation
Having planned everything that lies ahead and having come up with a plan for time
management, you may feel that you have got more than you could chew on your
plate. This is where delegation should come into play.
Becoming a good manager does not mean carrying out every task by him/herself.
Rather, it is about being able to delegate work effectively in order to complete the
task on time.
Many managers mishandle delegation either because they do not have enough
confidence in their co-workers and subordinates or because they do not master the
techniques of delegation.
Therefore, the key for delegation would be to identify the individuals that are
capable of carrying out the task, delegating the work with accurate instructions and
providing enough moral support. Once the task is complete, you will get an
opportunity to evaluate their performance and provide constructive feedback.
Communication Skills
Nothing could be ever accomplished in the world of a manager without him or her
being able to accurately, precisely and positively communicate their instructions,
suggestions or feedback to others.
Therefore, you should be extremely careful in picking out your words. A 'Can-Do'
attitude is something that can be easily portrayed through your words.
When your communication bears a positive note, it will run across your audience
almost contagiously.
Conclusion
Managing people and processes is a style in itself that requires dedication and
experience-blended practice. The skills needed are as vast and deep as the ocean.
The basic management skills presented herein is only a doorway for you to get
started on the management path that lies ahead.
1 - Time
A project's activities can either take shorter or longer amount of time to complete.
Completion of tasks depends on a number of factors such as the number of people
working on the project, experience, skills, etc.
Time is a crucial factor which is uncontrollable. On the other hand, failure to meet
the deadlines in a project can create adverse effects. Most often, the main reason
for organizations to fail in terms of time is due to lack of resources.
2 - Cost
It's imperative for both the project manager and the organization to have an
estimated cost when undertaking a project. Budgets will ensure that project is
developed or implemented below a certain cost.
Sometimes, project managers have to allocate additional resources in order to meet
the deadlines with a penalty of additional project costs.
3 - Scope
Scope looks at the outcome of the project undertaken. This consists of a list of
deliverables, which need to be addressed by the project team.
A successful project manager will know to manage both the scope of the project
and any change in scope which impacts time and cost.
Quality
Quality is not a part of the project management triangle, but it is the ultimate
objective of every delivery. Hence, the project management triangle represents
implies quality.
Many project managers are under the notion that 'high quality comes with high cost',
which to some extent is true. By using low quality resources to accomplish project
deadlines does not ensure success of the overall project.
Like with the scope, quality will also be an important deliverable for the project.
Conclusion
Project management is very often represented on a triangle. A successful project
manager needs to keep a balance between the triple constraints so that the quality
of the project or outcome is not compromised.
There are many tools and techniques that are available in order to face the
challenges related to the three constraints. A good project manager will use
appropriate tools in order to execute the project successfully.
The reputation of your organization would depend on the quality of the delivery of
your projects. This is another factor you should not lose sight of throughout the
project.
Your role would also be to keep reminding the team members that quality is key.
(3) No Budget Overrun
No project can be started off without the preparation of the budget. Although this is
just a forecast of the costs that would be incurred, it is essential that this budget is
prepared after careful research and comparing prices to get the best.
You would need to consider ways of cutting costs while also ensuring that you meet
the needs of the client as well as meeting the standards expected of your
organization.
This budget must include all costs with regard equipment, labor and everything else.
You then need to try and always stick to the budget, although it's always best to
leave some allowance for a few 100 dollars for any additional expenses that may
arise.
(4) Requirements Coverage
Another goal of a project manager involves meeting all requirements of the client.
You would need to therefore have all specifications at hand and go through them
every once in a while to ensure that you are on track.
If there is confusion as to any requirements, it would be best for you to get them
cleared at the very beginning.
(5) Team Management
While you would have to ensure that all aspects of the project are maintained, you
are also responsible as project manager for the happiness of your team.
You need to keep in mind that it is the incentives and encouragement provided to
them that will make them work harder and want to complete the work on time,
thereby helping you reach your goals.
If the team members are unhappy with the way things are being carried out,
productivity will also in turn decrease, pulling you further away from achieving your
goals. It is essential therefore to always maintain a warm friendly relationship with
them.
The communication within the team should be very effective. They should be willing
to voice out their opinions while you listen to their suggestions and consider
including them in the project.
This is after all a team effort. Your goals with regard to the project are also their
goals.
Conclusion
The role of a project manager is therefore no easy task. It involves taking up a lot of
responsibility as each of the goals of the project must be met without making too
many sacrifices.
If these goals are outlined to the project management team at the very beginning,
there in no way for the delivery of the goals to be delayed in any way as everyone
will always be aware of what they need to achieve and by when.
Project Charter
Introduction
Project Charter refers to a statement of objectives in a project. This statement also
sets out detailed project goals, roles and responsibilities, identifies the main
stakeholders, and the level of authority of a project manager.
It acts as a guideline for future projects as well as an important material in the
organization's knowledge management system.
The project charter is a short document that would consist of new offering request
or a request for proposal. This document is a part of the project management
process, which is required by Initiative for Policy Dialogue (IPD) and Customer
Relationship Management (CRM).
Business Case
This outlines the need for a project charter to take place. A business case should
set out the benefits gained from carrying out a project charter. Benefits need not
only be in terms of finance such as revenue, cost reduction, etc., but also the
benefit that the customer receives.
Following are the characteristics of a good business case:
The reasons of undertaking the project.
The benefits gained from undertaking the project now.
The consequences of not doing the project.
The factors that would conclude that it fits the business goals.
Project Scope
As the name denotes, it refers to the scope that the project will give the business if
they undertake the project.
Before doing a project, the following concerns need to be addressed:
The within scope and out of scope needs to be considered.
The process that each team will focus upon.
The start and end points for a process.
Availability of resources.
Constraints under which the team will work.
Time limitations.
The impact on the normal workload if the project is to be undertaken.
Conclusion
The project charter is not only a tool that is used for planning projects but also a
communication mechanism that acts as a reference. A well-planned project with an
effective communication plan will definitely bring in success for the project
undertaken at hand.
Therefore, the Project Charter should be one of the frequently referred documents
in a project and the entire project team needs to be aware of the content of the
Project Charter. This is a key element for a successful project.
Introduction
Project management is one of the critical processes of any project. This is due to
the fact that project management is the core process that connects all other project
activities and processes together.
When it comes to the activities of project management, there are plenty. However,
these plenty of project management activities can be categorized into five main
processes.
Let's have a look at the five main project management processes in detail.
1 - Project Initiation
Project initiation is the starting point of any project. In this process, all the activities
related to winning a project takes place. Usually, the main activity of this phase is
the pre-sale.
During the pre-sale period, the service provider proves the eligibility and ability of
completing the project to the client and eventually wins the business. Then, it is the
detailed requirements gathering which comes next.
During the requirements gathering activity, all the client requirements are gathered
and analysed for implementation. In this activity, negotiations may take place to
change certain requirements or remove certain requirements altogether.
Usually, project initiation process ends with requirements sign-off.
2 - Project Planning
Project planning is one of the main project management processes. If the project
management team gets this step wrong, there could be heavy negative
consequences during the next phases of the project.
Therefore, the project management team will have to pay detailed attention to this
process of the project.
In this process, the project plan is derived in order to address the project
requirements such as, requirements scope, budget and timelines. Once the project
plan is derived, then the project schedule is developed.
Depending on the budget and the schedule, the resources are then allocated to the
project. This phase is the most important phase when it comes to project cost and
effort.
3 - Project Execution
After all paperwork is done, in this phase, the project management executes the
project in order to achieve project objectives.
When it comes to execution, each member of the team carries out their own
assignments within the given deadline for each activity. The detailed project
schedule will be used for tracking the project progress.
During the project execution, there are many reporting activities to be done. The
senior management of the company will require daily or weekly status updates on
the project progress.
In addition to that, the client may also want to track the progress of the project.
During the project execution, it is a must to track the effort and cost of the project in
order to determine whether the project is progressing in the right direction or not.
In addition to reporting, there are multiple deliveries to be made during the project
execution. Usually, project deliveries are not onetime deliveries made at the end of
the project. Instead, the deliveries are scattered through out the project execution
period and delivered upon agreed timelines.
In such cases, the project is not a 100% success to the service provider. Therefore,
such instances should be studied carefully and should take necessary actions to
avoid in the future.
Conclusion
Project management is a responsible process. The project management process
connects all other project activities together and creates the harmony in the project.
Therefore, the project management team should have a detailed understanding on
all the project management processes and the tools that they can make use for
each project management process.
Is It an Overhead?
Some traditional organizations view the project management office as an overhead.
This is mainly due to the fact that the organization is small enough where there is no
explicit need for a project management office.
Conclusion
Project management office is one of the entities that will add value to large
organizations in the long run. A project management office could be an overhead for
smaller scale organizations and such establishment may end up as a failure.
A successful project management office can enhance the productivity of the project
teams and cause a lot of cost savings. In addition to that, it can make the
organization a more matured and capable entity.
Organizational Structures
Introduction
Any operating organization should have its own structure in order to operate
efficiently. For an organization, the organizational structure is a hierarchy of people
and its functions.
The organizational structure of an organization tells you the character of an
organization and the values it believes in. Therefore, when you do business with an
organization or getting into a new job in an organization, it is always a great idea to
get to know and understand their organizational structure.
Depending on the organizational values and the nature of the business,
organizations tend to adopt one of the following structures for management
purposes.
Although the organization follows a particular structure, there can be departments
and teams following some other organizational structure in exceptional cases.
Sometimes, some organizations may follow a combination of the following
organizational structures as well.
Bureaucratic Structures
Functional Structure
The organization is divided into segments based on the functions when managing.
This allows the organization to enhance the efficiencies of these functional groups.
As an example, take a software company.
Software engineers will only staff the entire software development department. This
way, management of this functional group becomes easy and effective.
Functional structures appear to be successful in large organization that produces
high volumes of products at low costs. The low cost can be achieved by such
companies due to the efficiencies within functional groups.
In addition to such advantages, there can be disadvantage from an organizational
perspective if the communication between the functional groups is not effective. In
this case, organization may find it difficult to achieve some organizational objectives
at the end.
Divisional Structure
Matrix Structure
When it comes to matrix structure, the organization places the employees based on
the function and the product.
The matrix structure gives the best of the both worlds of functional and divisional
structures.
In this type of an organization, the company uses teams to complete tasks. The
teams are formed based on the functions they belong to (ex: software engineers)
and product they are involved in (ex: Project A).
This way, there are many teams in this organization such as software engineers of
project A, software engineers of project B, QA engineers of project A, etc.
Conclusion
Every organization needs a structure in order to operate systematically. The
organizational structures can be used by any organization if the structure fits into
the nature and the maturity of the organization.
In most cases, organizations evolve through structures when they progress through
and enhance their processes and manpower. One company may start as a pre-
bureaucratic company and may evolve up to a matrix organization.
Management Styles
Introduction
In an organization, managers perform many functions and play many roles. They
are responsible for handling many situations and these situations are usually
different from one another.
When it comes to handling such situations, managers use their own management
styles.
Some management styles may be best for the situation and some may not be.
Therefore, awareness on different types of management styles will help the
managers to handle different situations the optimal way.
In short, a management style is a leadership method used by a manager. Let's have
a look at four main management styles practised by managers all over the world.
Autocratic
In this management style, the manager becomes the sole decision maker.
The manager does not care about the subordinates and their involvement in
decision making. Therefore, the decisions reflect the personality and the opinion of
the manager.
The decision does not reflect the team's collective opinion. In some cases, this style
of management can move a business towards its goals rapidly and can fight
through a challenging time.
If the manager has a great personality, experience and exposure, the decisions
made by him or her could be better than collective decision making. On the other
hand, subordinates may become dependent upon the manager's decisions and may
require thorough supervision.
There are two types of autocratic managers:
Directive autocrat. This type of managers make their decisions alone and supervise the
subordinates closely.
Permissive autocrat. This type of managers make their decisions alone, but allows
subordinates to freely execute the decisions.
Democratic
In this style, the manager is open to other's opinions and welcome their contribution
into the decision making process. Therefore, every decision is made with the
majority's agreement.
The decisions made reflect the team's opinion. For this management style to work
successfully, robust communication between the managers and the subordinates is
a must.
Paternalistic
This is one of the dictatorial types of management. The decisions made are usually
for the best interest of the company as well as the employees.
When the management makes a decision, it is explained to the employees and
obtains their support as well.
In this management style, work-life balance is emphasized and it eventually
maintains a high morale within the organization. In the long run, this guarantees the
loyalty of the employees.
One disadvantage of this style is that the employees may become dependent on the
managers. This will limit the creativity within the organization.
Laissez-faire
In this type of management, the manager is a facilitator for the staff. The employees
take the responsibility of different areas of their work. Whenever the employees face
an obstacle, the manager intervenes and removes it. In this style, the employee is
more independent and owns his or her responsibilities. The manager has only a
little managerial tasks to perform.
When compared with other styles, a minimum communication takes place in this
management style between the employees and the managers.
This style of management is the best suited for companies such as technology
companies where there are highly professional and creative employees.
Conclusion
Different management styles are capable of handling different situations and solving
different problems.
Therefore, a manager should be a dynamic person, who has insight into many types
of management styles.
Communications Management
Introduction
Often you would come across organizations that stress the importance of good
communication management. It's empirical for an organization to have a proper
communication management.
Once this is achieved, the organization is one step closer to achieving its overall
business objectives. Communication management refers to a systematic plan,
which implements and monitors the channels and content of communication.
To become a good manager, one must have a contingency approach at hand when
it comes to communicating with employees.
An effective communication management is considered to be a lifeline for many
projects that an organization undertakes as well as any department of the
organization.
Methods of Communication
Understanding the communication process alone will not guarantee success for
managers or an organization. Managers need to be aware of the methods used in
the communication process.
The standard methods of communication that are widely used by managers and
organizations across the world are either written or oral methods.
Apart from these two mechanisms, non-verbal communication is another prominent
method used to assess communication within the organization.
Non-verbal communication refers to the use of body language as a method of
communication. This method will include gestures, actions, physical appearance as
well as facial appearance and attitude.
Although most of these methods are still in use for a larger part of the organization,
the usage of e-mail and other electronic mediums as a method of communication
has lessened the need for face-to-face communication.
This sometimes leads to situations where both parties involved do not trust or feel
comfortable with each other and also the messages can be easily misinterpreted.
There are two aspects of oral communication, active listening and constructive
feedback.
Active Listening
This is where the person, who receives the message pays attention to the
information, interprets and remembers.
As you would be aware, listening helps you to pay attention and following are some
points, which illustrate active listening.
Making eye contact with the relevant party
Making sure to clarify questions if it's not clear
Avoiding using gestures, which are distracting or uncomfortable
Constructive Feedback
This is where managers fail most of the time. Feedback needs to be constructive
and then it will help the employees to shape up their performance instead of mere
criticism.
Conclusion
Communication management is vital for any organization irrespective of its size. It
contributes to achieving the company's overall objectives as well as creates a
positive and friendly environment.
An effective communication process within the organization will lead to an increase
in profits, high employee satisfaction and brand recognition.
Risk Identification
Managers face many difficulties when it comes to identifying and naming the risks
that occur when undertaking projects. These risks could be resolved through
structured or unstructured brainstorming or strategies. It's important to understand
that risks pertaining to the project can only be handled by the project manager and
other stakeholders of the project.
Risks, such as operational or business risks will be handled by the relevant teams.
The risks that often impact a project are supplier risk, resource risk and budget risk.
Supplier risk would refer to risks that can occur in case the supplier is not meeting
the timeline to supply the resources required.
Resource risk occurs when the human resource used in the project is not enough or
not skilled enough. Budget risk would refer to risks that can occur if the costs are
more than what was budgeted.
Risk Quantification
Risks can be evaluated based on quantity. Project managers need to analyze the
likely chances of a risk occurring with the help of a matrix.
Using the matrix, the project manager can categorize the risk into four categories as
Low, Medium, High and Critical. The probability of occurrence and the impact on the
project are the two parameters used for placing the risk in the matrix categories. As
an example, if a risk occurrence is low (probability = 2) and it has the highest impact
(impact = 4), the risk can be categorized as 'High'.
Risk Response
When it comes to risk management, it depends on the project manager to choose
strategies that will reduce the risk to minimal. Project managers can choose
between the four risk response strategies, which are outlined below.
Risks can be avoided
Pass on the risk
Take corrective measures to reduce the impact of risks
Acknowledge the risk
Risk Register
Often project managers will compile a document, which outlines the risks involved
and the strategies in place. This document is vital as it provides a huge deal of
information.
Risk register will often consist of diagrams to aid the reader as to the types of risks
that are dealt by the organization and the course of action taken. The risk register
should be freely accessible for all the members of the project team.
Conclusion
An organization will not be able to fully eliminate or eradicate risks. Every project
engagement will have its own set of risks to be dealt with. A certain degree of risk
will be involved when undertaking a project.
The risk management process should not be compromised at any point, if ignored
can lead to detrimental effects. The entire management team of the organization
should be aware of the project risk management methodologies and techniques.
Enhanced education and frequent risk assessments are the best way to minimize
the damage from risks.
For this step, there are many estimation mechanisms in place, so your project
should select an appropriate one.
Most of the companies follow either WBS based estimating or Function Points
based estimates in this step.
Once the activity estimates are completed, critical path of the project should be
identified in order to determine the total project duration. This is one of the key
inputs for the project time management.
5. Development of the Schedule
In order to create an accurate schedule, a few parameters from the previous steps
are required.
Activity sequence, duration of each activity and the resource
requirements/allocation for each activity is the most important factors.
In case if you perform this step manually, you may end up wasting a lot of valuable
project planning time. There are many software packages, such as Microsoft
Project, that will assist you to develop reliable and accurate project schedule.
As part of the schedule, you will develop a Gantt chart in order to visually monitor
the activities and the milestones.
6. Schedule Control
No project in the practical world can be executed without changes to the original
schedule. Therefore, it is essential for you to update your project schedule with
ongoing changes.
Conclusion
Time management is a key responsibility of a project manager. The project
manager should equip with a strong skill and sense for time management.
There are a number of time management techniques that have been integrated into
the management theories and best practices.
As an example, Agile/Scrum project management style has its own techniques for
time management.
In addition, if you are keen on learning time management into greater depths, you
can always get into a training course of one of the reputed and respected time
management trainers.
The Origin
The origin of the TQM goes back to the time of the First World War. During the
World War I, there have been a number of quality assurance initiatives taken place
due to the large-scale manufacturing required for war efforts.
The military fronts could not afford poor quality products and suffered heavy losses
due to the poor quality. Therefore, different stakeholders of the war initiated efforts
to enhance the manufacturing quality.
First of all, quality inspectors were introduced to the assembly lines in order to
inspect the quality. Products below certain quality standard were sent back for
fixing.
Even after World War I ended, the practice of using quality inspectors continued in
manufacturing plants. By this time, quality inspectors had more time in their hands
to perform their job.
Therefore, they came up with different ideas of assuring the quality. These efforts
led to the origin of Statistical Quality Control (SQC). Sampling was used in this
method for quality control.
As a result, quality assurance and quality control cost reduced, as inspection of
every production item was need in this approach.
During the post-World War II era, Japanese manufacturers produced poor quality
products. As a result of this, Japanese government invited Dr. Deming to train
Japanese engineers in quality assurance processes.
By 1950, quality control and quality assurance were core components of Japanese
manufacturing processes and employees of all levels within the company adopted
these quality processes.
By 1970s, the idea of total quality started surfacing. In this approach, all the
employees (from CEO to the lowest level) were supposed to take responsibility of
implementing quality processes for their respective work areas.
In addition, it was their responsibility to quality control, their own work.
The Cost
Some companies are under the impression that the cost of TQM is higher than the
benefits it offers. This might be true for the companies in small scale, trying to do
everything that comes under TQM.
According to a number of industrial researches, the total cost of poor quality for a
company always exceeds the cost of implementing TQM.
In addition, there is a hidden cost for the companies with poor quality products such
as handling customer complaints, re-shipping, and the overall brand name damage.
Conclusion
Total Quality Management is practiced by many business organizations around the
world. It is a proven method for implementing a quality conscious culture across all
the vertical and horizontal layers of the company.
Although there are many benefits, one should take the cost into the account when
implementing TQM.
For small-scale companies, the cost could be higher than the short and mid term
benefits.
Procurement Management
Introduction
Today, different organizations employ various management techniques to carry out
the efficient functioning of their departments. Procurement management is one such
form of management, where goods and services are acquired from a different
organization or firm.
All organizations deal with this form of management at some point in the life of their
businesses. It is in the way the procurement is carried out and the planning of the
process that will ensure the things run smoothly.
But with many other management techniques in use, is there any special reason to
use this particular form of management to acquire goods and services? Yes, this is
one of the frequent questions asked regarding procurement management.
Procurement management is known to help an organization to save much of the
money spent when purchasing goods and services from outside. It also has several
other advantages.
Always remember that it is of utmost importance to maintain a good relationship with the
supplier. This includes coming up with an agreement that both would find satisfactory.
This helps the sustainability of your business as well as the supplier's business.
These four simple steps would help you acquire your goods easily and quickly
without much hassle, but always requires careful consideration at each stage.
Conclusion
It should be kept in mind, however, that this procurement management system must
run efficiently and smoothly for all benefits to be reaped. The key to this would
therefore be an efficient system as well as the right supplier and resources.
For the purpose of procurement management, there should be a team of highly
trained individuals, if procurement management plays a key role.
As an example, a hospital should have a dedicated procurement team and should
employ strong procurement management techniques and tools.
Stakeholder Management
Introduction
When working on a project, there are many people or organizations that are
dependent on and/or are affected by the final product or output. These people are
the stakeholders of a project.
Stakeholder management involves taking into consideration the different interests
and values stakeholders have and addressing them during the duration of the
project to ensure that all stakeholders are happy at the end.
This branch of management is important because it helps an organization to
achieve its strategic objectives by involving both the external and internal
environments and by creating a positive relationship with stakeholders through good
management of their expectations.
Stakeholder management is also important because it helps identify positive
existing relationships with stakeholders. These relationships can be converted to
coalitions and partnerships, which go on to build trust and encourage collaboration
among the stakeholders.
Conclusion
In conclusion, in order to achieve an outcome from the projects, good stakeholder
management practices are required. Stakeholder management is the effective
management of all participants in a project, be it external or internal contributors.
Arguably, the most important element in stakeholder management is
communication where a manager has to spend his 99% time in doing meetings,
checking and replying e-mails and updating and distributing reports, etc.
Construction of a WBS
Identifying the main deliverables of a project is the starting point for deriving a work
breakdown structure.
This important step is usually done by the project managers and the subject matter
experts (SMEs) involved in the project. Once this step is completed, the subject
matter experts start breaking down the high-level tasks into smaller chunks of work.
In the process of breaking down the tasks, one can break them down into different
levels of detail. One can detail a high-level task into ten sub-tasks while another can
detail the same high-level task into 20 sub-tasks.
Therefore, there is no hard and fast rule on how you should breakdown a task in
WBS. Rather, the level of breakdown is a matter of the project type and the
management style followed for the project.
In general, there are a few "rules" used for determining the smallest task chunk. In
"two weeks" rule, nothing is broken down smaller than two weeks worth of work.
This means, the smallest task of the WBS is at least two-week long. 8/80 is another
rule used when creating a WBS. This rule implies that no task should be smaller
than 8 hours of work and should not be larger than 80 hours of work.
One can use many forms to display their WBS. Some use tree structure to illustrate
the WBS, while others use lists and tables. Outlining is one of the easiest ways of
representing a WBS.
There are many design goals for WBS. Some important goals are as follows:
Giving visibility to important work efforts.
Giving visibility to risky work efforts.
Illustrate the correlation between the activities and deliverables.
Show clear ownership by task leaders.
WBS Diagram
In a WBS diagram, the project scope is graphically expressed. Usually the diagram
starts with a graphic object or a box at the top, which represents the entire project.
Then, there are sub-components under the box.
These boxes represent the deliverables of the project. Under each deliverable,
there are sub-elements listed. These sub-elements are the activities that should be
performed in order to achieve the deliverables.
Although most of the WBS diagrams are designed based on the deliveries, some
WBS are created based on the project phases. Usually, information technology
projects are perfectly fit into WBS model.
Therefore, almost all information technology projects make use of WBS.
In addition to the general use of WBS, there is specific objective for deriving a WBS
as well. WBS is the input for Gantt charts, a tool that is used for project
management purpose.
Gantt chart is used for tracking the progression of the tasks derived by WBS.
Following is a sample WBS diagram:
Conclusion
The efficiency of a work breakdown structure can determine the success of a
project.
The WBS provides the foundation for all project management work, including,
planning, cost and effort estimation, resource allocation, and scheduling.
Therefore, one should take creating WBS as a critical step in the process of project
management.
In case if the project management needs to accelerate the project, the times for
critical path activities should be reduced.
Step 6: Critical path diagram to show project progresses
Critical path diagram is a live artefact. Therefore, this diagram should be updated
with actual values once the task is completed.
This gives more realistic figure for the deadline and the project management can
know whether they are on track regarding the deliverables.
Conclusion
Critical path identification is required for any project-planning phase. This gives the
project management the correct completion date of the overall project and the
flexibility to float activities.
A critical path diagram should be constantly updated with actual information when
the project progresses in order to refine the activity length/project duration
predictions.
Resource Leveling
Introduction
Resource leveling is a technique in project management that overlooks resource
allocation and resolves possible conflict arising from over-allocation. When project
managers undertake a project, they need to plan their resources accordingly.
This will benefit the organization without having to face conflicts and not being able
to deliver on time. Resource leveling is considered one of the key elements to
resource management in the organization.
An organization starts to face problems if resources are not allocated properly i.e.,
some resource may be over-allocated whilst others will be under-allocated. Both will
bring about a financial risk to the organization.
Stage
Phase
Task/Deliverable
All of the above-mentioned layers will determine the scope of the project and find
ways to organize tasks across the team. This will make it easier for the project team
to complete the tasks.
In addition, depending on the three parameters above, the level of the resources
required (seniority, experience, skills, etc.) may be different. Therefore, the resource
requirement for a project is always a variable, which is corresponding to the above
structure.
Establishing Dependencies
The main reason for a project manager to establish dependencies is to ensure that
tasks get executed properly. By identifying correct dependencies from that of
incorrect dependencies allows the project to be completed within the set timeframe.
Here are some of the constraints that a project manager will come across during the
project execution cycle. The constraints a project manager will face can be
categorized into three categories.
Mandatory - These constraints arise due to physical limitations such as experiments.
Discretionary - These are constraints based on preferences or decisions taken by
teams.
External - Often based on needs or desires involving a third party.
Leveling of Resources
Resource leveling helps an organization to make use of the available resources to
the maximum. The idea behind resource leveling is to reduce wastage of resources
i.e., to stop over-allocation of resources.
Project manager will identify time that is unused by a resource and will take
measures to prevent it or making an advantage out of it.
By resource conflicts, there are numerous disadvantages suffered by the
organization, such as:
Delay in certain tasks being completed
Difficulty in assigning a different resource
Unable to change task dependencies
To remove certain tasks
To add more tasks
Overall delays and budget overruns of projects
Fast tracking - This performs critical path tasks. This buys time. The prominent feature
of this technique is that although the work is completed for the moment, possibility of
rework is higher.
Crashing - This refers to assigning resources in addition to existing resources to get
work done faster, associated with additional cost such as labor, equipment, etc.
Conclusion
Resource leveling is aimed at increasing efficiency when undertaking projects by
utilizing the resources available at hand. Proper resource leveling will not result in
heavy expenditure.
The project manager needs to take into account several factors and identify critical
to non-critical dependencies to avoid any last minute delays of the project
deliverables.
Purpose of SOW
The main purpose of a SOW is to define the liabilities, responsibilities and work
agreements between clients and service providers.
A well-written SOW will define the scope of the engagement and Key Performance
Indicators (KPIs) for the engagement.
Therefore, the KPIs can be used to determine whether the service provider has met
conditions of the SOW and use it as a baseline for future engagements.
SOW contains all details of non-specifications requirements of the contractor or
service provider's effort. Whenever specifications are involved, the references are
made from SOW to specific specification documents.
These specification documents can be functional requirements or non-functional
requirements.
Functional requirements (in a software system) define how the software should
behave functionally and non-functional requirements detail other characteristics of
the software such as performance, security, maintainability, configuration
management, etc.
Format of SOW
The SOW formats differ from one industry to another. Regardless of the industry,
some key areas of the SOW are common. Following are the commonly addressed
areas in a SOW:
1. Scope
This section describes the work to be done in a technical manner. If the system to
be built is a software system, this section defines the hardware and software
requirements along with the exact work to be done in terms of the final system.
If there is anything 'out of scope', those areas are also mentioned under a suitable
subheading.
2. Location
The location where the work is performed is mentioned under this section. This
section also details the hardware and software specifications. In addition to that, a
description about human resources and how they work are addressed here.
3. Timelines
This defines the timeline allocated for the projects. It includes the development time,
warranty time and maintenance time. In addition to calendar time, the man days
(total effort) required to complete the project is also noted.
4. Delivery schedule
This section of the SOW describes the deliveries and the due dates for the
deliveries.
5. Standards
The standards (internal or external) are defined in this section. All deliveries and
work done should comply with the standards defined in this section of the
document.
6. Acceptance Criteria
This section defines the minimum requirements for accepting deliverables. It also
describes the criteria used for acceptance.
Since SOW is an integrated part of a project, almost all senior members of the
project team should become aware of terms and conditions of the SOW.
Sometimes, especially in software development projects, a penalty is applied if the
delivery dates are missed. Therefore, everyone should be aware of such
demanding terms of a SOW.
Conclusion
SOW is a critical document for project management. It defines the scope of the
work and the work agreements. Therefore, all stakeholders of the project should
have a thorough understanding of the SOW of the project and adhere to it.
Unit Price
In this model, the project is divided into units and the charge for each unit is defined.
This contract type can be introduced as one of the more flexible methods compared
to fixed price contract.
Usually, the owner (contractor/client) of the project decides on the estimates and
asks the bidders to bid of each element of the project.
After bidding, depending on the bid amounts and the qualifications of bidders, the
entire project may be given to the same service provider or different units may be
allocated to different service providers.
This is a good approach when different project units require different expertise to
complete.
Cost Plus
In this contract model, the services provider is reimbursed for their machinery,
labour and other costs, in addition to contractor paying an agreed fee to the service
provider.
In this method, the service provider should offer a detailed schedule and the
resource allocation for the project. Apart from that, all the costs should be properly
listed and should be reported to the contractor periodically.
The payments may be paid by the contractor at a certain frequency (such as
monthly, quarterly) or by the end of milestones.
Incentive
Incentive contracts are usually used when there is some level of uncertainty in the
project cost. Although there are nearly-accurate estimations, the technological
challenges may impact on the overall resources as well as the effort.
This type of contract is common for the projects involving pilot programs or the
project that harness new technologies.
There are three cost factors in an Incentive contract; target price, target profit and
the maximum cost.
The main mechanism of Incentive contract is to divide any target price overrun
between the client and the service provider in order to minimize the business risks
for both parties.
Conclusion
Selecting the contract type is the most crucial step of establishing a business
agreement with another party. This step determines the possible engagement risks.
Therefore, companies should get into contracts where there is a minimum risk for
their business. It is always a good idea to engage in fixed bids (fixed priced)
whenever the project is short-termed and predictable.
If the project nature is exploratory, it is always best to adopt retainer or cost plus
contract types.