BACKGROUND

The present disclosure relates generally to project planning and management tools in a cloud computing infrastructure.

This section is intended to introduce the reader to various aspects of art that may be related to various aspects of the present disclosure, which are described and/or claimed below. This discussion is believed to be helpful in providing the reader with background information to facilitate a better understanding of the various aspects of the present disclosure. Accordingly, it should be understood that these statements are to be read in this light, and not as admissions of prior art.

Cloud computing relates to the sharing of computing resources that are generally accessed via the Internet. In particular, a cloud computing infrastructure allows users, such as individuals and/or enterprises, to access a shared pool of computing resources, such as servers, storage devices, networks, applications, and/or other computing based services. By doing so, users are able to access computing resources on demand that are located at remote locations, which resources may be used to perform a variety computing functions (e.g., storing and/or processing large quantities of computing data). For enterprise and other organization users, cloud computing provides flexibility in accessing cloud computing resources without accruing large up-front costs, such as purchasing expensive network equipment or investing large amounts of time in establishing a private network infrastructure. Instead, by utilizing cloud computing resources, users are able redirect their resources to focus on their enterprise's core functions.

Developing and managing projects using cloud computing can be a complex task. To manage this complexity, different project scheduling modes may be employed. For example, one project scheduling mode allows for project tasks to be automatically updated when another related project task is delayed. However, automatically updating project tasks may reduce a user's control of a project. Further, automatically updating project tasks may lead to confusion for entities managing or executing the project. For example, in a complex project, delays may frequently occur, and each delay may automatically update project tasks. As a result, timelines for the project tasks may change on a weekly or even daily basis, which may create confusion for entities executing the tasks.

As such, improvements in project scheduling modes or a new project scheduling mode is needed to improve project planning and management tools in a cloud computing infrastructure.

SUMMARY

A summary of certain embodiments disclosed herein is set forth below. It should be understood that these aspects are presented merely to provide the reader with a brief summary of these certain embodiments and that these aspects are not intended to limit the scope of this disclosure. Indeed, this disclosure may encompass a variety of aspects that may not be set forth below.

Systems and methods described below may include a planning console generated in a cloud computing environment that allows for planning and management of projects. The planning console includes a semi-automated mode of operation to manage project task parameters according to dependency relationships between the project tasks.

Further, as discussed herein, in some embodiments projects may include automatically updating project tasks under certain conditions. As an example, a planning console may be generated by the cloud computing system. The planning console may include a semi-automated scheduling mode and a project with a plurality of project tasks. In one example, the project tasks include a predecessor task having a planned timing. The system determines at least one dependency relationship between the predecessor task and at least one successor task. Moreover, the system identifies a timing difference between the planned timing and an actual timing of the predecessor task. Further, the system generates one or more user-selectable interaction points, in the semi-automated scheduling mode, wherein interaction with a first interaction point causes the project to be automatically updated such that the timing of at least one successor task is based on the actual timing based at least on the dependency relationship and interaction with a second interaction point causes the project timelines to remain the same, i.e., to not be updated.

