Unit 1: Getting To Know Microsoft Project - Subjective Questions

Microsoft Project is a project management software tool used to plan, schedule, monitor, and control projects.

Its major roles in software project management include:

• Creating a structured list of project tasks.
• Assigning durations, dependencies, and resources to tasks.
• Preparing schedules using different views such as the Gantt Chart and Calendar.
• Tracking progress against the original baseline plan.
• Identifying delays, resource conflicts, and schedule-related risks.
• Presenting project information in a form that is easy for managers and team members to understand.

It helps project managers organize project activities and make informed decisions throughout the project life cycle.

The general steps for starting a new project are:

1. Open Microsoft Project and select a blank project or an appropriate template.
2. Set the project start date in the project information settings.
3. Choose the project calendar and define the working days and working hours.
4. Enter the project tasks in the task sheet.
5. Organize tasks into summary tasks and subtasks where necessary.
6. Specify task durations and establish relationships between tasks.
7. Add project resources such as people, equipment, and materials.
8. Assign resources to the appropriate tasks.
9. Review the schedule in the Gantt Chart view.
10. Save the project using a suitable file name and location.

These steps create the basic project structure needed for detailed planning and monitoring.

The project start date and calendar provide the scheduling foundation for the entire project.

• The project start date determines when the first scheduled activity can begin.
• The project calendar defines working days, non-working days, holidays, and working hours.
• Task start and finish dates are calculated using these settings.
• Correct calendar settings prevent activities from being scheduled during weekends, holidays, or approved leave periods.
• They help produce realistic estimates of project completion.
• They also ensure that resource availability and task durations are calculated consistently.

If these settings are incorrect, the resulting schedule may contain unrealistic dates, incorrect deadlines, and misleading information about project progress.

Toolbars are collections of buttons, commands, and controls that provide quick access to frequently used Microsoft Project functions.

They assist a project manager by:

• Creating, editing, and formatting tasks quickly.
• Applying task relationships and constraints.
• Assigning resources to tasks.
• Changing between project views.
• Saving, printing, and sharing project information.
• Accessing tracking and reporting functions.
• Reducing the time required to locate commands through menus.

Toolbars improve productivity because commonly used operations can be performed with a single click. Their arrangement may vary according to the Microsoft Project version, user preferences, and the active view.

A user can customize the Microsoft Project interface according to the tasks performed most frequently.

Typical customization activities include:

• Adding frequently used commands to the Quick Access Toolbar.
• Removing commands that are rarely used.
• Rearranging commands into a convenient order.
• Creating custom groups for scheduling, tracking, or reporting commands.
• Selecting the commands and views that are most relevant to project planning.
• Restoring the default interface when necessary.

Effective customization should focus on frequent project management activities. For example, a project manager may place commands for task linking, resource assignment, progress updates, and view selection in easily accessible locations. This reduces navigation time and supports faster schedule maintenance.

The Calendar view displays project tasks in a calendar format according to their scheduled start and finish dates.

It commonly shows:

• Task names.
• Task start dates and finish dates.
• Task durations.
• Tasks scheduled for particular days or weeks.
• Overlapping tasks.
• Milestones and important deadlines.

The Calendar view is useful for understanding the project schedule from a time-oriented perspective. It is particularly helpful when tasks are associated with specific dates, meetings, releases, inspections, or deadlines. However, it may not show complex task dependencies as clearly as the Gantt Chart view.

The Calendar view places tasks on the dates during which they are scheduled to occur. By examining the entries for each day or week, a project manager can identify scheduling problems.

• Tasks displayed on the same dates may indicate overlapping activities.
• Several tasks assigned to the same resource may suggest a resource conflict.
• A crowded date range may indicate excessive workload or unrealistic planning.
• Tasks extending over holidays or non-working days may indicate incorrect calendar settings.
• A milestone appearing after its required deadline may reveal a schedule problem.

After identifying a conflict, the project manager can adjust task dates, modify dependencies, reassign resources, or revise the task duration. The Calendar view is therefore useful for date-based review and communication.

The Gantt Chart view is a major Microsoft Project view that presents project tasks in a table on the left and a time-based bar chart on the right.

Its main components include:

• A task table containing task names, durations, start dates, and finish dates.
• Horizontal bars representing the duration of tasks.
• Milestone symbols representing important events.
• Summary task bars representing groups of subtasks.
• Links or arrows representing task dependencies.
• A timescale showing days, weeks, months, or other time units.

The Gantt Chart is used to plan task sequences, understand project duration, identify the critical path, monitor progress, and communicate the schedule to stakeholders.

The three elements have different purposes:

• A task is an individual project activity that requires time and possibly resources. For example, designing a database is an individual task.
• A summary task represents a group or phase of related subtasks. Its duration and dates are calculated from the subtasks beneath it. For example, system development may contain coding, integration, and testing subtasks.
• A milestone is a significant event or checkpoint with zero duration. It represents an achievement, approval, delivery, or decision point.

In the Gantt Chart, regular tasks appear as horizontal bars, summary tasks are displayed as larger summary indicators, and milestones are displayed using milestone symbols. Correct use of these elements makes the schedule easier to understand and manage.

Task dependencies define the order in which activities should occur. In the Gantt Chart view, they are commonly represented by arrows connecting task bars.

The common dependency types are:

• Finish-to-Start: The predecessor must finish before the successor starts. This is the most frequently used relationship.
• Start-to-Start: The successor cannot start until the predecessor starts.
• Finish-to-Finish: The successor cannot finish until the predecessor finishes.
• Start-to-Finish: The successor cannot finish until the predecessor starts. This relationship is used less frequently.

Dependencies help Microsoft Project calculate schedule dates automatically. They also make the effect of a delay visible because a change in one task can shift the dates of connected tasks.

Both views display scheduled project tasks, but they emphasize different types of information.

The Calendar view is easier for reviewing appointments and date-specific activities, while the Gantt Chart is more suitable for analyzing the structure, duration, dependencies, and progress of the complete project.

The Timeline view provides a compact, high-level representation of important project tasks, milestones, and phases.

It supports communication by:

• Showing major project activities in chronological order.
• Highlighting key deadlines and milestones.
• Presenting a simplified schedule for managers and stakeholders.
• Making the overall project plan easier to understand.
• Providing a useful visual summary for presentations and status meetings.
• Reducing the amount of detailed information shown to audiences who do not need the complete task list.

The Timeline view should be used as a communication summary rather than as a replacement for detailed scheduling. Detailed task information remains available in views such as the Gantt Chart.

A project timeline can be created and modified through the following process:

1. Open the Timeline view or display the timeline area above the main project view.
2. Select important tasks, summary tasks, or milestones.
3. Add the selected items to the timeline.
4. Arrange the items in chronological order as required.
5. Change the display level or format to improve readability.
6. Remove tasks that are not important to the audience.
7. Add or adjust milestone labels and task bars.
8. Review the timeline for overlapping labels and unclear dates.
9. Copy, print, or present the timeline as a project summary.

The timeline should contain only significant information so that stakeholders can understand the major project commitments quickly.

The Gantt Chart and Timeline view serve different purposes.

• The Gantt Chart provides detailed information about individual tasks, durations, dates, dependencies, resources, and progress.
• The Timeline presents a simplified, high-level summary of selected tasks, project phases, and milestones.
• The Gantt Chart is mainly used by project managers and team members for planning and controlling work.
• The Timeline is mainly used for management reviews, presentations, and stakeholder communication.
• The Gantt Chart can contain hundreds of tasks, whereas the Timeline should contain only the most important activities.

The Timeline is derived from project schedule information, but it does not replace the detailed planning capabilities of the Gantt Chart.

A timescale is the time scale displayed across the top of a project view, such as the Gantt Chart or Timeline. It provides the time reference used to interpret task bars and milestones.

Timescale levels may include:

• Years.
• Quarters.
• Months.
• Weeks.
• Days.
• Hours.

The timescale is important because it:

• Helps users understand when tasks begin and end.
• Allows schedules to be viewed at different levels of detail.
• Supports both long-term planning and short-term monitoring.
• Makes task durations and overlaps easier to interpret.
• Improves the readability of printed and on-screen schedules.

A project manager should choose timescale levels appropriate to the planning horizon and the audience.

Changing the timescale changes the level of detail shown in the schedule without changing the underlying task data.

• A yearly or quarterly scale is useful for long-term strategic planning.
• A monthly scale helps review project phases and major deliverables.
• A weekly scale is useful for monitoring medium-term work.
• A daily scale supports detailed execution planning.
• An hourly scale may be useful for short activities or operational scheduling.

A broad timescale reduces visual clutter and helps users understand the overall plan. A narrow timescale provides precise information about task timing, overlaps, and deadlines. The project manager should select a timescale that makes the relevant scheduling information easy to interpret.

Gridlines are horizontal or vertical lines displayed in project views to help users align information with rows, columns, and time periods.

Their benefits include:

• Making task rows easier to follow across the screen.
• Helping users align task bars with dates on the timescale.
• Improving the readability of dense schedules.
• Supporting accurate visual comparison of task start and finish dates.
• Making printed reports and charts easier to interpret.
• Separating important areas of the schedule visually.

Gridlines should be configured carefully. Too many strong gridlines can make a chart appear crowded, while too few may make it difficult to relate task bars to the timescale.

The timescale provides the date reference, while gridlines provide visual alignment with that reference.

• The timescale identifies the units of time displayed across the chart.
• Gridlines extend the time divisions into the chart area.
• Users can compare task bars with specific days, weeks, or months more easily.
• Appropriate gridline intervals reduce errors when estimating task dates visually.
• Stronger lines can be used for major time divisions, while lighter lines can represent smaller intervals.

For example, a monthly timescale with weekly gridlines can show both the broader project phase and the detailed weekly schedule. This combination is especially useful when reviewing task overlaps, deadlines, and progress.

The activities can be represented as a structured schedule as follows:

• Create a summary task named Software Project.
• Add the five activities as subtasks beneath the summary task.
• Enter estimated durations for each activity.
• Set finish-to-start dependencies where one activity must follow another.
• Use the Gantt Chart to display durations, dependencies, and the overall project sequence.
• Use the Calendar view to review the activities according to their scheduled dates.
• Add major deliverables such as approved requirements, completed design, and released software as milestones.
• Add the summary task and milestones to the Timeline view for management communication.
• Select a suitable timescale and gridline pattern to make the schedule readable.

This structure provides detailed control in the Gantt Chart and a concise project summary in the Timeline.

Visual views provide several advantages:

• They make complex schedules easier to understand.
• They reveal task sequences, overlaps, and deadlines.
• They support communication with technical and non-technical stakeholders.
• They help identify delays and scheduling conflicts.
• They allow the same project data to be examined from different perspectives.

However, they also have limitations:

• A crowded chart can become difficult to read.
• Visual displays may hide detailed resource or cost information.
• The Calendar view may not show dependencies clearly.
• The Timeline may oversimplify the project if important tasks are omitted.
• Incorrect dates or task relationships will produce misleading visual information.

Therefore, visual views should be used together with accurate task data, appropriate timescale settings, and regular schedule reviews.