Problem Action Consequence Technique (PACT) - Case Study

Problem Action Consequence
Technique (PACT)
Case Study
30th November 2017

Problem Action Consequence Technique (PACT)
Table of Contents
Case Study...................................................................................................................................................3
Introduction.............................................................................................................................................3
Ethical Problems......................................................................................................................................3
Set of Actions..........................................................................................................................................3
Alternative Actions as per Ethics.............................................................................................................4
Consequences of the Action....................................................................................................................4
Recommended Steps...............................................................................................................................5
References...................................................................................................................................................6
2

Problem Action Consequence Technique (PACT)
Case Study
Introduction
The case study that has been described in the YouTube video presents the situation of an un-
tested system that is being passed for go-live. The test manager associated with the project is
Ken and he has been informed about the release of the system in the untested state as per the
demands by the project client and stakeholders. Ken refuses to accept the decision as he
understands the adverse implications of such a step in the long run (Youtube, 2017).
Ethical Problems
The project schedule experienced multiple changes during the timeline of the project. The project
client has again put up a request to receive the final release of the system before the original
deadline. Due to such changes in the project schedule, system testing has not been completed.
There are certain modules of the system that are still in the un-tested state that may bring up
functional errors and non-functional defects during the usage of the system by the end user.
The project lifecycle comprises of a series of steps. Some of these steps are mandatory and
extremely significant in nature. System testing is one of such phases that must be carried out. In
this case, the release of the system would lead to system delivery in an untested state that may
bring up the issues of system defects that may lead to performance and quality issues for the
users (Bostrom, 2013).
There may be operational errors that may also be experienced by the end-users.
Set of Actions
The senior management has decided to deliver the system in the untested state. The system might
have certain defects and the action may impact the stakeholders associated with the system in the
following manner.
 Client: The project client will not be able to experience the desired functionalities and
benefits due to the defects present in the system.
 End Users: The user engagement and satisfaction levels will be low.
 Project Team Members: The project team will be held accountable for the defects in the
system and their performance will be questioned by the top management.
3