All 3 Milestones are included.
ITProject Managment
Regatta University
IT Project Charter
For
Student Degree Progress
Version
1
.0
Table of Contents
Document History 3
Executive Summary 4
Project Purpose/Justification 4
Project Description 4
Preliminary Scope Statement 4
Out of Scope 4
Project Objectives and Success Criteria 4
Constraints 4
Assumptions 4
Project Deliverables 5
Project Resource Estimate 5
Summary Milestone Schedule 5
Summary Budget 5
Project Approval Requirements 6
Project Organization 6
Authorization 6
Project Team 6
Directors of Assigned Resources 6
Project Sponsor 6
Document History
Document Revision/Release Status
Revision
Date
Description of Changes
Author / Editor
0.1
6/29/15
Initial format
Jane Smith
1.0
8/31/15
Initial draft
John Doe
Executive Summary
Students leverage a web portal to access university-related information and resources. Content within it can be targeted to all users or to those within a pre-specified role (e.g., students at a particular campus) or it can be user-specific.
As an academic institution, one piece of information critical to students is their current progress in their degree program or programs.
The purpose of the student degree progress project is to create an area to display user-specific academic progress.
Project Purpose/Justification
University leadership requested this project to promote student awareness and provide students easy access to their degree progress.
Project Description
Preliminary Scope Statement
The purpose of this project is to create an area that displays user-specific academic progress within the appropriate roles, leveraging data through a back-end system. This project will include the necessary modifications to the back end to relay this information. More specifically, this project will include the following:
· Creating the graphical elements in a web-friendly format
· Creating the necessary web view to accommodate the graphical elements
· Creating the necessary changes to the back end to prepare data supporting the student information
· Creating the necessary web service to securely expose the student’s information to the graphical elements and web view
Out of Scope
Due to business-specific processes, some students, particularly those who have been pursuing a degree for over four years, may not be able to see their academic progress using the deliverables of this project. Changes to the back end to expand this functionality are out of scope, as are any changes intended to enhance functionality to provide additional data beyond the academic progress already captured in another system.
Project Objectives and Success Criteria
· The project will provide the functionality described within the preliminary scope statement.
· The project will be delivered without incurring any additional expenses.
· The project will be delivered free from any significant defects or without causing any down time.
· The project will be delivered no later than two weeks from the target time frame defined within the milestone schedule below.
Constraints
· Additional funding is not available.
· The information available to students is derived from data within the back end and is as accurate, timely, and available as the source data and its structuring.
Assumptions
· No major changes in formatting or scope will be presented during the life of the project.
Project Deliverables
· Project Charter
· Project Management Plan
· Design
· User Interface Mockup
· Architectural Design
· Test Plan
· Test Scenarios
Project Resource Estimate
The student degree progress project is estimated to use the following resources:
Project Resource Estimate
Resource
Estimated Work Hours
Project Manager
48 Hours
Systems Analyst
12 Hours
Middleware Applications Developer
44 Hours
Backend Systems Analyst
50 Hours
Total:
154 Hours
Summary Milestone Schedule
Summary Milestone Schedule – List key project milestones relative to project start
Project Milestone
Target Date
Project Start
September 1
Graphical Component Unit Complete
September 23
Web View Unit Complete
September 25
Backend Unit Complete
October 7
Integration Testing Complete
October 14
Submit to Leadership
October 26
Leadership Acceptance
November 2
Transition to Production
November 5
Project Closeout
November 13
Summary Budget
Fiscal Year
Summary Budget – List component project costs
Project Component
Component Cost
Hardware
$0
Software and Licensing
$0
Vendor
N/A
Total
$0
Project Approval Requirements
The project will be completed once all requirements are met and all deliverables have been received and approved by the client.
Project Organization
Role
Name(s) – Department(s)
Project Sponsor
Jane Smith
Project Manager
John Doe
Core Stakeholder
Arthur Bowman
Vendor Resources
None
Project Team Members
Shila Cole, Ana Fischer, John Jones
Authorization
Approval of this project charter provides authorization to move forward in accordance with the information contained in this document.
Project Team
1
John Doe, Project Manager
Shila Cole, Systems Analyst
Ana Fischer, Middleware Application Developer
John Jones, Backend Systems Analyst
Date:
Date:
Date:
Date:
Directors of Assigned Resources
Michael Erdmann, Middleware Director
Amber McLedon, Applications Director
Cynthia Carmom, PMO Director/Acting Student Systems Director
Date:
Date:
Date:
Project Sponsor
Jane Smith, Project Sponsor
Date:
image1
>Project Scenario
Project Scenario egatta University is a leader in both traditional education and career-path development, including in emerging fields. The university prides itself on staying on the leading edge of curriculum and degree programs, learning methodologies and instructional technologies, student services, and demonstrated student success. “The future is here and now,” the university’s president, Martha Yoon, likes to say. ,000 students at locations including the original campus in Augusta, Maine, and satellite campuses in Ventura, alifornia; Dayton, Ohio; and Hilo, Hawaii. n a typical term, approximately 0% of Regatta’s students take courses at a distance through the university’s online education hub. Enrollment growth has been strong, increasing by 4 to 8% each year for the last decade. I 2 A/R A/R I 4 C/I I A/R A/R 8 A/R A/R A/R A/R A/R A/R I A/R C/I A/R A/R A/R A/R R I A/R C 1.0 Student Degree Progress Project 1.1 Initiation 1.1.2 Project Management Plan 1.2 Planning 1.3.1.1 User Interface Mockup 1.3.1.2 Architectural Design – Main Application 1.3.2 Implementation 1.3.3.2 Test Scenarios 1.3.3.3 Integration Testing 1.3.4 Transition to Production 1.5 Project Closeout 1.3.3 Testing 1.3.3.1 Test Plan 1.3.2.1 Graphical Component Unit 1.3.2.2 Web View Unit 1.3.2.3 Backend Unit 1.1.1 Project Charter 1.3 Execution 1.2.1 Scope Definition 1.2.3 Scheduling (Gantt Chart) 1.3.1 Design 1.2.2 Budget Plan 1.4.1 Final Project Report 1.4.2 Project Reflections (Lessons Learned) 1.4 Controlling 1.4.1 Monitor Project Progress 1.4.2 Manage Deliverables 1.4.3 Assess and Manage Risks 1.3.1.3 Architectural Design – Backend High High Low Low Jane Smith John Doe Arthur Bowman Shila Cole Ana Fischer John Jones
R
Regatta serves approximately 8
C
I
4
You are a key member of the information technology team at Regatta, with a core specialization in student services. You are responsible for providing user-friendly interfaces connecting to a flexible, powerful information structure. Now you have a new project—working with colleagues to create a student degree progress tool that students will use for accurate, instant information on their progress toward program and degree completion. As you may imagine, this tool is eagerly awaited by a variety of stakeholders, including Regatta academic advisors and the Office of Enrollment Management, as tracking and communicating student progress toward degree completion is vital for retention. “We need a tool that will be easy to use but also accurate. No misinformation!” your team manager says.RACI Chart
Steps will be highlighted if A and R are not assigned.
R:
Does the step
RACI Chart
A:
Accountable for the step
C:
Consulted with before the step
I:
Informed when the step is completed
Project:
Student Degree Progress
DEPARTMENT
Information Technology
STEP
DESCRIPTION
Jane Smith
John Doe
Arthur Bowman
Shila Cole
Ana Fischer
John Jones
1
Create the project charter
A/R
Develop the project management plan
3
Define the project scope
C
C/I
I
Create a formal budget and budget plan
A/R
I
5
Fill in a Gantt chart with the project schedule and milestones
A/R
I
C/I
I
I
6
Develop a user interface mockup for review
7
Create the architectural design for the front end of the application (user-facing)
Create the architectural design for the back end of the application (for data processing)
9
Develop the graphic user interface (GUI) for the degree tracker
10
Develop the web code to receive data from the back end and place data within the GUI
11
Develop the back-end code to process data and send it to the web application
12
Create a defined test plan for all system components
C/I
C/I
13
Test the scenarios defined in the test plan for proper application behavior
R
R
14
Perform integration testing to ensure that the front-end components and back-end components speak to each other as well as integrate seamlessly with the rest of the web application
R
R
15
Transition web application into production environment (go-live)
A/R
16
Monitor project progress throughout its life cycle
I
17
Manage project deliverables for records and hand-off
I
18
Assess and manage risks throughout the project life cycle
R
R
19
Develop the final project report
A/R
I
20
Perform project reflections
C
C
Work Breakdown Structure (WBS)
Risk Matrix
Project Risk
Likelihood
Implications
There is a risk that severe weather in Sailcloth, Maine (the main campus that houses the development team), will close the campus and impact progress.
Medium
There is a risk that the ambiguity in the project scope (it only defines “graphical element” but not what type) will lead to requirement changes by the stakeholder during development, affecting both the budget and schedule.
High
There is a risk that sign-off on project deliverables (charter, Gantt chart, product approval, etc.) from project sponsors and stakeholders exceeds the allotted time. This decision delay will impact the progress schedule.
Low
There is a risk for rollout issues when deploying to production due to complexity of merging code with the “go-live” of another project on the same system.
Two projects are currently being developed at the same time in the same code base. Delays to the secondary project will cause delays to the Student Progress go-live.
The student portal where the project will be deployed is a high-availability system and is expected to be accessible for students 24/7. There is a risk that the large number of changes occurring during go-live could take the system offline, temporarily impacting system availability.
There is a risk that an interpersonal conflict will arise within the team, impacting the human resources assigned to the project and potentially impacting the allotted schedule.
Team Member Info
Role
Name
Role Description
IT 32
8
Final Project Guidelines and Rubric
Overview
The final project for this course is the creation of a risk analysis and mitigation memo.
We all work on projects whether at work, at school, or around the house. Some projects are small and can be completed quickly; however, some take time,
planning, and preparation. How can you make sure that a project is completed once it is started? How do projects in information technology really run behind
the scenes? Project management provides a structured method to move through a project from the time it is created until the time it is completed and all the
steps in between.
In this project, imagine that you are team member for an IT development project. Your team has identified several risks the project faces that could negatively
impact its outcome. You have been tasked with selecting one of those risks and analyzing it in order to determine the best solution to mitigate the risk and
determine how your solution will affect the overall project. You will write a professional email memo to your project manager, with supporting documentation
as attachments. The email will explain your analysis, recommendations, and the impact of those recommendations. Your thorough analysis is critical to the
project manager to help him or her make an informed decision about how to move the project forward. Use this reference as an example, to assist you with
writing a business memo.
In this assignment, you will demonstrate your mastery of the following course outcomes:
Explain the relationship between an information technology project’s scope, budget, and schedule to determine how they impact one another
Develop industry-appropriate messaging for communicating an information technology project’s status and needs to project stakeholders
Determine key information-technology considerations for informing project risk-management response strategies
Examine project management documents for key project data to promote successful information technology projects through development, testing, and
production
Prompt
Your email memo and attachments should be drafted in a Word document with the project charter, RACI chart, and Gantt charts included in an appendix. In
your memo, you will describe background information about the project that you are working on, detail information about a specific project risk, and propose a
recommended risk mitigation strategy to your leadership team.
Your memo will make use of the following project scenario:
https://owl.purdue.edu/owl/subject_specific_writing/professional_technical_writing/memos/sample_memo.html
Regatta University is a leader in both traditional education and career-path development, including in emerging fields. The university prides itself on staying on
the leading edge of curriculum and degree programs, learning methodologies and instructional technologies, student services, and demonstrated student
success. “The future is here and now,” the university’s president, Martha Yoon, likes to say.
Regatta serves approximately 8,000 students at locations including the original campus in Augusta, Maine, and satellite campuses in Ventura, California; Dayton,
Ohio; and Hilo, Hawaii. In a typical term, approximately 40% of Regatta’s students take courses at a distance through the university’s online education hub.
Enrollment growth has been strong, increasing by 4 to 8% each year for the last decade.
You are a key member of the information technology team at Regatta, with a core specialization in student services. You are responsible for providing user-
friendly interfaces connecting to a flexible, powerful information structure. Now you have a new project—working with colleagues to create a student degree
progress tool that students will use for accurate, instant information on their progress toward program and degree completion. As you may imagine, this tool is
eagerly awaited by a variety of stakeholders, including Regatta academic advisors and the Office of Enrollment Management, as tracking and communicating
student progress toward degree completion is vital for retention. “We need a tool that will be easy to use but also accurate. No misinformation!” your team
manager says.
Your memo will analyze and recommend mitigation strategies for one project risk. The risk you choose to focus on must come from the list of project risks in
the provided Project Management Documents Excel worksheet. They are located in the tab titled Risk Matrix.
Specifically, the following critical elements must be addressed in your memo:
I. Introduction: Using the Student Degree Progress Project Charter document, the RACI chart in the Project Management Documents workbook, and the
Gantt Chart document as guides, provide background information on the project you are working on.
A. Describe the purpose of the project and the end objective, including where this information is documented.
B. Identify the key stakeholders involved in the project, including an explanation of their roles and responsibilities.
C. Describe your own role and responsibilities on the project team, citing specific information from the project’s Gantt chart.
D. Explain the triple constraint relationship between the project’s scope, schedule, and budget. Support your response with examples from the
project materials and your experience in adding the new element to your project during Milestone Two.
II. Project Risk: Select a risk from the list in the Project Management Documents workbook. Using these project management documents as guides,
provide detailed information about the specific project risk.
A. Explain why this risk requires attention. Support your response with examples from the project management documents.
B. Describe any dependencies within the project that may be affected by this risk. Provide specific examples from the project management
documentation to support your response.
C. Explain the implications for the project within the context of the triple constraint if this risk is not addressed.
http://snhu-media.snhu.edu/files/course_repository/undergraduate/it/it328/it328_student_degree_progress_project_charter x
http://snhu-media.snhu.edu/files/course_repository/undergraduate/it/it328/it328_project_management_documents.xlsx
http://snhu-media.snhu.edu/files/course_repository/undergraduate/it/it328/it328_gantt_chart.mpp
III. Risk Mitigation: Using all available project documents as guides, recommend a risk mitigation strategy.
A. Explain the steps that need to be taken in order to mitigate the identified risk.
B. Explain in detail how the proposed mitigation strategy will affect the project. Include any tradeoffs that must be made to accommodate the
mitigation strategy, and consider the triple constraint and any other variables that you deem important.
C. Defend why your proposed mitigation strategy is the best course of action for the project team.
IV. Conclusion: Summarize the project needs in your project risk and mitigation proposal for your stakeholders. What are the most important pieces of
information to take away?
V. Communication: Your risk mitigation email memo attachments will be evaluated based on the following elements:
A. Develop email communication in a clear and professional way, using language appropriate for the audience of stakeholders.
B. Attach supporting documentation to aid in the communication of your mitigation strategy.
Milestones
Milestone One: Introduction, Stakeholders, and Roles
In Module Two, you will compose a brief project description that summarizes the student degree progress project, including its purposes, objectives, and how
and where to find further information about it. This milestone will be graded with the Milestone One Rubric.
Milestone Two: Your Role and the Triple Constraint
In Module Three, you will take on one of the three technical roles on the project team. Using the Gantt chart, you will first describe the work assigned to your
role. You will also list work performed by others that must be done prior to the tasks assigned to your role. In this milestone, you will also consider the
implications for the project restraints with the addition of a new project component that you will create. This milestone will be graded with the Milestone Two
Rubric.
Milestone Three: Project Risk and Mitigation
In Module Five, you will draft two key sections of your final project. In this milestone, you will identify and describe a project risk from the list of risks included in
the Project Management Document Excel workbook, then you will recommend risk mitigation strategies. This milestone will be graded with the Milestone
Three Rubric.
Final Submission: Risk Analysis and Mitigation Memo
In Module Seven, you will submit your final project. It should be a complete, polished artifact containing all of the critical elements of the final product. It should
reflect the incorporation of feedback gained throughout the course. This submission will be graded with the Final Project Rubric.
Deliverables
Milestone Deliverable Module Due Grading
One Introduction, Stakeholders, and Roles 2 Graded separately; Milestone One Rubric
Two Your Role and the Triple Constraint 3 Graded separately; Milestone Two Rubric
Three Project Risk and Mitigation 5 Graded separately; Milestone Three Rubric
Final Submission: Risk Analysis and
Mitigation Memo
7 Graded separately; Final Project Rubric
Final Project Rubric
Guidelines for Submission: Your email memo and attachments should be 2 to 4 pages in length with double spacing, one-inch margins, 12-point Times New
Roman font, and adherence to the latest edition of APA formatting.
Critical Elements Exemplary (100%) Proficient (85%) Needs Improvement (55%) Not Evident (0%) Value
Introduction:
Purpose
Meets “Proficient” criteria and
description demonstrates an
advanced ability to extract
accurate information from
project documentation
Describes the purpose of the
project and the end objective,
including where this information
is documented
Describes the purpose of the
project and the end objective,
but description is cursory,
contains inaccuracies, or does
not include where this
information is documented
Does not describe the purpose of
the project and the end objective
6
Introduction:
Stakeholders
Meets “Proficient” criteria and
response demonstrates a
sophisticated awareness of the
roles and responsibilities of each
stakeholder within the project
team
Identifies the key stakeholders
involved in the project, including
an explanation of their roles and
responsibilities
Identifies the key stakeholders
involved in the project, but
explanation is cursory, contains
inaccuracies, or does not include
stakeholders’ roles and
responsibilities
Does not identify the key
stakeholders involved in the
project
6
Introduction:
Role and
Responsibilities
Meets “Proficient” criteria and
cited information is especially
well-suited for supporting the
description of own role and
responsibilities within the project
team
Describes own role and
responsibilities on the project
team, citing specific information
from the project’s Gantt chart
Describes own role and
responsibilities on the project
team, but description is cursory,
contains inaccuracies, or lacks
specific reference to the project’s
Gantt chart
Does not describe own role and
responsibilities on the project
team or cite specific information
from the project’s Gantt chart
6
Introduction:
Triple Constraint
Meets “Proficient” criteria and
explanation demonstrates a
complex grasp of the implications
of the triple constraint
relationship on the project
Explains the triple constraint
relationship between the
project’s scope, schedule, and
budget, supporting response
with examples from the project
materials and experience in this
course
Explains the triple constraint
relationship between the
project’s scope, schedule, and
budget, but explanation is
illogical, contains inaccuracies, or
is not supported by examples
from the project materials and
experience in this course
Does not explain the triple
constraint relationship between
the project’s scope, schedule,
and budget
8
Project Risk:
Requires
Attention
Meets “Proficient” criteria and
explanation demonstrates a
complex grasp of the project
needs
Identifies risk and explains why
the risk requires attention,
supporting response with
examples from project
management documents
Identifies risk and explains why
the risk requires attention, but
explanation is illogical, contains
inaccuracies, or does not include
example from project
management documents
Does not identify risk and explain
why the risk requires attention
8
Project Risk:
Dependencies
Meets “Proficient” criteria and
description demonstrates a
complex grasp of the
dependencies within a project
Describes any dependencies
within the project that may be
affected by the risk, including
support from project
management documentation
Describes any dependencies
within the project that may be
affected by the risk, but
description is illogical, contains
inaccuracies, or does not include
support from project
management documentation
Does not describe dependencies
within the project that may be
affected by the risk
6
Project Risk:
Implications
Meets “Proficient” criteria and
explanation demonstrates a
sophisticated awareness of
possible risk results
Explains within the context of the
triple constraint the implications
for the project if the risk is not
addressed
Explains the implications for the
project if the risk is not
addressed, but explanation is
illogical or cursory or is not
within the context of the triple
constraint
Does not explain the implications
for the project if the risk is not
addressed
8
Risk Mitigation:
Mitigate
Meets “Proficient” criteria and
explanation demonstrates a
sophisticated awareness of steps
needed to mitigate the identified
risk
Explains the steps that need to
be taken in order to mitigate the
identified risk
Explains the steps that need to
be taken in order to mitigate the
identified risk, but explanation is
illogical, cursory, or contains
inaccuracies
Does not explain the steps that
need to be taken in order to
mitigate the identified risk
8
Risk Mitigation:
Affect
Meets “Proficient” criteria and
explanation makes cogent
connections between important
project variables and the
proposed risk mitigation strategy
Explains in detail how the
proposed mitigation strategy will
affect the project, considering
the triple constraint and any
other variables deemed
important including any tradeoffs
that must be made to
accommodate the mitigation
strategy
Explains how the proposed
mitigation strategy will affect the
project, but explanation lacks
detail, is illogical, contains
inaccuracies, does not consider
the triple constraint and any
other variables deemed
important, or does not include
tradeoffs that must be made to
accommodate the mitigation
strategy
Does not explain how the
proposed mitigation strategy will
affect the project
8
Risk Mitigation:
Best Course of
Action
Meets “Proficient” criteria and
defense makes cogent
connections between the
proposed mitigation strategy and
the project goals
Defends why the proposed
mitigation strategy is the best
course of action for the project
team
Defends why the proposed
mitigation strategy is the best
course of action for the project
team, but response is cursory or
illogical or contains inaccuracies
Does not defend why the
proposed mitigation strategy is
the best course of action for the
project team
8
Conclusion Meets “Proficient” criteria and
summary demonstrates an
advanced ability to distill project
information
Summarizes the project needs for
stakeholders
Summarizes the needs for
stakeholders, but summary is
unclear or missing key
components
Does not summarize the project
needs for stakeholders
8
Communication:
Professional
Meets “Proficient” criteria and
email demonstrates an advanced
ability to appropriately tailor
communication to a specified
audience
Develops email communication
in a clear and professional
manner, using language
appropriate for the audience of
stakeholders
Develops email communication
in a professional manner, but
language is not appropriate for
the audience of stakeholders or
information is not clear
Does not develop email in a clear
and professional manner using
language appropriate for the
audience of stakeholders
8
Communication:
Documentation
Meets “Proficient” criteria and
supporting documentation is
especially well-suited to aid in
the communication of the
proposed mitigation strategy
Attaches supporting
documentation to aid in the
communication of the mitigation
strategy
Attaches supporting
documentation to aid in the
communication of the mitigation
strategy, but documentation is
incomplete or contains
inaccuracies
Does not attach supporting
documentation to aid in the
communication of the mitigation
strategy
8
Articulation of
Response
Submission is free of errors
related to citations, grammar,
spelling, syntax, and organization
Submission has no major errors
related to citations, grammar,
spelling, syntax, or organization
Submission has major errors
related to citations, grammar,
spelling, syntax, or organization
that negatively impact readability
and articulation of main ideas
Submission has critical errors
related to citations, grammar,
spelling, syntax, or organization
that prevent understanding of
ideas
4
Total 100%
- IT 328 Final Project Guidelines and Rubric
Overview
Prompt
Milestones
Milestone One: Introduction, Stakeholders, and Roles
Milestone Two: Your Role and the Triple Constraint
Milestone Three: Project Risk and Mitigation
Final Submission: Risk Analysis and Mitigation Memo
Deliverables
Final Project Rubric
5
Milestone 2
Student name
Institution affiliation
Course name
Date submitted
Milestone 2
Technical role
The effective part for this project is as a system analyst. The analyst is mandated to study, plan and implement fresh information structures. The individual also assesses the appropriateness of the information structure and ensures the project attains the expected outcome and objectives. The system analyst may need an ample understanding of the programming language and hence is not on the front line when coding for the system itself. The analysts liaise with the users, programmers and software vendors. Some typical responsibilities include examining the current systems, engaging with the users (requirements gathering), producing specifications for modified systems, and liaising with IT personnel to develop and implement new systems (Portland Community College, 2023). The system analyst has various roles and tasks that must be performed, including preparing and evaluating workflow and gathering, collecting and analyzing data. After the mock-up is complete, the analyst must have sufficient skills to test the system. In the project’s lifespan, the analyst will be needed to train the end users on how the system functions. The training can take a daylight, dependent on the system’s convolution.
Each task done by the system analyst can only be completed when the predecessors complete other tasks. Firstly, the system analyst needs to design the structure itself. This necessitates ensuring that the Gantt chart is established so that the personnel can see the amount of time every task will take, hence making sure that the design is ready to go to the programmers to develop a mock system. Once the system design is ready, there need to be involved with the programmers to understand the design needed for the project. It is essential to test the mock-up to ensure it meets the client’s needs and preferences and other key project members to ensure everyone understands the system functionality. When the existing system is complete, the system analyst is mandated to ensure the system has no issues- This is why the primary tasks must be completed to ensure the project meets the needed objectives. The last step involves data gathering throughout the project’s course, hence the analysts’ essentiality to ensure that the learners get information from the system.
Triple constraint matrix
An essential additional element that arises within the project is to have a system that looks back at students’ records over the new system’s timeframe. The additional element will ensure the system has a feature that allows past learners to access their info. The project does not permit any extra funding. Still, it is an element that can enhance system efficiency and offer room for old students to access files from the older database. The additional element is a simple engagement that would not affect the project timeline. The elements can take between two days and three days at maximum.
The additional element necessitates increasing the testing time and developing the system. The task also can be completed without additional funding. There is no need for a major timeline alteration that touches on the project’s time frame after the creators establishes a consumer interface for the degree trailer. The programmers can establish a tactic to access older data and augment it to the new interface- it can take a projected three days. After completion of the interface, the added element offers an opportunity to implement the system quickly, allow effective testing, and ensure no issues arise during the system implementation phase. The major issue likely to arise is time, as all the tasks must be completed within the given time frame. The additional element will allow older students easy access to information, benefiting from the new system.
References
Portland Community College. (2023).
Systems analyst. Portland Community College. Retrieved January 17, 2023, from https://www.pcc.edu/hr/employment/management-jobs/systems-analyst/#:~:text=Typical%20responsibilities%20include%3A%20maintaining%20software,lower%20level%20information%20technology%20staff.
5
Milestone one
Student name
Institution affiliation
Course name
Date submitted
Milestone one
Introduction
The project aims to establish a program that will permit learners to trail their academic advancement. The scholar degree evolvement project must generate a more manageable web format that helps learners view their college education progress. The tool will help learners to correctly and promptly access the info on their advancement towards program and unit accomplishment. The website will offer learners a safe way to browse indispensable information without the concern of intruders gain access to their data. The project will also support multiple browsers and all graphical elements provided by the service provider. It will have a protected website’s back-end to help effectively collect all the data the learners need without any access problems.
The project’s end objective is to offer a service tool where learners can securely access the needed info about their advancement within the school program they are following. The project must ensure that it houses all relevant information that learners need to keep track of their education progress in their classes and overall program. The project’s objective is to ensure that every learner can access the information, hence the essentiality of a back-end. The info utilized in this project is derived from the student charters created for this project:
Student Degree Progress Project Charter
. The document offers direction on the info enclosed in the learner degree advancement tool that will get introduced from a scholar info system attained from records input into the structure by hand or automatically. The project’s outcomes depend on the charter’s information, which summarises the project’s aim and desired achievements. Effective implementation of the project will help learners view their progress towards completing their academic education.
Key stakeholders and roles
The primary stakeholders for the project include team supporters Shila Cole, Ana Fischer, and John Jones, Arthur Bowman as the core stakeholder, John Doe as the manager and Jane Smith as the project sponsor.
Every stakeholder plays an essential role that ensures the project’s success. Derakhshan, Turner & Mancini (2019) establishes that stakeholders are crucial to project governance and hence need to have a comprehensive framework that outlines the roles, associations and situations of the internal and external participants in the authority arrangement. The sponsor is the individual that is held accountable for the project. The sponsor is tasked to present the business case, approve the project’s budgeting process and estimates, appoint the project manager and have the authority to deal with arising team issues or cancel the project. The project manager has many tasks to ensure that he carries his role. Some duties include involvement in the budget process, creating charts and schedules for the team, and engaging in risk analysis, resource planning, cost assessment and scope definition. The core stakeholder also plays an integral role in the project’s success and is tasked to ensure that the project fits the company’s strategy. The core stakeholder also offers needed details about the project’s requirements and engages in the financial planning process. The individual is also tasked with ensuring effective resource distribution. Lastly, the team members are people that work on the project directly. In other words, they are the lifeblood of the project and hence engage in task completion in the provided time frame.
The various stakeholders play a significant role in the project from the planning and implementation phases. The sponsor acts as the group’s champion, where the individual is mandated to ensure that other stakeholder’ views are heard, ensuring effective communication among all stakeholders. The sponsor also appoints the manager, who must provide the project’s framework adhered to by the team members. The manager also needs to ensure that resources are availed on time to prevent delay. The manager also sets the milestones for the team members. This aims at helping the team members set needed targets and ensure they achieve them at a given time. The project manager ensures that everything is set for the commencement of the project and communicates with the team members in the entire project phase to ensure results are achieved. The core stakeholder needs to ensure the project follows the company’s expectations. This involves ensuring that the project adheres to the requirements to attain objectives or outcomes.
Reference
Derakhshan, R., Turner, R., & Mancini, M. (2019). Project governance and stakeholders: a literature review.
International Journal of Project Management,
37(1), 98-116.
6
Milestone 3
Student name
Institution affiliation
Course name
Date submitted
Milestone 3
Project risk
Risks in the project include any uncertain occurrence that may or may not happen during the project management process. The risks can offer negative or positive impacts on the progress towards the project’s objectives (Qazi et al., 2018). Depending on the project, many risks may arise, and one can outweigh the other. In this project, the risk of rollout issues can be a more significant issue than others. The risk arises during deployment to assembly due to the convolution of amalgamation code with the ‘go-live’ of a new project in the same structure. The project involves creating a fresh user interface; numerous things can occur throughout the launching phase. The risk needs more attention than other risks, as any wrong line of code can lead to the project’s complete stop. This will lead to increased costs and more time, forcing the team to go through the entire code to find the issues. This process will make the group associates spend much stretch on the venture, impacting the calendar. The entity will also need to use more cash to ensure the workers are motivated to complete the project hence the need for more resources.
The realization of this risk can make the entire project’s schedule incontrollable because of the various dependencies that depend on having the right code and it is delivered on schedule. One of the dependent tasks that will be impacted involves the development of a user interface mockup for review. This task can be put on grasp or pressed back in the venture life cycle. The issue is attributed to having a wrong code, hence the need to go back and identify where the problem lies, wasting more time in this task completion. Another dependent task that will be impacted is the creation of the website’s front end. The identified threat will make the group affiliated to go back and recreate the tasks of the UI that the wrong code will have negatively impacted. This wastes time as a need to rewrite the front end and ensure it is effectively functional, adding costs for the stakeholder. A bad code impacts the front and back end and hence needs to correct with a new interface. If this risk is attended to, it can lead to clarity among the learners using the interface hence troubles finding the needed information. The issue can also make GUI develop issues, hence impacting its effectiveness. It is crucial to ensure the database is easily accessible for the learners and staff members.
The triple constraint looks at the three most substantial restrictions on any project. This includes the scope, schedule and costs. It is essential as it helps the team adapt to the changing conditions that the project faces daily and in its development process (Kerzner, 2022). The identified risk will affect the three categories. First, the risk will make the investors to use more cash on the venture. The project has its set budget limits; hence additional costs inconvenience the stakeholders and can negatively lead to a possible shutdown of the project. Secondly, the risk will impact the project’s timeline or schedule. Any issue that affects the project will bring about various problems with the Gantt chart compelling the manager to engage in various steps aiming to recover the chart. This aims to ensure the project is completed on time or to engage the stakeholders and ask for a time extension. Lastly, the risk will impact the project’s scope. This arises from more tasks added to the schedule hence more tasks that need timely completion. This creates scope creep hence affecting the scope and time.
Risk mitigation
A risk mitigation strategy aims at lessening the impacts of potential risks. It involves the development of a plan to manage, eliminate or limit the setbacks as much as possible. There is also a need to monitor progress and evaluate the needed modifications if necessary (Beecham et al., 2021). The proposed mitigation steps are aimed at keeping the project on track. The leading step involves taking a small amount of time and double-checking the project’s entire code. This step will help ensure that the created code is effective by checking if there is any issue with the algorithm itself. This includes analyzing the code with every novel line of code to ensure nothing is tossing the venture in a loop. The step can involve a small quantity of extra time in the development stage but will save much time that could be used when trying to find the incorrect line of code. The code testing takes little time and will not impact the project’s scope. Another step is allowing every team to test the code and software they create. The step will guarantee the algorithm and the software has no concerns with functioning together with other constituents utilized in the venture.
The proposed mitigation steps aim to ensure the project does not face any delay towards its completion by preventing the risk occurrence. However, they can add unwarranted stretch to the venture timeline, generating scope creep, which can impact the venture’s completion stage. This arises from checking the code or software in individual steps to prevent any issues. The constant testing can add unsolicited stretch to the venture hence slowing down other responsibilities that must be completed as per the schedule. The steps are improbable to impact the venture in the end; hence it is a tradeoff as only a little stretch is taken away from the venture itself. The steps also help avoid going back to check the code to identify the underlying issue, either small or big. It is a better tradeoff in the long run as testing the code or the software with the other teams ensures that when the project ‘goes live’, everything is working well, contributing to the project’s success. However, the step can slow things down, affecting the teams as they take too much time to test their code and software with the other teams. If everything is done correctly, then the steps can prevent the risk from occurring.
The proposed risk mitigation strategy is the best action to address the rollout risk. The strategy can help cut down the money used to fix issues that may arise, although it can add time to the project. Testing the algorithm or software can lessen the threats of developing problems in other portions of the venture. The issues can be further prevented by assessing with further portions of the venture to ensure the creation rolls out in time. The coding functionality can be impacted by minor issues, messing up the entire project and creating more time. When the proposed steps are enacted, the issue may not arise, ensuring the stakeholders are happy with the project. If the steps need a little time, they can help cut back spending more money on the project hence helping the project in the long term.
References
Beecham, S., Clear, T., Lal, R., & Noll, J. (2021). Do scaling agile frameworks address global software development risks? An empirical study.
Journal of Systems and Software, p.
171, 110823.
Kerzner, H. (2022).
Project management metrics, KPIs, and dashboards: a guide to measuring and monitoring project performance. John Wiley & Sons.
Qazi, A., Quigley, J., Dickson, A., & Kirytopoulos, K. (2018). Project Complexity and Risk Management (ProCRiM): Towards modelling project complexity-driven risk paths in construction projects.
International journal of project management,
34(7), 1183–1198.
Order an Essay Now & Get These Features For Free:
Turnitin Report
Formatting
Title Page
Citation
Outline
