Section B:

Ans 1: The task that belong to Critical path are highlighted in the below image.

Ans 2:

There are 5problems which I have found in the Gantt chart. Major tool is brainstorming.
Each problem is kept in a yellow box, with numbering of 1 to 6, which will be explained
 1.The flow of task in Gantt chart should not have a break unless there is a weekend or any addition
holidays due to festival season, in this case their have been an additional of 3 days without a reason, the
way this can be mitigated
2.The approve of project proposal has been kept for a 1 day but the time duration has not been
mentioned at all its at 0 which can’t be done in a Gantt chart, the solution for this is to create a meeting
for the approval and placing at least an 1 or 30 mins for the approval process.
3.Once a task is moved ahead no task should go back in the chart but has been moved in the wrong
location
4.This case is clear that arrows in the Gannt chart should not be placed from left side and are only
supposed to go from the right-hand side of the chart. The solution for this is to check the task and find
out if these tasks placed in the right time of execution.
5.This issues is a mess with all the task which is not supposed to happen in a Gantt chart, the flow of
Task should happen along with or one after one, both not happening solution for this is to recreate
where the extra task is from and place it 2 steps above to manage with the flow or to remove if
unnecessary.
Ans 3:

five new tasks aimed at avoiding cost of non-conformance are as follows -

Inspection and auditing the plan helps to understand fault in the software and it can be resolved, Gantt
chart the software is all checked but the a proper inspection and audit will help the process to work
better. Follow Quality standers
reason being these standers in the long run for being stable, if quality measures are not taken in
firsthand then the project can fall apart before completion.
Documentation is necessary for any project, It helps the organization for documents to be in place for
completion with all the related software licenses and completion of the project.
Assembly of the software, helps in integrating project software with extra requirement tools
Collaborates and does not make any issues related to losing of data at the completion of the project.
System test failure, helps in checking the system in such a way that failure should happen, this is a type
of testing which helps to understand that failure for the software is not easy and only with a lot of error
can this happen. This allows the project to be handed in a better way.
Responsible

Ranking
Impact

Sno. Risk Mitigation Contingency

Likely hood

(What could possibly go wrong) (action to be taken (action to be

in advance) taken if risk
arises)

1 Change in preferences Project 2 1 21 Make a robust Effective use of

manager preference list Customer
before hand on any relationship
change service
2 Inefficient time management Operation 2 1 17 Time planning and Revised/
manager the Gantt chart second plan of
timing should be time
followed without a management
fail must be
followed
3 Poor communication Project 3 4 14 Meeting should be The use of
manager conducted, with communication
 equal intervals planning will
make it
effective
4 Coding issues Technical 4 5 5 Each part should be Implementing
lead checked in intervals, a Quality check
to see no gap is for double
present with the cross checks
actual output
5 Technical issue Technical 3 5 4 Explain all the Training them
lead employees with the with all the
related issues which information
are possible to show again, for this
up. to never
happen again
Ans4