GANTT Charts

A Gantt chart is a horizontal bar chart developed as a production control tool in 1917 by Henry L. Gantt, an American engineer and social scientist. Frequently used in project management, a Gantt chart provides a graphical illustration of a schedule that helps to plan, coordinate, and track specific tasks in a project.

Gantt charts may be simple versions created on graph paper or more complex automated versions created using project management applications such as Microsoft Project or Excel.

A Gantt chart is constructed with a horizontal axis representing the total time span of the project, broken down into increments (for example, days, weeks, or months) and a vertical axis representing the tasks that make up the project (for example, if the project is outfitting your computer with new software, the major tasks involved might be: conduct research, choose software, install software). Horizontal bars of varying lengths represent the sequences, timing, and time span for each task. Using the same example, you would put “conduct research” at the top of the verticle axis and draw a bar on the graph that represents the amount of time you expect to spend on the research, and then enter the other tasks below the first one and representative bars at the points in time when you expect to undertake them. The bar spans may overlap, as, for example, you may conduct research and choose software during the same time span. As the project progresses, secondary bars, arrowheads, or darkened bars may be added to indicate completed tasks, or the portions of tasks that have been completed. A vertical line is used to represent the report date.

Gantt charts give a clear illustration of project status, but one problem with them is that they don’t indicate task dependencies – you cannot tell how one task falling behind schedule affects other tasks. The PERT Chart, another popular project management charting method, is designed to do this. Automated Gantt charts store more information about tasks, such as the individuals assigned to specific tasks, and notes about the procedures. They also offer the benefit of being easy to change, which is helpful. Charts may be adjusted frequently to reflect the actual status of project tasks as, almost inevitably, they diverge from the original plan.

Also Read…

Management Communication Plan

PERT Charts

A PERT chart is a project management tool used to schedule, organize, and coordinate tasks within a project. PERT stands for Program Evaluation Review Technique, a methodology developed by the U.S. Navy in the 1950s to manage the Polaris submarine missile program. A similar methodology, the Critical Path Method (CPM) was developed for project management in the private sector at about the same time.

PERT Chart 1

A PERT chart presents a graphic illustration of a project as a network diagram consisting of numbered nodes (either circles or rectangles) representing events, or milestones in the project linked by labelled vectors (directional lines) representing tasks in the project. The direction of the arrows on the lines indicates the sequence of tasks. In the diagram, for example, the tasks between nodes 1, 2, 4, 8, 9 and 10 must be completed in sequence. These are called dependent or serial tasks. The tasks between nodes 2 and 3, and nodes 2 and 4 are not dependent on the completion of one to start the other and can be undertaken simultaneously. These tasks are called  parallel or concurrent tasks. Tasks that must be completed in sequence but that don’t require resources or completion time are considered to have event dependency. These are represented by dotted lines with arrows and are called dummy activities. For example, the dashed arrow linking nodes 6 and 9 indicates that the system files must be converted before the user test can take place, but that the resources and time required to prepare for the user test (writing the user manual and user training) are on another path. Numbers on the opposite sides of the vectors indicate the time allotted for the task.

The PERT chart is sometimes preferred over the Gantt Chart, another popular project management charting method, because it clearly illustrates task dependencies. On the other hand, the PERT chart can be much more difficult to interpret, especially on complex projects. Frequently, project managers use both techniques.

Also Read…

Management Communication Plan

Business Driven IT KPIs

KPIs (Key Performance Indicators) are a critical management tool to measure the success and progress of effort put in towards achieving goals and targets – to continually improve performance.

Every business set their specific KPIs to measure the criteria that drive the business success – these vary from business to business. One thing every modern business has in common though, is IT – the enabler that underpin operational processes and tools used to commerce daily. Setting KPIs that measure the success of IT operations does not just help IT leadership to continuously improve but also proof the value of IT to the business.

Here are ten IT KPIs that matter most to modern business

1. % of IT investment into business initiative (customer-facing services and business units)
How well does the IT strategy, reflected in the projects it is executing, align with the business strategy? This metrics can help to align IT spend with business strategy and potentially eliminate IT projects for IT that does not align directly with business objectives.

2. % Business/Customer facing Services meeting SLAs (Service Level Agreements)
IT is delivering service to customers; these are internal to the business but can also be delivered external to the business’ client/customers directly. Are these services meeting required expectations and quality – in the eye of the customer? What can be done to improve.

3. IT Spend vs Plan/Budget
Budgets are set for a purpose – it is a financial guideline that indicates the route to success. How is IT performing against budget, against plans? Are you over-spending against the set plans? Why? Is it because of a problem in the planning cycle or something else? If you are over-spending/under-spending, in which areas do this occur?

Knowing this metrics give you the insight to take corrective actions and bring IT spend inline with budgets.

4. IT spend by business unit
IT service consumptione is driven by user demand. How is IT costs affected by the user demands by business unit – are business units responsible to cover their IT cost, hence owning up to the overall business efficiency. This metrics put the spotlight on the fact that IT is not free and give business unit manager visibility of their IT consumption and spend.

5. % Split of IT investment to Run, Grow, Transform the business
This is an interesting one for the CIO. Businesses usually expects IT to spend more money in growing the business but reality is that the IT cost of running the business is driven by the demand from IT users with an increased cost implication. Business transformation, now a key topic in every board meeting, needs a dedicated budget to succeed. How do these three investment compare in comparison with business strategic priorities.

6. Application & Service TCO (Total Cost of Ownership)
What is the real cost of delivering IT services and application. Understanding the facts behind what makes up the total cost of IT and which applications/services are the most expensive, can help to identify initiatives to improve.

7. Infrastructure Unit Cost vs Target & Benchmarks
How do you measure the efficiency of your IT infrastructure and how does this compare with the industry benchmark? This is a powerful metrics to justify ROI (Return on Investment), IT’s value proposition, IT strategy and the associated budget.

8. % Projects on Time, Budget & Spec
Is the project portfolio under control? Which projects need remediation to get back on track and what can be learned from projects that do run smoothly?

9. % Project spend on customer-facing initiatives
How much is invested in IT projects in the business for the business (affecting the bottom line) in comparison with customer-centric projects that impacts the business’ top line.

10. Customer satisfaction scores for business/customer facing services

Measure the satisfaction of not just the internal business units that consume IT services but also the business’ customer’s satisfaction with customer-facing IT services. Understand what the customer wants and make the needed changes to IT operations to continuously improve customer satisfaction.

KPI vs Vision

In the famous words of Peter Drucker “What gets measured gets improved”, KPIs give you the insight to understand:

  • your customer
  • your market
  • your financial performance
  • your internal process efficiency
  • your employee performance

Insight brings understanding that leads to actions driving continuously improve.