fastProject Advanced Guide - lateralworks.com · display the Basic interface which consists of fastBuild, modeling tools, update functions, analysis functions and reporting. The Basic

fastProject Advanced Guide

Based on lateralworks research into the best practices of fast teamsUse with fastProject version 4.x

lateralworks

Contents

1. Purpose 3 2. Overview of fastProject 3

2.1.Basic Mode 32.2.Advanced Mode 4

3. The Basics 5 3.1.Build 53.2.Viewing 53.3.Navigating 63.4.Navigating the hierarchy 73.5.Modeling 73.6.Reports 103.7.Updating 11

4. Schedule Analysis 11 4.1.Overview 114.2. Inspector 124.3.Schedule Analyzer 144.4.Pull-in the schedule 154.5.Preventing Future Slip 19

5. Task Analysis 23 5.1.Network Logic Peel 235.2.Baselines 235.3.Wigglets (task trends) 255.4.Wigglechart (milestone trends) 265.5.Task Inspector (Targets and Tasks) 285.6.Miscellaneous task functionality 30

6. Project Analysis 31 6.1.View schedule “laterally” and functionally 31

Selected questions to ask of the schedule data… 34 Accelerate the schedule every week 35 High level questions 36 Questions to be answered during labs (in class) 37 Selected Slides 38 Appendix 39

� . | © lateralworks. All rights Reserved. Reproduce only with lateralworks permission.2

1. Purpose

The purpose of this document is to provide an overview of fastProject, specifically focusing on the

multiple ways to analyze a schedule. This document does not discuss:

• Best practices around execution and scheduling

• FTTM methodology

• Provide a detailed user guild to all fastProject functionality

2. Overview of fastProject

fastProject implements many of the scheduling best practices, both at the program and portfolio level. It

is a necessary part of the FTTM System, but the reader must bear in mind that there are many other

components that are necessary that cannot be automated, to fully implement FTTM. However,

fastProject goes along way to help automate and perform sophisticated analysis of a schedule, that

allows the user to achieve large gains very quickly.

fastProject has two modes: Basic and Advanced. These modes are accessed on the quick access

toolbar as seen below.

2.1.Basic Mode

Basic mode is invoked by clicking on the first of the two mode buttons on the toolbar. Clicking it will

display the Basic interface which consists of fastBuild, modeling tools, update functions, analysis

functions and reporting. The Basic mode is intended to be used by users who don’t require any of the

more sophisticated analysis functions, and just want to build, model, update, pull-in and report out on

their schedule.


2.2.Advanced Mode

Advanced mode is invoked by clicking on the second of the two mode buttons on the toolbar. Clicking it

will display the Advanced interface which consists of multiple tabs. The Advanced mode is used to

access all the advanced analysis functionality. The following tools are available under Advanced Mode.

Tools: Together with the quick access toolbar, contains all the functionality required for the majority of

functionality.

Resources: Gives the user access to functionality relating to resources, including building a resource

pool, allocating and analyzing resources. It also includes the ability to export resource loading analysis

into Excel, which tends to be more convenient for readability, usability, analysis and distribution.

Portfolio: Provides a means to roll-up/down and roll-over task dates from one schedule to another. It

also provides a means to create and update a “dashboard” from multiple wiggle charts.

Utilities: Provides additional functionality, typically used infrequently.


Info: Provides additional help, including screencasts to the methodology, documentation and the current

version of fastProject.

�

The rest of this document focuses on fastproject functionality. As we said earlier, it does not attempt to

explain the practices or the methodology that are taught during either a training class, an applied

learning engagement or a full program engagement.

3. The Basics

3.1.Build

Clicking on the Build dropdown reveals multiple ways to build the initial schedule, i.e. create the Work

Breakdown Structure (WBS). A full description of each is beyond the scope of this document.

3.2.Viewing

From left to right in order…


Reset view: Puts the Table on the left, Gantt chart on the right, hides completed tasks, opens the lower

pane, displays predecessors and successors, turns the baseline off and resets any formatting.

Mark or unmark tasks: Highlights/unhighlights the selected tasks by adding a yellow background.

Zoom in/Zoom out: Zooms timescale in/out (avoid using slider in lower right).

Entire project: Zooms the timescale so the whole project fits within the visible viewing area.

Notes: Opens notes in a separate window - does not change when user changes tasks.

Lower pane: Opens and closes the lower pane.

Filter (dropdown): Filters the tasks based on the criteria of the selected filter - both fastProject and

standard MS Project filters are accessed via the dropdown.

Selected tasks: Displays only the selected tasks.

Summaries on/off: Show/hide summaries in the Gantt chart.

Targets on/off: Show/hide target milestones in the Gantt chart.

Risk on/off: Show/hide risk on the top of the Gantt chart bars (double spacing).

Show update notes: Displays only those tasks where notes were added during an update.

Important: The correct view for scrubbing and analyzing: screen is 1/3 table, 2/3 Gantt chart, lower

pane open only as much as it needs to be.

3.3.Navigating


F5 (keyboard): Goes directly to the task with the ID entered by the user - note, the task must be open,

i.e. not within a closed summary task or filtered out.

Show UID: Shows the Unique ID column.

Find UID: Goes directly to the task with the Unique ID (UID) entered by the user - note, the task does not

have to be open (if not visible, all tasks will be opened).

3.4.Navigating the hierarchy

Show all: Shows all tasks, including completed tasks.

Close all: Closes all tasks and and all hierarchy levels.

Outline Level: Shows the schedule at various outline levels.

3.5.Modeling

Continuing the left to right descriptions…

Breakdown

Breakdown the selected task into 2-10 subtasks, ending in a milestone. All predecessors are moved to

the first task and all successors are moved to the end milestone. The user has the option to have tasks

linked (or not) and to add doneness criteria prior to the breakdown. In either case, the duration of the

summary task is set to the original task duration by appropriately setting the duration of the subtasks. If

the breakdown occurs on an in-progress task, the first subtask maintains the current update. If the

breakdown is done on a summary task, it will take all wording up to (and including) the first space in the

text, and prefix each of the subtasks (including the milestone) with the text (including the space).


This is typically used where a template is repeated throughout the schedule and it is necessary to

differentiate one for the next. In this case, the user can prefix the summary task with appropriate

wording, e.g. “ToolX: Install and qualify”, and all subtasks will be prefixed with “ToolX: “. This can also be

removed by repeating the procedure of breaking down the summary then, when asked if you want to

add the wording up to the first space, click No then you will be prompted to remove the wording up to

(and including) the first space.

Undo Breakdown

Available in the Utilities tab > Undo breakdown, reverses a breakdown by converting a summary task

back into a task. Removes all subtasks from the schedule, all predecessors linked to the first subtask are

added to the task and all successors linked to the milestone are added to the task. A check is done if

there are any summary tasks that are subtasks or there are any dependencies that will be broken as a

result of the undo. In this case, the undo breakdown stops in order to maintain schedule integrity. There

is also the option to put the original subtask names, durations and owners into the notes of the task so

the effort that went into identifying the subtasks is not lost. They are put into a form such that they can

be copy-pasted at a later point in time.

Link: Links tasks with a Finish-to-Start dependency. The order the tasks are selected is important, i.e. it

links from the first selected task to the second (or last if multiple consecutive tasks are selected).

Unlink: removes only the dependencies between the selected tasks.

Add Hierarchy: Creates a hierarchy between the first and last selected task, i.e. it adds a Summary task

above the selected task and a milestone after the last selected task. Any successors attached to the last

selected task are moved to the last milestone.


Link to Last Task: Adds a Finish-to-Start dependency from all selected tasks to the last task. If the

selected task is a summary task, it uses the last task (typically a milestone) of the summary task.

Link from First Task: Adds a Finish-to-Start dependency from the first task to all other selected tasks. If

the selected task is a summary task, it uses the last task (typically a milestone) of the summary task.

Indent: Indents the selected tasks one level in the hierarchy.

Outdent: Outdents the selected tasks and all subtasks one level in the hierarchy.

Remove constraint (ribbon): Removes any date constraints on the selected tasks. There is also an

option to remove all redundant date constraints in the Utilities tab > Redundancy checks > Remove

redundant date constraints.

Milestones (ribbon): Invokes the milestones interface to allow the user to set various kinds of

milestones, including a Target, a Window, a Challenge, a Touchpoint, Checkpoint, and Deliverables.


3.6.Reports

Various reports are available within fastProject.

WiggleChart

Updates the WiggleChart associated with the schedule. If no WiggleChart is associated with the

schedule, the user has the option to create a new one or link to an existing one. By default, the wiggle

chart should be in the same folder as the schedule.

However, it is possible to manually set the wiggle chart to a location other than the current location by

Utilities tab > Change WiggleChart. If this only contains a filename, the current folder is assumed. If it

contains a path and filename, fastProject will use that location as the location of the wiggle chart. The

location can also be a sharepoint address, in which case the WiggleChart is downloaded to the same

folder as the schedule. Note that the wiggle chart is not “checked out” from sharepoint and the user is

responsible for checking the wiggle chart back into sharepoint.

WiggleChart 3-on-1: displays up to 3 wiggle charts on a single chart, using the data stored in the

current wiggle chart, i.e. it does not store history.

Look Ahead Report: Generates a look ahead report in Excel. The report includes all: in-progress tasks

not started (but could start) tasks and all tasks starting within X days of the current date, where X is one

week by default, but can be set as one of the options.

Targets Report: Produces Wigglets Report for all targets and displays those targets in the Gantt Chart.

Marked Tasks Report: Generates a report of Marked Tasks with Trends and displays Marked Tasks in

Gantt Chart.


Update Notes: Displays tasks that had notes input during the previous update (using date stamp).

Displays notes field and Gantt Chart.

3.7.Updating

Update Schedule: Updates (i.e. the input of actuals) the complete schedule based on the various

settings set by the user on the Update Wizard startup screen.

Update Task: Updates the selected task.

4. Schedule Analysis

4.1.Overview

The remainder of this document will focus on how to analyze a schedule. Analyzing a schedule is

considered in the following groups:

• Schedule Analysis

• The schedule should be technically correct. Unless the schedule is technically correct (all

tasks have successors, no tasks updated in the future, etc.), any further analysis could

be rendered meaningless.

• Pull-in the Schedule

• The primary objective of the team is to determine how to pull-in (accelerate) the

schedule. If they are behind schedule (later than the target), they need to pull-back to the

target. If they are ahead of schedule, they need to pull-in the schedule further, since the

future can be unpredictable, and pulling-in further is a form of “time banking” - creating a

buffer to account for the unexpected.

• Preventing Future slip

• Can also be seen as a form of pull-in, but identifies tasks, not yet on the critical path, that

have a history of slipping and could potentially become the critical path resulting in the

schedule slipping. If these tasks can be identified early, schedule slip can be prevented.

• Network Analysis

• Analyzing the schedule based dependencies, e.g. cross-functional handoffs, all

predecessors/successors to a task, etc.


4.2. Inspector

Regardless of the type of the analysis technique used, the Inspector is the source of all schedule

analysis functions and can be used to answer questions as simple as “How far from the critical path is

this task?” to “What tasks are common to my first 5 critical paths?” In other words, it should be seen as

a one-stop-shop for all schedule analysis functions.

The Inspector is located on the quick access toolbar:

Although all schedule analysis functions are accessed via the Inspector, some of the most common ones

are also available on the toolbar:

• Critical Path (project)

• Critical Path (to task)

• Network Logic Peel

• Peel Back

• Peel Forward

• Turn Peel Numbers On or Off

• Task Trend (of selected tasks)

• Baseline On ir Off


The Inspector is invoked either directly from the quick access toolbar or after an update. In the case of

completion of the update, the Inspector starts up displaying the critical path of the project.

The screenshot below displays the structure of the Inspector.


What to analyze:• Selected task• Selected target• Project

Task information based on the selection above

Cycles through:• Tasks if analyzing

by selected task• Targets if

analyzing by targets

• Disabled if analyzing by project

Schedule analysis functions. The selection of functions is dependent on what is being analyzed, i.e. the selection of the top dropdown.

To focus on an individual task/milestone

Minimize to top right corner

Advanced analysis functions. This analysis is based on what has been selected from the drop-down above or if in task-mode it is based on the selected task.

4.3.Schedule Analyzer

Before doing any form of advanced schedule analysis, ensure the schedule is technically correct. If not,

any form of analysis may be mute: garbage in, garbage out.

fastProject Schedule Analyzer will test for 16 of the most critical problems, i.e. problems that can affect

the critical path thereby getting the team to potentially focus on the wrong thing, or make the schedule

difficult to read leading to missing or incorrectly linked tasks.


Schedule Analyzer: Runs 16 critical tests on the schedule to find problem tasks or areas of the

schedule that need “fixing”, per best practices. This test generates a quality score. We expect good

schedules to have quality scores above 90%. There are additional quality tests that are not scored, but

the errors are reported. Included is a complete best practices description of each test. The Schedule

Analyzer should be run at least once a week.

Individual Test: Allows the user to select any one of the critical tests separately and display the result in

the Gantt Chart. Alternatively, a wizard can cycle through each test and will locate/display the problem.

4.4.Pull-in the schedule

Critical Path: When invoked from the toolbar, displays the critical path of the project. To invoke from the

Inspector, select upper drop-down: Project (information is displayed in the status bar at the bottom).

Critical path to Task (or to a selected Target): When invoked from the toolbar and on a milestone that

has an associated Target, displays the critical path to the selected milestone (or task). To invoke from the

Inspector, select upper drop-down select one of the Targets or put into task mode and select a specific

task to show the critical path to that task.

Peel the Onion: The concept of “peeling the onion” is to “peel back” the levels of critical path, i.e. first

we look at the first critical path (typically the red tasks), then the next critical path (critical path 2) which

is the path with the second least amount of float (the first one being the critical path), and so on. In

fastProject, peeling can be done at the project level (starting with the critical path to the project) or at the

task level (using critical path to task). There is no additional function to calculate the critical paths (the

peels) - they are calculated automatically as part of displaying the critical path to the project or a task.

To peel back the layers, first invoke one of the critical path functions above then use the left blue arrow

on the toolbar to peel back. To peel forward, click the right blue arrow. To display the peel IDs in a

column in the table and on the Gantt bar, click the “123” button which toggles the peel IDs on and off.


By default, only the main and and current peeled critical path is displayed. The user can change what is

displayed by invoking “peel mode” located in Options (from the Tools menu).

This allows the user to choose multiple viewing options.

In addition, it is possible to display icons

(for the current peel only) rather than peel

numbers in the column when displaying

the peel IDs; however, the peel IDs will still

appear on the Gantt bar.

Critical Path Analysis: The functionality

described above allows us to show how

much pull-in we get per peel. A more

advanced method of critical path analysis

is to determine which tasks are common

to a number of the peels then, knowing


this, pulling in those tasks would pull-in multiple critical paths simultaneously. For example, if we could

determine the common tasks between critical paths 1, 2 and 3, then pulling in those tasks would result

in a pull-in of all critical paths. If we only pulled-in critical path 1, the pull-in may not be as much because

critical path 2 would appear on the critical path.

The steps involved are:

1. Analyze the critical paths to determine number of days pull-in for each peel.

2. Identify which critical paths (peels) to analyze further in order to find common tasks.

3. Determine common tasks to the

selected critical paths (peels).

Step 1: Analyze the Critical Paths

Invoke the Inspector, then select:

Upper drop-down: Selected task (in

task mode), or any of the Targets, or

the current project

Lower drop-down: Critical Path

Analysis


At this point, a dialog box will appear. Click “Find Critical Paths” (various options are available in terms of

labelling the chart, applying constraints, generating wigglets, etc.). This will analyze the critical paths and

determine how many days pull-in you get for each peel. An example chart is below.

Step 2: Identify which critical paths to analyze further to find common tasks

What is clear from the above chart is we get a 53 day pull-in if we can pull-in critical paths 1, 2 and 3.

Step 3: Determine common tasks to selected critical paths

Knowing we want to find common tasks to critical paths 1-3, we then select:

First critical path: 1

Last critical path: 3

Then click “Find Common Critical Paths.” This will result in a schedule showing

both the individual tasks and the common tasks. The common tasks are always

in a bold red color. “Normal” looking tasks are in their usual color (blue, shared

red, etc.). Common critical paths are usually found at the beginning and end of

a schedule, and the user has the option to display either or both and whether to

display just the near-term tasks.

From this example, we can see if we can pull-in

“Validate firmware” of “Perform final tests” then

we can pull-in critical paths 1, 2 and 3.


4.5.Preventing Future Slip

An important part of managing any project is to determine which tasks have a history of “slipping”. Left

alone, these tasks could potentially become the critical path, so the logic is to to identify and stop them

from slipping before they become (or become close) to the critical path.

There are two tools that help us in this quest:

• Trends of selected tasks - is available both in the

quick access toolbar and in the Inspector. Displays

trends (wigglets) for the selected tasks. If multiple

tasks are selected, the user is prompted if they

want to limit the tasks to just the near-term.

• This is because the trends of tasks that are

dependent on the near-term tasks have identical (or similar) trend, so it is only necessary to

focus on the near-term.

• If a specific task/milestone is selected then the View Trend tool will display a trend chart (a

Wigglet) in a pop-up box. Various baselines can be displayed by moving the baseline slider in

the pop-up box, see screenshot below.


• Task and Trend Analysis - is accessed only from the Inspector. Provides a more advanced

analysis. Some of this analysis is presented below.


When the Task and Trend Analysis is

selected from the drop-down list a second

option window pops-up with further

criteria to narrow your focus.

In this example we selected in progress

and not started tasks that were slipping

more than 2 days a week. We chose to

display them in the Gantt Chart and to

produce a report of these 27 tasks to

show each tasks trend (below).


Task Breakdown Analysis: Analyzes the WBS and only displays those tasks matching the selected

criteria. Used to identify and drill-down on potential problem tasks, e.g. tasks starting in the next month,

that are >30 days duration and within 16 days of the critical path. This is an indication that these tasks

should be broken down.

In the example above, we have selected all tasks in the project. A stacked bar chart shows how many

tasks fall within the 1 month, 2-3 month, 4-6 month, and >6 months windows. In this example there are 7

tasks that are greater than 30 days duration inside the one month window of time. These clearly need to

be broken down. Further refinement can be done using the Task Breakdown option choices that pops up

after the Task Breakdown Analysis is selected.


5. Task Analysis

5.1.Network Logic PeelLogic Peel: Shows the immediate predecessors and successors of the selected task in the Gantt

Chart. By using the Peel back or Peel forward buttons, the layers of the predecessor/successor

network is exposed. The Network Logic Peel can also be accessed from the quick access toolbar

along with the blue peel tools. In the example below, we have run the logic peel from the inspector,

in Task Mode by selecting a task (highlighted) and then in this case peeling back one logic layer to

reveal the immediate predecessors. You can also peel forward from the selected task.

5.2.Baselines

Update schedule: Baseline is set on the first update of the day (user has the option of not setting a

baseline or setting a new baseline on subsequent updates during the same day).


Baseline on/off: From the quick access toolbar, displays the latest baseline in the Gantt chart (grey

bar on the Gantt chart bar), allowing the user to see graphically “what changed” since the last

update.

Change from baseline: Determine how much the selected task changed from the selected baseline.

View Baselines: Allows the user to selectively display previous baselines. New baselines can be

manually added or previous baselines deleted. The project baseline (baseline 0) is also set here. In

the example above we are using the Inspector to manage baselines. The last 9 baselines can be

displayed on the Gantt Chart as well as Baseline 0 (which should not change). As you scroll left and

right the baselines are displayed on the Gantt.

Of course this is based on what you selected in the top drop-down. You can look at the complete

project, specific targets, or specific tasks. As you change the selected task, so does the trend line

change. This is a very powerful analysis tool used to better understand what is changing on a project

(at the task level).


5.3.Wigglets (task trends)Analyze task trends to prevent a possible future schedule slip. Also see section 4.5 above.

Trends of selected tasks (or a specific task): Generates

the trend of only the selected tasks using the schedule

baseline information. The Finish dates from the last 9 (max)

baselines plus the current Finish date is displayed. Wigglets

can be generated from the quick access toolbar or from

inside the inspector (below).

Analyze trends of selected tasks: In Wigglet report (Excel). Additional functionality contained in the

custom “Wigglets” tab (below).


5.4.Wigglechart (milestone trends)Analyze milestone trends (versus Target) to prevent a possible future schedule slip.

WiggleChart: Generates the WiggleChart based on the current schedule and provides a dashboard

(Target Milestone Summary tab).

WiggleChart 3-on-1: Generates a WiggleChart with up to 3 targets on a single chart (uses data in

the WiggleChart to combine three on one chart). See next page example. Also included on next

page is a “Dashboard” from the WiggleChart.



5.5.Task Inspector (Targets and Tasks)Allows the user to quickly analyze the schedule based on any of the targets in the schedule or the

selected task. Current status information of the target of the task is displayed. Actions that can be

performed are:

Critical Path: Cycle through the critical paths to each target and get it’s status.

Trends: Trend of target or selected task .

Near-term Task Trends: Trends of each in-progress/not started task leading to target or

selected task.

Critical Path Analysis: Critical path

analysis on target or selected task.

All Predecessors: To target or selected

task.

All Successors: To target or selected

task.

Look Ahead Report: To target or

selected task.

Update & Trend Stats: Can be found in

the second and third sheets in the Task

and Trend Analysis report (examples on next page).


The charts on these reports are dynamic and will change based on what you select in the filters

on the table below. This becomes a very

powerful analysis tool for individual activity

owners.


5.6.Miscellaneous task functionalityDays between two tasks’s dates: calculate the duration between two tasks in the schedule. If

multiple tasks are selected, only the first and last task is used. The Start or Finish date of the

selected tasks can be used. This function is found in the Inspector (last function on the top drop-

down list).

Tasks creation and completion rate: Shows all tasks added to the schedule since <date> (see next

page).


6. Project Analysis

6.1.View schedule “laterally” and functionallyUse the functional schedule for individualized scrubbing (missing, correct, accurate, inter/intra-

dependencies). Using the Filter to slice and dice schedule by Function. Use the tool to analyze

dependencies (between milestones, between functions).

Filter: only displays only what the user selects, e.g. just tasks owned by the function firmware (FW)

Cross Functional Analysis: displays only those tasks that have an input or/and output to the

selected field that are different from the selected field, e.g. display all tasks not owned by firmware

that are an input to the

firmware tasks. User can


optionally filter on a subset of the output. User can optionally generate Wigglets. Inputs are


formatted light brown, outputs dark brown (colors are coincidental).

Cross Milestone Analysis: Displays

only those dependencies between

different top-level (outline level 1)

tasks. Available in the Inspector when

it is in “Project” mode, i.e. when

looking at the complete project.

Task Starting or Finishing within a

Date Range: Permits a filtering of

tasks within a specific time frame.

Only available in the “Project” mode

while using the Inspector (below).


Selected questions to ask of the schedule data…

Are these the right tasks?

Are we missing anything?

Do the durations reflect realistic risk and/or estimated learning cycles needed?

Could any of the durations be realistically accelerated?

• What do we need to make them go faster?

Are these the correct dependencies?

• Within the project and to other functions/schedules

Can anything realistically start sooner?

Based on what we know today, will we be able to meet the schedule?

• If not, what are the barriers to acceleration?

• Can they be removed?

Have we defined the right doneness criteria for each of the major milestones?

• If yes, do we have all the tasks?

• If no, what is missing?

Do we have all the tasks to fulfill the doneness criteria for the next major milestone?

What can be done differently (critical thinking), eliminated, done concurrently or changed (doneness

criteria) to make the project go faster?

• What do we need to make it happen?


Accelerate the schedule every weekStrategic

• Do we have to make it? Can we buy it or outsource it instead?

• Can we establish a development/alliance partner?

• Is it possible to change the product definition/functionality?

• Can we re-use and/or use common parts?

• Can we challenge the base technology assumptions?

• Is there/should we set a common reference architecture?

Tactical

• Can we eliminate non-value activities?

• Could we make activities take place concurrently?

• Can we find more resources internally?

• Can we find contract resources outside?

• Can we realistically reduce the duration estimates, understanding that risk may go up but can

be managed?


High level questionsHow far off are you from the target date?

What is the schedule trend?

• Are you slipping or accelerating the schedule?

If slipping, do you have enough time to recover?

What are your recovery plans?

• If on schedule, what are you doing to continually pull-in the schedule?

• What are the top 3 future slips you are expecting?

• What are you doing to mitigate those slips?

Do you have confidence that the team will hit/can hit the target date:

• If not, what do you need to increase your confidence level?

What factors will be/are barriers to timely delivery (per our customer commitments)?

• What are the top 3 technical problems or innovations needed?

• What are you doing to solve them?

• How do you plan to overcome the barriers?

• What are the other non-technical barriers that need to be removed in order to go faster?

What is the critical path?

• What steps are you taking to accelerate the critical path?

• What can I do to help you accelerate the critical path?

• What do you need that you are not getting now?

• What is the 2nd-5th critical paths?

• What are you doing to accelerate the 2nd-5th critical paths?

• What is your management process to continually accelerate the schedule?


Questions to be answered during labs (in class)Viewing

• How can I see a macro view of the project and the general timelines?

• What tasks are driving my project end date?

• Where are we relative to our targets?

• How can I see the schedule by function or by any other criteria generally?

• How ate baselines used and how can I manage them?Critical Path Analysis

• What tasks are near my main critical path?

• What is the critical path to an intermediate task or milestone?

• How can I see all (or just the one) critical paths near my main critical path?

• How can I get a quick summary of milestones vs. targets

• How to get to the critical path for each of these?Task Analysis

• Show me only the tasks leading to/from my selected task

• Show me only the next predecessors and successors to/from my selected tasks

• What are the next level of predecessors or successors?

• How far is my selected task from the critical path?

• What is the duration between the finish dates of my two selected tasks?Project Analysis

• In general, are tasks slipping, not changing or pulling-in?

• What is the trend of my selected tasks?

• What tasks are slipping more than N days/week?

• What is the trend of my milestones w.r.t. their targets?

• Which targets am I likely to miss?

• Where are the errors in my schedule?

• Which near-term tasks need to be broken down?


Selected Slides


Appendix

Class Overview

This class is designed for people who have been using FTTM schedules for a few months and who

would like a deeper understanding of how to analyze their schedules. The class covers advanced

analysis tools in fastProject that support the FTTM Planning Methodology. The goal of deep schedule

analysis is to better understand schedule trends in order to improve transparency and early warning by

using historical patterns to better predict future performance. fastProject has a series of analysis tools

that permit managers to dig deep into their own areas of the schedule.

Deep schedule analysis by core team members has proven to be a key technique for distributing the

ownership of the integrated schedule across the core team. Team members tend to look at the

integrated schedule from their own functional perspective, while the Program Manager analyzes the

schedule from the horizontal integrated perspective. This class reviews how to use fastProject to

perform this analysis. The more this analysis is distributed around the team and to functional executives,

the more shared ownership is gained over the project’s outcome. Further, we have found that more

people doing analysis improves the overall quality of the schedule data. Better data means more reliable

schedules.

Audience

• FTTM Core Team Members (typically functional managers or directors)

• Program Managers

• Executive functional managers interested in deeper analysis capabilities (typically VPs)

Learning Objectives

• Enable managers to independently analyze fastProject schedules in order to provide ongoing

scrubbing inputs to the Program Manager, such that the overall quality and accuracy of the schedule is

improved throughout the life of the project.

• Enable each functional manager on the core team to periodically (e.g. weekly) analyze their schedule

with their team(s).

• Enable core team members to identify possible pull-in opportunities in the schedule, specifically

concerning their functional areas.

• Expand asynchronous development of the schedule through having the full core team engaged in the

schedule creation and analysis process.

• Learn how to perform basic schedule analysis techniques using fastProject.


Requirements

• For Intact Team:

• Use the teams latest schedule for analysis. Each person should have a copy of the latest

schedule.

• For representatives from multiple teams:

• Option A: Use one schedule as the basis for individual analysis.

• Option B: Each team uses their own schedule for analysis (preferred).

• Refresh Planning has been implemented on the project for at least 4 weeks. More project history

improves the analysis results.

• fastProject is installed on each participants laptop. If each participant does not have a fastProject

license, then learning pairs are formed around each licensed copy of fastProject.

• Since this is a hands-on class, it is essential to have fastProject available for at least each learning

pair.

• Five hours is the estimated duration for the class, however since the class is based on the use of the

live project schedule and highly interactive, the class timing can be variable.

Timing

• 4 to 8 hours, depends on audience/learning objectives

The class is not designed to...

• Teach participants how to create and maintain FTTM schedules.

• Provide a comprehensive overview of fastProject general features. The focus of this class is exclusively

on schedule analysis tools.


Documents

fastProject Advanced Guide - lateralworks.com · display the Basic interface which consists of fastBuild, modeling tools, update functions, analysis functions and reporting. The Basic