1-2 Journal: Choosing a Case Study Tips on Writing a Problem Statement

1-2 Journal: Choosing a Case Study -Tips on Writing a Problem Statement
Student’s Name
Institution Affiliation
1-2 Journal: Choosing a Case Study -Tips on Writing a Problem Statement
This case study will be based on company dealing with software development and data hosting services, mainly offering these services and products to wireless carriers. The company has had issues positioning new software versions into the invention environment. In this case, deployment is the work key to taking an invention ready binary and mounting, running tests and releasing into the market environment. The organization has in the recent been unsuccessful in deploying the releases as per the release schedule over fifty percent of the time (Brynjolfsson & Hitt, 2000).
Problem Statement
Our goal is to have all our software publications going to the production flawlessly, deprived of shortcomings, and where every party is informed and aware of the software outcomes and rank (Markus & Robey, 1998).
Currently, our organization has many issue failures that have resulted in too many roll-back fiascos. If this problem is not handled, there will need to increase resources take care of the gushing complications, and the company may miss meeting critical client targets which could result in revenue loss, lost business, SLA fines, and at worse, damage to the organization’s quality status.
Solving this problem will not only benefit the production department of the company but the organization at large.

The organization will be able to deploy almost hundred percent of the releases as per the clients’ schedule, there will be minimum damages and fines, and importantly customer satisfaction. Finally, the move will increase the organization’s overall income from software releases due to the accelerated deployment, and also improve the company’s quality standing in the market (Hippel & Krogh, 2003).
The Kaizen Blitz methodology will be used to evaluate the previous release to help the organization improve its processes (Laraia et al., 1999).References
Brynjolfsson, E., & Hitt, L. M. (2000). Beyond computation: Information technology, organizational transformation and business performance. Journal of Economic perspectives, 14(4), 23-48.
Hippel, E. V., & Krogh, G. V. (2003). Open source software and the “private-collective” innovation model: Issues for organization science. Organization science, 14(2), 209-223.
Laraia, A. C., Moody, P. E., & Hall, R. W. (1999). The kaizen blitz: accelerating breakthroughs in productivity and performance. John Wiley & Sons.
Markus, M. L., & Robey, D. (1988). Information technology and organizational change: causal structure in theory and research. Management science, 34(5), 583-598.