WK 3– Apply: Project Management Flowchart and Summary
NAME
UNIVERSITY
CMGT-545
Due Date: 4
Project Management Flowchart
Project Management Flowchart is a representation that helps to visualize the sequence of process
to be followed during project management process. Cloud-based application provides the
functionality over a network where compute and storage happens on servers in data centers.
Basically, this new changeover would help the company in saving time, money and resources on
the long run.
The above flowchart represents on how the project will managed. As this cloud migration project
has been divided into three phases,
1. Initiation phase
2. Execution phase
3. Final phase
Initiation phase includes start of project and defines the project. This phase is where the project
is directed to board members of our company. This is the phase where convincing power and
visionary goals are directed at shareholders and c-level managers. It also depends upon how the
project is defined at a broad level and is researched whether the project is feasible or not. These
two factors are challenges in this phase.
Execution phase deals with project planning, if the project gets approved by key members of the
company. This phase also deals with installing and testing the software, conducts training and
sharing the progress report with shareholders and board committee. As it is to migrate existing
application with cloud-based software, some of the legacy systems were not automatically
compatible with new system. Secondly, it was a challenge to train as there are various location
across the country. This phase may face challenges in managing communication, project
scheduling conflicts.
Final phase evaluates on how cloud migration project had influenced the company’s overall
progression and performance. It also deals with all the shortcoming problems faced during
project so that improvements can be made for future projects. The final report is all about the
overall project progress. What information needs to be input in a project manager report may be
a challenging issue. Also, which information should be shared with which member could be also
key issue that need to be managed.
CEO of Intuit Inc, Dylan Piazza believes that cloud migration project will help the company in
the long run by saving resources, capital and time. As a project manager, I have to plan and
develop a team for this project. Apart from them, communication means with our leaders and
key shareholders should be established. Information sharing with team members, c-level
managers and shareholders enables them to be updated and helps in solving problems that need
to be solved immediately.
Presenting meetings with c-level managers and stockholders regularly will direct the project on
course as such meeting will help in pointing out problem and how to tackle them immediately. It
also encourage high morale within the team enabling them to have more enthusiasm and interest
toward the project. I would prefer open communication with my team and encourage them to be
critical thinkers. I would openly accept any ideas and suggestions giving them freedom for
creativity. Rather than accepting the privilege of running the project efficiently myself, I would
prefer to my team to accept as a whole. This will create a positive mentality in my team members
as their hard work has been acknowledged.
References
Eby, K.(2018).smartsheet.https://www.smartsheet.com/blog/demystifying-5-phases-project-
management
Kowalski, A.(2017).egrappler.https://www.egrappler.com/project-manager-challenges/
#Project_Closure
Review
As SaaS is a rather new phenomenon of the software business, the subject is not widely
researched. Additionally, software deployments are commonly seen as a part of the
system development lifecycle and therefore the amount of the deployment specific
research is also quite limited. The field of project management is widely researched, but
there is a lack of knowledge on the usage of project management methods and their
success in practice
Software development life cycle (SDLC) is a term covering all activities of developing
the software from initial planning to its retirement. SDLC is used in software engineering
to describe a process for planning, creating, testing, and deploying a software system.
Core activities of SDLC include requirements engineering, solution design, building,
testing, debugging, deployment, and maintenance.
Deployment process phases and activities
Release
After the software development process the product is ready to be released. In the
release phase all operations in order to prepare a system for assembly and transfer to
the customer site are performed. In addition, it is important to identify needed
resources needed for operation at the customer site and planning of later phases of the
deployment process.
Install and activate
In the activation phase, the software is activated usually with an execution command.
More complex systems might require additional activation operations and they require
confirmation that all supporting systems are ready to use.
In large software deployment processes the usage of multiple environments is common.
This means that the vendor installs the working copy of the software on a production
environment whereas other versions may be installed on different servers to a test
environment, development environment, and disaster recovery environment.
Deactivate
Compared to activation, deactivation is the opposite action. In deactivation the
executing components of a system are shut down. Usually before being able to perform
deployment of a new software/version some deactivation operations are required.
System deactivation is commonly called as application retirement or application
decommissioning.
Adapt
In the adaptation phase the installed software is being modified. The difference between
adaption and updating is that this phase is initiated by local events such as changing
the environment of customer site, whereas updating is usually executed by an external
software vendor.
Update / Version upgrade
As mentioned above, updating is a process where an earlier version of a software or
part of it is replaced with a newer release.
Built-in updates: is a common term for system mechanisms that are checking new
updates and installing them automatically. The process can be fully automated, or the
updating might require user initiation and can be controlled by the user. Usually these
updates at least ask for user’s approval before the installation is started.
As a new version of the software is released the version tracking system helps users to
notice and install these updates on PCs and local networks. The version tracking can be
web based, local or browser based depending on the software and client’s
requirements.
Uninstall
The inverse phase of installation is naturally uninstallation of a software. In this phase
the software is removed, and it usually also involves some reconfiguration of other
software systems in order to remove the uninstalled system’s files and dependencies.
Obsolescence
As the software is outdated and its support has been discontinued, the product life cycle
becomes to an end and the software is being taken out of use.