What specifically could have been done to avoid the negatives, and what specifically could be done to address such issues in the public IT world.

Module 5 Case Study

Case Studies: There are 3 case studies required. Each student is required to review and
analyze the case studies and submit his or her analysis on a four page double-­­spaced
paper. Each paper should contain two sections:
1. A Summary Section of not more than two pages
2. An Analysis section of not less than two pages.

All case studies are due on the date listed on the class schedule and must be submitted electronically to the professor on the due date. Sources used in the analysis should be cited and referenced at the end of the paper.

The analysis section should not repeat what is already in the case study and the summary. Instead, students are required to apply the concepts learned in the lectures and readings pertaining to the modules in their analysis of the case studies. Failure to do so will result in a deduction of points.

Based on the concepts learned in the class, students are expected to discuss in their own words, as part of the analysis, what they think are the positives or negatives in the management and execution of the projects in the case, the causes of those positives or negatives, what specifically could have been done to avoid the negatives, and what specifically could be done to address such issues in the public IT world.

Some case studies have questions at the end of the cases. Students should not answer these questions directly. Rather, they should apply the knowledge gained in the lectures and other readings to analyze the cases.

Required:
Review, summarize and analyze this case study by applying the concepts learned in the class readings. You are expected to discuss in your own words, as part of the analysis, what you think are the:
a) Successes or failures (positives or negatives) in the planning, design, management and
execution of the project in the case,
b) Roles of the parties and the causes of those successes or failures,
c) Actions that could have been taken to improve the outcome of the project, and
d) Lessons learned and what could be done to address such lessons in the public IT world.