Milestone 2

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.