Showing posts with label Project Management. Show all posts
Showing posts with label Project Management. Show all posts

Thursday 28 September 2017

Microsoft Project 2016 Step by Step 50% discount offer (Microsoft Press Store)

ebook deal: Microsoft Project 2016 Step by Step 50% off offer expires Oct 1 at 7AM GMT #ProjectServer #ProjectOnline http://ow.ly/W2v430fuhvI

The quick way to learn Microsoft Project 2016!
This is learning made easy. Get more done quickly with Project 2016. Jump in wherever you need answers–brisk lessons and colorful screenshots show you exactly what to do, step by step.

  • Quickly start a new plan, build task lists, and assign resources
  • Share your plan and track your progress
  • Capture and fine-tune work and cost details
  • Use Gantt charts and other views and reports to visualize project schedules
  • Share resources across multiple plans and consolidate projects
  • Master project management best practices while you learn Project
  • Look up just the tasks and lessons you need

Friday 15 January 2016

Project Management and Red Tape - Holding back Creativity

This is an excellent article from HBR;
Project engineers possess a wealth of good ideas and creative solutions, but too often these ideas are just not able to carry the day inside the bureaucracy of large capital projects. Project executives also understand that entrepreneurial and creative engineers can be their best allies in delivering quality, cost-efficient, timely new builds. So what is holding these engineers back?

jan16-14-hbr-img-6438

Some of the most common barriers are the unintended consequences of well-intentioned efforts to mitigate risk:
  • A sense that blanket design philosophies, technical standards, and previous designs cannot be questioned. While common standards across companies and industries foster consistency, they can blind stakeholders to potential breakthroughs — unless a culture of healthy challenging and questioning is encouraged.
  • Removing responsibility for key technical decisions from the project team. Most organizations that undertake capital projects centralize the ultimate arbiters of technical design decisions (the very best subject-matter experts and engineers) in order to leverage economies of scale and achieve consistency. This can often mean that the most talented engineers have no skin in the game on any single project (except to ensure there are no major technical shortcomings) and develop a bias toward conservatism.
  • An inability to easily determine the value of ideas. The rigmarole required to financially model most projects can make evaluating ideas extremely difficult for engineers, so they often assume that any deviation will produce nominal (or negative) value.
  • A preoccupation with benchmarking against other projects. Comparing project costs can create a false ceiling by inherently casting doubt on innovative ideas that create value beyond the benchmark.
  • Missing the forest for the trees. In managing the tremendous volume and complexity of work required to develop and build a large capital project, the notion of creating value is often lost in the flurry of activity to complete engineering deliverables.
Read More about this on HBR>>>>

Friday 24 July 2015

How to pick a project management methodology

Think of project management (PM) methodologies as blueprints, step-by-step instructions that guide your team on how to build a successful project. With so many different – and in some cases, overlapping – approaches to managing the complexities of any given program, how can you know which one is right for your project, team or organization?

Let’s start by taking a look at some of the key PM methodologies:

  • Agile was developed for projects requiring significant flexibility and speed and is comprised of “sprints” – short delivery cycles. Agile may be best-suited for projects requiring less control and real-time communication within self-motivated team settings. Agile is highly iterative, allowing for rapid adjustments throughout a project.
  • Waterfall methodology is sequential in nature; it’s used across many industries, most commonly in software development. It’s comprised of static phases (requirements analysis, design, testing, implementation and maintenance), executed in a specific order. Waterfall allows for increased control throughout each phase but can be highly inflexible if scope changes may be anticipated later.
  • Critical Path Method (CPM) is a step-by-step methodology used for projects with interdependent activities. It contains a list of activities and uses a work-break-down structure (WBS), a timeline to complete and dependencies, milestones and deliverables. It outlines critical and non-critical activities by calculating the “longest” (on the critical path) and “shortest” (float) time to complete tasks to determine which activities are critical and which are not.
  • Critical Chain Project Management (CCPM) differs from Critical Path Method (CPM) in that it focuses on the use of resources within a project instead of project activities. To address potential issues with resources, buffers are built in to ensure projects are on-time and that safety is not compromised.
  • Six Sigma was originally developed by Motorola to eliminate waste and improve processes and profits. It is data-driven and has three key components: DMAIC (define, measure, analyze, improve and control) DMADV (define, measure, analyze, design and verify) and DFSS (which stands for “Design for Six Sigma” and can include the previous options, as well as others, like IDOV – identify, design, optimize and verify). Six sigma is sometimes debated as a methodology in the PM community.
  • Scrum (named after rugby) is a part of the agile framework and is also iterative in nature. “Scrum sessions” or “30-day sprints” are used to determine prioritized tasks. A Scrum Master is used to facilitate instead of a Project Manager. Small teams may be assembled to focus on specific tasks independently and then meet with the Scrum Master to evaluate progress or results and reprioritize backlogged tasks.
Good, better, best?

While there is no “best” methodology that works for all business types, sizes or industries, there are ways to determine which methodology to use and how to effectively apply it. When evaluating methodologies, these are only a few of the many factors that should be carefully considered:

  • Organizational strategic goals and core values
  • Key business drivers
  • Constraints
  • Stakeholders
  • Risks
  • Complexity
  • Project size & cost

To assist in this regard, the Project Management Institute (PMI) developed the Organizational Project Management Maturity Model (OPM3) – now a globally recognized standard – to enable organizations to identify, measure and improve PM capabilities, standardize processes, help solidify successful project outcomes and ultimately determine best practices and strengthen the connection between strategic planning and execution. OPM3 focuses on overall organizational strategic effectiveness and incorporates project, program and portfolio management. This standard was updated in 2008 and again in 2013 and is recognized by the American National Standards Institute (ANSI) as an American National Standard.

[Related: Why agile skills are more valuable than certifications]

In their Implementing Organizational Project Management Practice Guide, the PMI discusses some high-level processes for tailoring PM methodologies. Organizations should carefully evaluate which methodologies work for various projects based on factors in the PMI Methodology Tailoring Process in order to maximize strategic benefits.

Benefits of Organizational Project Management (OPM)

OPM3 is aimed at achieving successful strategic alignment. And since successful project outcomes depend heavily on such alignment, it may make sense for your business to adopt OPM3. Organizations will need include EPMOs (Enterprise Program Management Offices) in high-level planning sessions in order to ensure the right methodologies are deployed for specific projects to increase productivity and customer satisfaction, gain a competitive advantage, improve cost control and communications and predict performance. Ultimately, this will improve and expedite decision making as well as support alignment with company-wide goals.

Different PM methodologies have their strengths and weaknesses; organizations may want to consider selecting multiple project management methodologies based on the project and other factors previously mentioned (among others)…and also develop some standardized best practices that can be tweaked as various factors change.

The key is to figure out how specific projects align with the over-all organization objectives, and, once you determine what factors impact the success or failure of those goals, find the most suitable methodologies that will enable your organization to effectively and efficiently reach the desired business result.

Read More >>>

Wednesday 3 June 2015

Microsoft Shoring Up Tasks with Wunderlist To-Do App

The Berlin-based company behind the Wunderlist to-do app has been purchased by Microsoft Relevant Products/Services. Redmond reportedly agreed to buy 6Wunderkinder GmbH for between $100 million and $200 million.

The purchase will indeed bring Microsoft something it lacks, namely mobile task management capability.

"Microsoft Project is a very heavyweight solution, geared toward large teams and complex project planning, and is not targeted to individual or small team use," said Stowe,managing director of research and analyst firm workfutures. "Although Project is integrated with Office as Project Online, it doesn't really solve the need for lighter weight task management, and is definitely not a 'mobile first, people first' product, which Wunderlist is, with very popular iOS and Android apps." 

Read More>>>

I personally would like to see this integrated with SharePoint and Project Server Task Management.

Tuesday 3 June 2014

What can CIOs do to avoid project failure?

Excellent article in CIO Magazine;

Projects require the right teams and as CIO you'll need to select individuals who have the right skills, a proper understanding of the methodology based on appropriate training, and very importantly the capacity to take on the project.

By ensuring good governance and clear project specification, which should be driven by business objectives, you can give your team, and your customer, a thorough understanding of the end goal and a clear vision of where a project is heading. It also means that when a project is not working effectively, it can be picked up earlier and prevent much wasted time and resources.

Risk and stakeholder management has an enormous contribution to make if you're looking to be successful.

Read More at CIO: http://j.mp/SpRrPj

Wednesday 16 November 2011

Why People Micromanage? Learn to manage by exception using appropriate tools

Interesting Article by Ron Ashkenas in HBR;

Over the past few decades I've worked with hundreds of managers, and many complain that they work for micromanagers. But strangely I don't recall anyone who ever admitted to being one.

I was thinking about this incongruity while working with a group of senior managers from a manufacturing division who were trying to streamline their operational reporting processes. During the meeting, the team listed their various monthly reports and the review meetings that accompanied them.

From the discussion it became clear that the same data was being sliced, diced, and formatted in many ways and then being checked and rechecked by a variety of managers at different levels. In addition, ad-hoc reports were being created in response to particular questions raised by the regular reports. In other words, operational reporting had become a cottage industry that sucked up time and resources.

None of the senior managers found this process productive, and they knew that their people complained about being "micromanaged to death." At the same time, none of them felt accountable for having created this problem. Somehow this burdensome, costly culture of micromanagement happened unintentionally.

So if nobody's waking up in the morning intending to be a micromanager, then why do people still feel micromanaged? Let me suggest two mostly unconscious reasons:

Managers worry about being disconnected. As managers rise through the ranks, they often become concerned that they've lost touch with the actual work of the organization. Because they have less direct contact with the shop floor or customers, they start to feel isolated. One way of reducing this anxiety is to seek information in as many ways as possible — through reports, meetings, and one-on-one conversations. But since this attempt to stay connected is largely unplanned and driven by idiosyncratic anxiety, the result is that managers at different levels and functions end up looking at the same basic data in many different ways.

Managers stay in familiar operational territory. Many managers are unable to let go of their old job or their old ways of doing their job. It's the well-worn saying: "What got you here won't get you there." Many managers are promoted based on their ability to achieve operational goals, manage budgets, control their numbers, and solve problems. However, at higher levels managers usually need to dial down their operational focus and learn how to be more strategic. To do so, managers have to trust their people to manage day-to-day operations and coach them as needed, rather than trying to do it for them. For many managers this is a difficult transition and they unconsciously continue to spend time in the more comfortable operational realm of their subordinates.

When the unconscious need for more direct information converges with a manager's tendency towards operational focus, micromanagement is often the result. And when many managers operate this way, we end up with the complex micromanagement culture described above.

The good news is that once you discover these unconscious patterns, it's possible to do something about them. The divisional manufacturing meeting that I attended is a good example. During the discussion, managers began to confront their patterns — both individually and as a team — and agreed to eliminate or modify certain reports and reviews. They also agreed to continue holding regular meetings to recalibrate their information appetite.

The message here is that with every promotion, managers need to learn a little more about how to lead using an "instrument panel" instead of direct observation. In doing this, managers need to work together to standardize the cockpits — so that the instruments and information not only make sense to them, but don't become overwhelming for everyone else.

What's your experience with micromanagement?

Why People Micromanage - Ron Ashkenas - Harvard Business Review

Wednesday 19 October 2011

The Project Map: Your road map to project management

Here is a great article from Microsoft online help….

Applies to: Microsoft Excel 2010, Project 2010, Project Server 2010

Project roadmap image

The Project Map can help you accomplish your project goals by teaching you how to work with the standards and practices of project management methodology as you use Project 2010.

The Project Map follows the phases of the project life cycle:

  • Initiate your project.
  • Plan your project with tasks, budgets and resources.
  • Track and monitor your project.
  • Close your project.

Click the links to go to “project management goals,” which provide you with detailed information on how to accomplish that goal.

Step 1: Initiate a project

The initiation phase of a project plan helps you prepare for creating a schedule in Microsoft Project. Activities that occur at this time include:

  • Preparing a charter that outlines the scope of your project at a high level.
  • Understanding who your stakeholders are.
  • Getting familiar with the communication and scheduling tools you’ll need to manage your project.

GOAL DESCRIPTION

Introduction to project management
Learn the basics of project management to get the most out of Microsoft Project and complete your project successfully.

Microsoft Project basics
New to Microsoft Project? Learn the basics of the program and how to get started using it for simple project management tasks.

Get to know Project 2010
Project 2010 has powerful new scheduling features, a timeline view, and the team planner, as well as the new ribbon interface.

Initiate a project
The best projects exhibit good planning before the schedule is created. Learn what happens before the schedule happens, such as stakeholder needs, project expectation setting, company constraints and portfolio, and charter drafting.

Step 2: Plan and build a schedule

After a project has been approved and initiated, it’s time to put it together using scheduling software. Activities that occur at this time include:

  • Adding tasks to a schedule.
  • Creating relationships between tasks using outlining and task linking.
  • Assigning people and other resources to tasks.

GOAL DESCRIPTION

Set up a project
Once you've finished your initial planning, use Project 2010 to create and set up your project plan.

Add tasks
Most projects begin with a list of the tasks that need to be completed. Once you create or import your task list, you can then define the relationships between them.

View your project
Project managers, stakeholders, and team members need different types of project information. Project 2010 provides many customizable ways to view the critical elements of your project.

Manage resources
Resources are typically people assigned to tasks in your project plan. They can also include anything that is used to complete a project, such as equipment and materials.

Manage risks
The best way to prevent risks to future projects is to learn from the risks that came up in past projects.

Step 3: Track and monitor your project

Once your project is underway, you need to know what’s happening in order to keep it on-track. Activities that occur at this time include:

  • Understand which views in Project help you discover problems in your schedule.
  • Take corrective action on problem tasks that are affecting the project end date.
  • Communicate problems and possible solutions to your team and stakeholders.

GOAL DESCRIPTION

Track progress
Though Project makes tracking easy, there are several steps to take before you can begin tracking your progress.

Manage project costs
Going over budget often causes projects to fail. Project 2010 can help you add and manage resources to make certain your project ends on time and in good shape.

Work with multiple projects
Use Project 2010 collaboration features to communicate across and manage multiple projects.

Communicate project information
Project 2010 can sync a task list to a list on a SharePoint site. Or you can import a SharePoint list into Project. This helps communication and collaboration in organizations that do not use.

Create and print reports
Project allows you to create visual and textual reports in Excel or Visio to help you analyze and present project information to stakeholders.

Manage risks
Identify potential trouble spots by anticipating risks and responding to risk events, and report project progress to stakeholders and team members.

Use Project Server to manage your project
Discover how Microsoft Project Server can be used to track and manage tasks and assignments throughout your organization.

View your project
Project managers, stakeholders, and team members need different types and depths of project information. Project 2010 provides many customizable ways to view the critical elements of your project.

Step 4: Close your project

All projects come to an end, but this doesn’t mean that your work is finished. If you don’t record the successes and challenges of the project, you’re doomed to repeat the problems in the next project. Activities that occur at this time include:

  • Reporting your project successes and challenges to team and stakeholders.
  • Archiving your project so that it can be used to help ensure the success of future projects.

GOAL DESCRIPTION

Close your project
Not all work on a project ends when the project ends. Archiving a project is also important, especially if you want others in your organization to copy the successes you had.

Capture and archive project information with SharePoint
Project 2010 can sync a project task list to a list on a SharePoint Server 2010 or SharePoint Foundation 2010 site. Or you can import a SharePoint list into. This is an important option for collaboration, especially if your organization does not use Project Server.

Create project reports
When a project has completed, then it’s time to put a stamp on it by creating reports to show everyone the success of the project. .

View your project
Project managers, stakeholders, and resources need different types and depths of project information. Project 2010 provides many customizable ways to view the critical elements of your project.

The Project Map: Your road map to project management - Project - Office.com

Thursday 14 April 2011

Microsoft EPM - Managing Programs/Master Projects, Part10 – inserting/ embedding Sub-Projects into Master Projects

In this post, we will review how we bring everything together i.e. inserting/embedding Sub-Projects into Master Projects.

Once all the projects are published, return to the master project.

  • In the master project, click Insert > Project.
  • Next, select the projects to insert, one at a time. Ensure that each Project being selected is Checked-in and also the option 'Link to Project' is selected. See below for further details. Remember to insert the Projects in the order you want them to appear on the Program schedule.
image

Note: If you don't want to update the subproject with changes from the original project, or if you don't want to show changes from the subproject in the original project, clear the 'Link to Project' check box.

The Master Project/Program structure will start taking shape as you add/insert the Sub-projects. See example below.

If an inserted Sub-project needs to be moved/relocated to another part of the overall WBS, this can be done just as easily as you would move a task/summary task.

image

Critical Note: After the sub-projects are inserted, it is important to expand them so that their data is refreshed.

Configuring Cross-Project Dependencies

Once the sub-projects are inserted in the Master Project/Program, it is important to review and set up (as necessary) the dependencies on the various components that make up the overall Program.

Create dependency links between tasks and milestone across projects as necessary. See example below.

!

Important Note:

  • It is recommended that cross-project dependencies are not created at summary task level.
  • It is recommended that users add associated notes to cross-project linked tasks and milestones for ease of reference.

The procedure for creating dependencies on tasks and milestones across inserted sub-project projects is very much similar to that within the same project. For example, select the tasks/millstones to link and then click the 'Link Tasks' button on the toolbar. Refer to example below.

Linked tasked and milestones can be viewed easily by adding the 'External Tasks' column to your view and then setting auto filter to quickly filter in and out these links.

image

Once the dependencies are created, external dependent tasks and milestones will show up as 'ghost' tasks within the sub-projects. See example below:

image

!

Important Note:

It is recommended that for ease of reference, appropriate task notes are added when external project dependencies are created.

Saving & Publishing Master Project with Sub-Projects

Once all the sub-projects have been inserted and the required dependencies created, it is time to save the projects.

· Expand all sub-projects that have not been expanded since inserting into the Master Project/Program.

image

· Select File > Save

· Ensure that you select 'Yes to All' in the save dialogue to save changes on all inserted sub-projects and the Master Project/Program.

image

· Close the Master Project/Program including associated Sub-project.

Note: If there are some changes pending, the above save dialog box will appear.

image

· Ensure that the Master Project/Program and all the associated Sub-projects are properly checked in prior to exiting the application.

You can review the cache status via the File > Open Dialog box.

image

Setting Baselines (Optional if required)

Open individual sub-projects and baseline as required by your Business Processes.

· Open each sub-project via File > Open

image

· From the toolbar select Tools > Tracking and then select 'Set Baseline'.

Note: User may choose either to baseline the entire project or selected tasks.

image

image

· Save, Close and Check-in the Sub-project.

· Repeat the above steps for each Sub-project.

That’s all for now folks. In the next post, we will review process for updating sub-projects.

Thursday 17 March 2011

Microsoft EPM Project & SharePoint Workspace Automated Archive & Recovery Solution (ARS)– April Bonanza!!

Author: David Smith (Project Solution Ltd - Business Development Manager )

- Are you struggling with the numerous manual steps for archiving completed projects and associated SharePoint Workspaces?
- If you are using categories to hide/deny projects? what about access to important project artefacts?
- Wasting too much time and effort when you could be focusing on other key areas of your business?
- Are you experiencing system performance issues as result of amount of data/structure of data? Is this affecting adoption of EPM/SharePoint?

Want EPM Project Archive & Recovery processes to be completely automated? Want a simple solution that aligns with your Work/Project Management business processes? Payback within approximately 1year?

Microsoft EPM ARS 2007/2010 is one of the Business productivity add-on solutions/tools for Microsoft EPM/SharePoint which completely automates the entire process for Archiving and Recovery. simple and ease to use.
- Make the most of your existing investments in Microsoft EPM/SharePoint.
- Helps improve adoption of the overall Microsoft EPM/SharePoint Solution.
- Manage complete project life cycle including archiving completed projects.
- End-user self-service capability for archiving & recovery without losing access to associated project workspaces/artefacts.
- Improve system performance by keeping live data streamlined.

Check out the demonstration video below and find out more!!

Microsoft EPM Project & SharePoint Workspace Automated Archive & Recovery Solution (ARS)

April 2011 is going to an exciting month for all of us here in UK. We have the Easter break and the Royal Wedding on 29th April to look forward to. The whole nation will be celebrating. We at Project Solution will be participating by offering a massive 25% discount and FREE lifetime technical support and maintenance (including upgrades for 2010) for all our Business productivity add-on solutions/tools, on all orders during the month of April 2011, including ARSOffer valid until mid night 30th April. Contact us today on +44 (0) 1223 597 940 or [email protected]  quoting eCode ‘April2011’.

Monday 10 May 2010

Link between project management excellence and long-term success

Here is an interesting article that I found very enlightening.

This is extract from ‘Closing the gap’: The link between project management excellence and long-term success is an Economist
Intelligence Unit briefing paper, sponsored by Oracle. The Economist Intelligence Unit conducted the survey and analysis, and wrote the report.

Economist_ClosingTheGap

(click picture to download copy of paper)

Note: The report was based on a survey of 213 senior executives and project managers worldwide and in-depth interviews with nine executives and project management experts in the fields of industrial manufacturing; architecture, engineering and construction; aerospace and defence; mining and metals; pulp and paper; and utilities, oil and gas.

Conclusion

To be successful, companies should consider the following best practices;

  • To maintain a competitive advantage and ensure that projects generate maximum value for the company, business leaders must link every project management decision, from the choosing of projects to the way teams will measure outcomes, to the strategic goals of the organisation.
  • Training, mentoring and other development activities for project management professionals should be tied to specific skills gaps and career planning.
  • To prove that a project was a success, it is necessary to measure more than timeliness and adherence to budget; companies should also measure outcomes against project goals, determine whether the project delivered bottom-line results and assess the satisfaction of clients and stakeholders with the project.
  • A lessons-learned database, in which project teams document project challenges and how they were handled, is a valuable tool for avoiding mistakes in the future.
  • Leaders who continue to focus on improving project management strategies and methodologies as the economy rebounds will garner the greatest long-term success.

Hope this helps in understanding the relevance and importance of structured Project Management processes within the organisation.

Sunday 28 December 2008

Good planning techniques

A few things that you may wish to bear in mind when planning your project;

  1. Minimize number of assignments per task to say 1-2 assignments.
  2. Do not mix Resource Type assignments on common tasks. Split/create different tasks/assignments as necessary.
  3. Resource assignment (task) durations should be reasonable say 2-5days. Use re-occurring tasks as necessary to split larger single assignment durations.
  4. Use multiple ‘annual’ projects for long running assignments.

Hope this helps….

Task Planning: best-practice tips for Microsoft Project users

Here is a great article from Andy Jessop……….

Once you’ve created your project and have the basic building blocks of it in place, the next thing to do is define the tasks that allow the project to meet its aims. As with most aspects of using Microsoft Project, a little time (and thought) at this stage will pay you back many times over when your project plan is implemented.

Below you’ll find a handful of best-practice tips and tricks, gained over many years of experience in working with people who plan real-world projects using Microsoft Project as their project management tool of choice.

1. Plan from the top down

The easiest way to plan and manage a project is to start by thinking about the overall project deliverables and then successively break down each element into greater detail.

As you’ve already defined your overall project information (within the Project Information dialog box), your next step is to list the key deliverables that will make up your project.

If you’ve created your project from a template, common deliverables may already have been defined for you. If not, then simply list them on your Gantt chart in approximately the order in which they will happen. Don’t worry about exact sequencing at this stage, this will be explained in step 4 below.

If you’re not sure what your key deliverables are, take a look at your project documentation; for example a “Project Charter”, “Terms of Reference” or “Project Initiation Document”. Within these documents should be listed the key areas of your project that you will be measured against and will also contain the scope items that will be of interest to your project’s sponsor.

2. Add tasks and milestones

With top level entries listed (initially as simple tasks); you should now start adding the detailed tasks to accurately describe your project’s scope. An ideal way to do this is to take each top level entry in turn and break it down into several sub-deliverables.

Try to ensure that each sub-deliverable is measurable and can be allocated to a team member (or members) to perform. This breaking down of work is commonly known as ‘outlining’ and is similar in function to outlining a Word or PowerPoint document using the Indent and Outdent buttons.

Regarding detail, don’t be tempted to create tiny tasks with unnecessary detail in them – remember that every bit of detail you create here will have to be tracked and managed later on in the project’s lifecycle.

Don’t forget that you can use Task Notes to list detailed information about each task. If you are in an EPM environment, Task Notes are published automatically to team members assigned to relevant tasks.

Finally, don’t forget the project’s timescale in relation to detail. Tasks that happen early on within the lifecycle can be planned to greater detail than those nearer the project’s end (which has still to be accurately defined) – especially if the project is to last several months. Many successful projects are planned using this ‘rolling wave’ principle, with additional task and assignment detail added as the project progresses through its lifecycle.

Now, look at adding key milestones. These milestones may already be defined as part of a project template. If they aren’t, simply insert new tasks and make their duration values zero days.

Try to have milestones scheduled when major pieces of work (or expenditure) have concluded or are about to happen. Also place milestones at key decision points within the projects lifecycle.

One note on naming conventions; milestones are easier to read if they follow a noun-verb convention e.g. “Testing completed” or “Testing can commence”; task descriptions make more sense if they follow a verb-noun convention e.g. “Conduct user acceptance tests”.

3. Enter durations against tasks

With tasks, summary tasks and milestones listed, you should now enter best-guess duration values against tasks. Don’t worry about too detailed an estimate at this stage; remember that the resource assignments which you will subsequently add can change task duration values.

When entering durations, don’t forget that you can drag task bars directly on the Gantt chart. Do be careful when dragging to use the correct cursor. The one to choose has a single arrowhead and can be found when you hover the cursor over the right of a task’s bar.

The other two cursors, a percent symbol or a 4-way arrowhead (which can be found when you hover the cursor over the left and middle of a bar respectively) will either add percent complete progress to the task or schedule the task with a ‘Start No Earlier Than’ constraint.

If you’re following the ‘rolling wave’ principle explained above, consider having large duration values for tasks late in the project’s lifecycle. These tasks will invariably be broken down into smaller tasks with more discrete duration values as and when more detail about the project is known.

Another useful technique is to mark these large-duration tasks as being ‘Estimated’. When a duration is estimated, a “?” symbol is appended to the task’s duration. You can use the ‘Tasks With Estimated Durations’ filter to select tasks that are flagged as estimated.

4. Link related tasks together

Once you’ve defined your tasks, you should next place them in a logical sequence by linking them together. The easiest way to do this is to click on a predecessor task, hold down the CTRL key and then click on its successor task. Then click on the Link Tasks button on the Standard toolbar so that the successor will be scheduled to start once the predecessor is complete.

By linking this way, you can quickly create your project’s schedule, confident that tasks will happen in the correct sequence, especially if tasks or milestones have multiple predecessors or successors.

An alternative (and intuitive) way to link tasks is to drag a link from predecessor to successor. You should however drag with care. Use the 4-way arrowhead and initially drag up or down, but not left or right. The cursor will change to a link icon, which you can then drop on a successor task’s bar.

Try to ensure that the predecessor and successor bars are both visible on screen. If you have to scroll off screen, do be careful as scrolling can be very rapid. If sudden scrolling loses your position on the screen, don’t panic. To get your task bars back in view, just click on the Go To Selected Task button on the Standard toolbar.

Using this approach you’ll create a structured project plan encompassing all the relevant summary tasks, subtasks and milestones. By giving the tasks duration values and linking related tasks to each other, you’ll be well placed to identify which tasks are critical to you completing your project on time.