In this assignment, you will begin your work with the course case scenario involving the student degree progress project. You will begin by examining three key project documents: the project charter, the RACI chart, and the WBS chart. The project charter is in the
Student Degree Progress Project Charter Word Document
document, while the RACI and WBS charts are included in the
Project Management Documents Spreadsheet
. This workbook has multiple tabs.
Using this information, you will address the questions and critical elements in the Milestone One Guidelines and Rubric document. 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 is the type of communication project that team members typically provide for stakeholders.
Your work on this milestone will help you prepare to compose sections of Part I of your final project, which introduces the student degree progress project and discusses roles and responsibilities within the project team.
To complete this assignment, review the
Milestone One Guidelines and Rubric PDF
document.
******* You missed the key requirements for this assignment which was to analyze and show the work on the Gantt chart. Please let me know if you want to do that work and submit and i’d be happy to reassess. Please send me an email if you choose to do that..otherwise see my sample solution
IT 328 Milestone Two Guidelines and
Rubric
Your Role and the Triple Constraint
Overview: In Milestone One, you began your progress toward successful completion of your final project, the risk analysis and mitigation memo. You will now
continue this preparatory work in Milestone Two by focusing on a technical role. You will consider how the tasks assigned to the role fit into an integrated
schedule found in a Gantt chart. You will then work with the triple constraint, showing how changes to it may impact the project, while proposing a new project
element that will enhance user experience with the student degree progress tool. It is important to note that this milestone addresses Section I, Parts C and D of
your final project. For purposes of this activity, these items have been further broken down than they are in the final version of your project; this will help guide
you through all the aspects of this point in your learning experience.
As you are beginning to see, working within project budgets and staying on schedule typically requires a team effort, as work tasks must be completed efficiently
and often in the correct order for the project to stay on track. Additions to the project and changes to the triple constraint may present opportunities or
potential obstacles. As a project team member, you need to adjust to changes to the project or to the triple constraint, identify and mitigate risks, and accurately
interpret or provide project information. While you will not engage with project risk and risk mitigation until your next milestone, this milestone presents an
opportunity to practice key skills related to understanding the project schedule and the triple constraint relationship in relation to the project’s scope, schedule,
and budget that will lay the foundations for the next steps in your final project.
Remember, as you go through these documents, you should be thinking of yourself as a member of this team. At this point, you have reviewed the project
charter (in its own separate Word document). You have reviewed the project scenario and RACI and WBS charts, which are included in the Excel workbook that
you used in Milestone One. To complete Milestone Two, you will need to examine an additional key piece of project information: the Gantt Chart file. As you will
see, the Gantt chart provides a thorough schedule that integrates the tasks assigned to project team members. Such a synchronization of tasks is typical in an IT
project, and part of the work of any team member is interpreting this schedule and performing tasks in the correct order. You will continue to refer back to these
documents throughout your work on the milestones leading to your final submission. You may reference aspects of these documents to support your answers,
using text and screenshots as needed.
Prompt: The project charter and RACI chart have been approved by the Regatta University administration. Using the project Gantt chart, your team has started
working on the project schedule based on these documents. The team needs to make sure that each member understands his or her responsibilities based on
the schedule. There are three technical roles for this project:
Systems analyst—Shila Cole
Application developer—Ana Fischer
Backend systems analyst—John Jones
http://snhu-media.snhu.edu/files/course_repository/undergraduate/it/it328/it328_gantt_chart.mpp
First, select one of the above roles as your own.
Next, consider that you and your team have been thrown a curveball and were informed of the following by your manager:
The team has one more item it needs your help to complete. The project has been given an extra $10,000 to add a new element that enhances the project to the
student degree progress widget. With this $10,000 comes an additional week of time added to the schedule. (The distribution of tasks among the team during
that week does not impact the budget.)
Based on your understanding of the Gantt chart and how to read it, your submission for Milestone Two should address the following critical elements:
I. Your Technical Role in the Project Schedule: This section should be approximately 2 paragraphs in length. In this area, you will discuss your selected
role, responsibilities, and important predecessor tasks:
Select and identify a technical role from the approved list.
Summarize the responsibilities of this role.
Using specific information from the project’s Gantt chart, list where in the project schedule these responsibilities are assigned.
Explain why it is important that predecessor tasks are completed before your tasks are performed, citing specific information from the project’s
Gantt chart to support your explanation.
II. The Triple Constraint Matrix: This section should be approximately 2 to 3 paragraphs in length. In this area, you will refer to the new directive you have
been given by your manager. Provide a brief explanation of the new project element that you want to implement. Examples include live animation on
the progress bar or a callout box that opens when students hover on a hot spot and that provides more detailed information to the students. You will
use this experience to inform your understanding of the triple-constraint relationship between the project’s scope, schedule, and budget.
Clearly describe the additional element you propose, including how your feature alters the project timeline. For instance, will this addition to
the project add more testing time or increase development time?
Use the Gantt chart and the Microsoft Project Tutorial document to appropriately place the new tasks for your feature. These additional tasks
should be inserted during the execution process steps (such as close to the development tasks or increasing the testing time). Be sure to update
any predecessors that may have changed with the newest addition and to assign each new task to the appropriate team member. In the Gantt
chart, highlight the task that you have added to make it easy for your instructor to find. Refer to the tutorials and resources provided to you in
this module to help you with this task. You will submit this element as a separate Microsoft Project file.
Explain how the addition of this new element may alter the project timeline.
Explain how a change in the triple constraint of schedule, cost, and scope allows for this project addition to occur based on your experience in
this activity.
http://snhu-media.snhu.edu/files/course_repository/undergraduate/it/it328/it328_microsoft_project_tutorial
Rubric
Guidelines for Submission: Milestone Two should 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. Also submit your updated Microsoft Project file.
Critical Element
Attempted With Minimal or No Functional
Issues (100%)
Attempted With Significant Functional
Issues (75%)
Not Evident in Submission (0%) Value
Technical Role Selects and identifies a technical role from
the approved list
Selects a role, but role is not clearly identified
or may not be on the approved list
Does not select or identify a project role
12.86
Responsibilities Summarizes with minimal or no errors the
responsibilities assigned to the selected
technical role
Summarizes the responsibilities, but
summary has major errors related to
accuracy, completeness, or clarity
Does not summarize the responsibilities
assigned to the selected technical role
12.86
Project Schedule Lists with minimal or no errors the areas of
the project schedule assigned to the
technical role’s responsibilities
Lists the areas of the schedule assigned to
the designated responsibilities but has major
errors related to accuracy or completion
Does not list the areas of the schedule
assigned to the designated responsibilities
12.86
Predecessor
Tasks
Explains with minimal or no errors why it is
important that predecessor tasks are
completed before own tasks are performed,
citing specific information from the project’s
Gantt chart
Explains the importance of predecessor task
completion, citing specific information from
the project’s Gantt chart, but has major
issues related to accuracy, completion, or
clarity
Does not explain the importance of
predecessor task
12.86
Additional
Element
Clearly describes with minimal or no errors
an additional project element, including how
the feature alters the project timeline
Describes an additional project element and
how the feature alters timeline, but
description has major issues related to
accuracy, completion, or clarity
Does not describe an additional project
element and how the feature alters timeline
12.86
Place New Tasks Places the new tasks for feature with minimal
or no errors
Places the new tasks for feature but has
major issues related to accuracy, completion,
or clarity
Does not place the new tasks for feature 6
Project Timeline Explains with minimal or no errors how the
addition of this new element may alter the
project timeline
Explains how the addition of this new
element may alter the project timeline but
has major issues related to accuracy,
completion, or clarity
Does not explain how the addition of the new
element may alter the project timeline
12.86
Project Addition Explains with minimal or no errors how a
change in the triple constraint allows for this
project addition to occur based on own
experience in this activity
Explains how a change in the triple constraint
allows for this project addition to occur
based on own experience in this activity but
has major issues related to accuracy,
completion, or clarity
Does not explain how a change in the triple
constraint allowed for the project addition
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
3.98
Total 100%
- IT 328 Milestone Two Guidelines and Rubric Your Role and the Triple Constraint
Rubric
>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
1
SNHU IT328 Milestone 2: Sample Solution and Grading Guide Rajiv Chhatwal
Key points to complete this milestone are shown below and follow the rubric. You should have covered them for
receiving full credit. Please do not copy- learn and use these ideas to fine tune your solution for the final. Thankyou.
Expectations: At the end of completing Milestone 2, I expected you to learn the following:
a) How to read a Gantt Chart. Understanding of tasks, predecessors and follower tasks and relationship between
tasks
b) How to modify a Gantt Chart by adding in new tasks (NPE project added to SDP)
c) Impact of task addition- does it change schedule, cost, time and do these fit within the provided constraints
(You may have chosen any role- For illustration I am carrying thru with the role of Ana Fischer)
1 Technical Role
Select and identify a technical role from the approved list
I have assumed the technical role of Ana Fischer who functions as the middleware application engineer on this project
team
2 Responsibilities
Summarizes with minimal or no errors the responsibilities assigned to the selected technical role
Name/Role Function Significance Assigned Tasks/Responsibility
Ana Fischer-
middleware
application
engineer
• Development and
programming
Informed during Planning
phase. Responsible for a large
part of the execution phase.
• User interface
• Front end design
• Develop GUI
• Test scenarios
• Test integration
• Go-live
• Mange risks
3 Project Schedule
Lists with minimal or no errors the areas of the project schedule assigned to the technical role’s
responsibility
Understand first how a Gantt chart records information. A sample of first few tasks is shown below:
Task
ID#
Task Name Duration
in days
Start Day End Day = (Start
day + Duration)
Predecessor (Task IDs
that precede the task)
Resource Name (all resources
responsible for the task)
Graphical Display
Now lets look at tasks assigned to Ana Fischer:
2
Tasks assigned to Ana Fisher (from the Resources column, Select only Ana Fischer)
Now describe these tasks briefly. You many enhance per your style but this core info needs to be present:
• Tasks 6,7,8 show me developing a user interface, creating an architectural design and then developing the GUI
• Task 10 shows me integrating the web code to the UI
• Task 13 show testing and task 14 collaborating with John and Shiela for integration testing.
• Task 15 involve moving the application into production
• Task 18- collaborate with the team to assess and review risk through project
Let’s review the predecessor tasks and their importance:
Task Predecessor Importance
6,7 5 This is driven by John, who needs to complete the project gantt, charter, docs etc.
9 6 Prior to development, I need complete the GUI design and architecture design tasks
10 7 Prior to development I need to complete the architecture design
13 9,10,11 Prior to test I need to complete development
14 13 Prior to moving to production, I need to complete testing
15 14 Prior to risk analysis I need to deliver the completed project
5 Additional Elements
Clearly describes with minimal or no errors an additional project element, including how the
feature alters the project timeline
The additional project element or the NPE requirement is to add a “download” feature while a user is in their account.
This would allow the user to view a chronological order of their taken and future courses, and then click on the
4 Predecessor Tasks
Explains with minimal or no errors why it is important that predecessor tasks are completed before own
tasks are performed citing info from projects Gantt chart
3
download button which would render this view in a pdf. We will need to add the University Logo, the detail of the user
and the courses and add pagination if the page extends beyond one page.
6 Places the new tasks with minimal or no errors
The “Add Download Button” feature will need the following tasks:
a) Provide complete requirement of the feature include typical test scenarios (1 day)
b) Design the GUI of the placement of all the elements of the users information (0.5 Day)
c) Code the GUI design and render into a page format which can be saved as a PDF (0.5 Day)
d) Test the feature with the provided scenarios (0.5 Day)
e) Integrate the code bases and then test the integrated projects (0.5 Day)
f) Move integrated project to Production (Already assigned on SDP project)
Thus total amount of time taken for this feature is ( 1 + 0.5 + 0.5 + 0.5 + 0.5 )= 3 Days
Now place these tasks on the project Gantt:
Observe that two new tasks have been added. Total addition of two tasks is 3 days.
Impact on overall schedule of the project is also 3 days.
Task 1 Added- 1 Days
Task (a) listed above
Task 2 Added- 2 Days
Task (b)+(c)+(d)+(e) listed above
Total impact on schedule is 3 days
4
7 Project timeline
Explains with minimal or no errors how the addition of this new element may alter the project
timeline
Please see the detailed chart and documentation listed above. As can be seen from the list of tasks needed for NPE,
there are two tasks added to the Gantt chart. The first is for 1 day and second for 2 days. Thus, the total impact on the
timeline due to impact of these tasks is 3 days.
Note: Its important that for us to see the reflection on the actual timeline due the addition of tasks, the newly added
tasks should be not just listed but integrated into the timeline. Here is an example on when you create a new task, you
can specify their predecessor and also the task to task relationship.
8 Project Addition
Explains with minimal or no errors how a change in the triple constraint allows for this project
addition to occur based on own experience in this activity
In the case presented, we are to analyze the impact of NPE on SDP. As shown earlier to complete NPE we identified a
total for five key tasks which were grouped and inserted in two specific locations on the SDP Gantt chart. The total
impact of these tasks is to extend the timeline by 3 days. One of the task is completed by the PM John Doe and the other
by application engineer Ana Fischer. The total impact of the NPE can thus be measured as:
Cost : Extra spend on John and Ana à ( John: 8 hrs@ 100/hr = $800, Ana: 16 hours @ $75/hr = $1200) = $2000
Time : Timeline extension à 3 Days
Scope : Managed à No issues
Since we have been allocated a period of 5 days and a budget of $10K for this successful integration, we are confident
the NPE can be completed within the provided constraints.
Order an Essay Now & Get These Features For Free:
Turnitin Report
Formatting
Title Page
Citation
Outline
