IT 328 Module Three Milestone Two
docx
keyboard_arrow_up
School
Southern New Hampshire University *
*We aren’t endorsed by this school
Course
328
Subject
Information Systems
Date
Dec 6, 2023
Type
docx
Pages
3
Uploaded by MajorTitanium846
Milestone Two Your Role and The Triple Constraint
Maleka Monono
Southern New Hampshire University
IT 328 Project Mgmt in Info Tech
Professor William Collard
Sunday, November 12th, 2023
Your Technical Role in the Project Schedule
The chosen technical role is Systems Analyst. The responsibilities of this role are to solve
business problems using IT through designing and implementing software. Specifically for this
project, the Systems Analyst has been assigned the following responsibilities:
Create a defined test plan for all system components (steps 12).
Test the scenarios defined in the test plan for proper application behavior (step 13).
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 (step 14).
Assess and manage risks throughout the project life cycle (step 18).
(Refer to project management document: Gantt Chart)
Predecessor tasks must be completed before the Systems Analyst tasks are performed to
ensure that all project objectives are met without complications. This will aid the project in
running smoothly. The predecessor tasks for step 12 are 7 and 8 (refer to Gantt Chart). Before a
defined test plan can be created, system components such as front end and backend application
must be created. The predecessor tasks for step 13 are 9, 10, and 11 (refer to Gantt Chart).
Without the development of graphic user interface, web code, and backend code, there will be no
code to test. The predecessor tasks for step 14 are step 13 (refer to Gantt Chart). Before
integration testing is performed, scenarios must be tested independently to ensure that the
application is responding the way it is supposed to. Only, then can it be tested to make sure that
the components are working together. There are no predecessor tasks for step 18 because it
should be done throughout the project life cycle. In the project Gantt chart predecessor tasks are
listed next to each task.
The Triple Constraint Matrix
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 additional element to be added to the project is a live animation
on the progress bar. On the students end they will be able to see the term week they are currently
in, the amount of days they have remaining in their term, the term starts and end date, and the
actual progress bar that moves along with each passing day. Fortunately, we have been given
extra funds as well as time to test and develop this new element. Additionally, time should be
added to any predecessor tasks involving the new element.
Predecessor tasks in the Gantt chart will need to be extended by a day or two. This new
element is going to be included in the interface, front/back end application, and web/back end
code. The project timeline is not going to face a drastic change because of the extra allocated
time. In terms of the schedule, cost, and scope, only the scope is to be expected. An amount of
$10,000 has been given to cover the cost of the new element. The schedule and discussed
previously has been slightly altered, but not pushed back. With triple constraint if one changes
then another part of the constraint is also altered. The new element that was added increases the
scope. However, this would be an issue if extra time and money was not given. The triple
constraint affects the success of the project. Since, the two of three of the constraints are taken
care of the scope will balance itself out.
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
- Access to all documents
- Unlimited textbook solutions
- 24/7 expert homework help