The demo opens with a title card that displays the text Manage scope changes.

Change is inevitable in a project, and keeping scope change to a minimum is an important part of my job.

Next, a Scope Change Request form is shown in Microsoft Office Word 2003. The image zooms in to a more detailed view of the form. While the pointer clicks the down scroll arrow on the vertical scroll bar, the form scrolls up.

To ensure that changes go through the proper channels, I ask everyone on my team to use a change request form. This allows everyone close to the project to identify potential changes and keeps me in the loop during the course of the project.

The image changes to a close-up of a Scope Change Record in Microsoft Office Excel 2003. A cell in the column Project Impact Statement is selected, and the text Will add 20% to the overall scope budget, schedule and cost is typed.

When the requests come in, I can assess them and add them to the Excel Change Record if they meet the right criteria. As long as everything is documented, I can manage the changes before they become a bottleneck or turn into a scheduling issue.

The image changes to a project management plan in Microsoft Office Project Professional 2003. The pointer clicks a cell that's in the Work column and the Manage scope row, displaying the value 8 hrs. The pointer clicks the down arrow in the cell until 6 hrs is displayed. Then the pointer clicks outside the cell, and the adjacent cell in the Duration column is updated from 1 day to 0.75 days.

Using templates like these helps everyone on a project communicate better. And keeping track of the changes throughout a project helps me protect the quality of the project, even if a schedule change is necessary.

The image of the project management plan disappears. The text Microsoft Office appears with the Microsoft Office logo, and under them the URL http://www.office.microsoft.com appears.