Abstract: Embodiments of the present invention are directed toward providing a method utilizing project management software for creating a project plan utilizing a top-down strategy allowing a user to describe high-level objectives before filling in details for the underlying tasks of which the high-level objectives are comprised. As an alternative to basing summary task dates and durations solely on subtask data, the present invention allows a user to enter dates and duration values into summary tasks regardless of when the corresponding subtasks occur. By utilizing a top-down project management approach, embodiments of the present invention promote utilizing summary tasks as a starting point of project planning. Users are able to input high-level objectives of a project when more specific details of subtasks are unknown. Because summary task data is not rolled-up from the subtask data, a user may specify details such as dates and durations of subtasks at a later time.

Abstract: A project management application provides an environment in which a user can transform a project sketch, which is based on mostly “freeform” data, into a defined project plan. The project management application facilitates the mixture of freeform task attribute values with structured attribute values of one or more project tasks. The project management application can utilize an internal calculation model to manage the relationships between task attribute values despite accepting freeform values for task attributes. The project management application calculates the attribute values to the extent allowed by the calculation model's recognition of the attribute values.

Abstract: Embodiments of the present invention are directed toward providing a method utilizing project management software for creating a project plan utilizing a top-down strategy allowing a user to describe high-level objectives before filling in details for the underlying tasks of which the high-level objectives are comprised. As an alternative to basing summary task dates and durations solely on subtask data, the present invention allows a user to enter dates and duration values into summary tasks regardless of when the corresponding subtasks occur. By utilizing a top-down project management approach, embodiments of the present invention promote utilizing summary tasks as a starting point of project planning. Users are able to input high-level objectives of a project when more specific details of subtasks are unknown. Because summary task data is not rolled-up from the subtask data, a user may specify details such as dates and durations of subtasks at a later time.

Abstract: Technologies are described herein for providing a pan and zoom control in conjunction with a timeline for navigating project schedule data in a project management application. The project management application displays a pan and zoom control in conjunction with a project schedule timeline, with the pan and zoom control at a position and of a size relative to the timeline that reflects the temporal scope of project schedule data currently displayed. The pan and zoom control is configured to allow a user to move and resize the control along the timeline. Upon detecting movement or resizing of the pan and zoom control, the project management application will change the scope of the project schedule data displayed to match the time period represented by the new position and/or new size of the pan and zoom control in relation to the timeline.

Abstract: A project management application is provided in which an active or not active task state for each task may be displayed in a user interface. The active or not active task state would indicate whether the task is inactive or active. If the state of a task is active, the project management application may treat the active task as a normal task in the project plan. If the state of a task is inactive, the project management application may treat the inactive task as having no effect and may ignore the inactive task for scheduling purposes in the project plan. The project management application may maintain and display information of the inactive tasks in the project plan. The project management application may display the inactive tasks in a different style from the active tasks in the user interface.

Abstract: Technologies are described herein for showing and correcting irregularities in a schedule. A project management application allows a user to manually define tasks within a schedule. The application evaluates the manually defined tasks to determine if the tasks cause an irregularity within the schedule. If so, the application provides one or more visual indications of the irregularity to the user. The application also provides functionality for allowing a user to resolve or ignore the irregularity.

Abstract: A project management resources scheduling user interface is provided in which resource information may be displayed in a condensed timeline for each resource over the duration of a project. Individual tasks or groups of tasks displayed in the project management resources scheduling view may be moved from one resource to another resource while respecting project constraints and dependencies. Unassigned and unscheduled tasks may be dragged onto the scheduling view and may be dropped on a given resource in a timing location required by the project. Tasks may be viewed according to a hierarchical relationship between tasks of a given project. The scheduling view may be used in combination with a Gantt chart view of project tasks for allowing a view of both task-based and resource-based scheduling.

Abstract: A project management application provides an environment in which a user can transform a project sketch, which is based on mostly “freeform” data, into a defined project plan. The project management application facilitates the mixture of freeform task attribute values with structured attribute values of one or more project tasks. The project management application can utilize an internal calculation model to manage the relationships between task attribute values despite accepting freeform values for task attributes. The project management application calculates the attribute values to the extent allowed by the calculation model's recognition of the attribute values.