ITProject Managment
>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
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
IT 328 Final Project Milestone One Guidelines and
Rubric
Introduction, Stakeholders, and Roles
Overview: In Milestone One, you will begin your progress toward successful completion of your final project, the risk analysis and mitigation memo. It is
important to note that this milestone addresses Section I, Parts A and B of your final project. For purposes of this activity, these items have been further broken
down in the milestone activity than they will be in the final version of your project. This is meant to help guide you through all the aspects of this point in your
learning experience.
You will start by reviewing the project scenario and some key documents that contain information about the student degree progress project that are provided
for you in the Project Management Documents Excel workbook. Your work on this milestone will help you successfully develop several elements of Section I of
the final project, including discussion of the purpose of the student degree progress project, its objectives, the location of information about the project, and the
roles and responsibilities of project team members. Use this reference as an example, to assist you with writing a business memo.
Prompt: As you go through these documents, think of yourself as a member of this team. In the following activity, you will use those documents to make key
connections. While the project charter is in its own Word document, the Student Degree Progress Project Charter, the RACI and WBS charts are included in the
Excel workbook that you will use to complete this assignment. Go through each labeled tab to access each key piece of information. You will continue to refer
back to these documents throughout your work on the milestones leading to your final submission. You may reference the elements in this document to support
your answers, using text and screenshots as needed.
Your submission for Milestone One should address the following critical elements:
I. Introduction to the Project: Keep this area as concise as possible (1 to 2 paragraphs) while ensuring you fully accomplish the following:
Explain the purpose of the student degree progress project.
Describe the end objectives or project outcomes.
Explain where this information is documented in the artifacts you are using and provide an attachment of the specific documentation you used
to obtain this information. Remember, your email memo will want to refer your reader very specifically to key areas in the attachments you
provide so that your leadership team can dig into it as needed.
II. Key Stakeholders and Roles: In this area, you will describe all of the project roles in a detailed paragraph. These descriptions of each team member’s
role are important and are often used for stakeholder audiences. For instance, this information may be used when the project work structure is
presented to department management for comment and approval. You may organize this area as you wish; as a rule of thumb, you will likely need a
complete paragraph to fully address the following for each role:
List the team members identified in the project documentation and their project roles accurately.
Describe the relevant function or general behavior of each role specific to this project.
Explain the significance of each role specific to the phases of the project that the role is involved in.
List the assigned tasks for each role.
http://snhu-media.snhu.edu/files/course_repository/undergraduate/it/it328/it328_project_management_documents.xlsx
https://owl.purdue.edu/owl/subject_specific_writing/professional_technical_writing/memos/sample_memo.html
http://snhu-media.snhu.edu/files/course_repository/undergraduate/it/it328/it328_student_degree_progress_project_charter x
Rubric
Guidelines for Submission: Milestone One must be submitted as a Word document with double spacing, one-inch margins, 12-point Times New Roman font, and
adherence to the latest edition of APA formatting. Your submission should be clear, coherent, concise, and free of errors.
Critical Element
Attempted With Minimal or No Functional
Issues (100%)
Attempted With Significant Functional Issues
(75%)
Not Evident in Submission (0%) Value
Introduction:
Purpose
Clearly and concisely explains the purpose of
the project with minimal or no issues
Explains the purpose of the project, but
explanation may be inaccurate, unclear, or too
long for the occasion
Does not explain the purpose of the project
12.86
Introduction: End
Objectives
Clearly and concisely explains the end
objectives or project outcomes with minimal
or no issues
Explains the end objectives or project
outcomes, but explanation may be inaccurate,
unclear, or too long for the occasion
Does not explain the end objectives or project
outcomes
12.86
Introduction:
Documentation
Clearly and specifically explains where
information is documented
Explains where information is documented but
explanation may be inaccurate, unclear,
lacking in specificity, or not supported by the
artifacts in the attachment
Does not explain where information is
documented
12.86
Stakeholders/Roles:
Members
Lists the team members and their project roles
with minimal or no issues related to accuracy
Lists the team members and their project roles
but with significant issues related to accuracy
Does not list the team members and their
project roles
12.86
Stakeholders/Roles:
Relevant Function of
the Role
Describes the relevant function or general
behavior of each role with minimal or no
issues related to accuracy
Describes the relevant function or general
behavior of each role but with significant
issues related to accuracy
Does not describe the relevant function or
general behavior of each role
12.86
Stakeholders/Roles:
Significance
Explains the significance of the role specific to
the phases of the project that the role is
involved in with minimal or no issues related
to accuracy
Explains the significance of the role specific to
the phases of the project that the role is
involved in but with significant issues related
to accuracy
Does not explain the significance of each role
specific to the phases of the project that the
role is involved in
12.86
Stakeholders/Roles:
Assigned Tasks
Lists the assigned tasks for each role with
minimal or no issues related to accuracy
Lists the assigned tasks for each role but with
significant issues related to accuracy
Does not list the assigned tasks for each role 12.86
Articulation of
Response
Submission has no major errors related to
grammar, spelling, syntax, or organization
Submission has major errors related to
grammar, spelling, syntax, or organization that
negatively impact readability and articulation
of main ideas
Submission has critical errors related to
grammar, spelling, syntax, or organization that
prevent understanding of ideas
9.98
Total 100%
- IT 328 Final Project Milestone One Guidelines and Rubric Introduction, Stakeholders, and Roles
Rubric
Order an Essay Now & Get These Features For Free:
Turnitin Report
Formatting
Title Page
Citation
Outline
