To complete this analysis, you will:
Remember: A good analysis is updated iteratively so that each part aligns well with the next (and the last).
After a full day of meetings with the MDCM executive team, MDCM’s new CIO Shawn Atkins feels no closer to a solution. Frustrated, he turns to his “SWAT Team” – the nickname he’s given to an advisory group formed from an elite subset of the twenty-three managers he identified as high potential IT leaders – a group he’s asked you to lead.
Shawn has given you a short-list of questions to consider as a starting point:
This is a deliberately chosen “classic” case. This means that the story is old, as are the technology references, but the issues and themes are valuable and timeliness. In analyzing the case you should interpret any technology references as their modern day equivalent, and you should plan and propose in terms of our contemporary time and era (i.e. if they say Windows assume we’re talking Windows 7, 8 or 10, if you are thinking they should adopt a new online service you would look at contemporary options).
Since most steps contain a tree diagram and the others benefit from general visuals, you have some discretion on how you create these, including:
However, irrespective of whatever method you use to create your work you must then translate into a single contiguous PDF document with 1-2 pages per each of the 5 analysis steps (i.e. your finished document should be 5-10 pages long). For example, if you were to hand draw out these steps (e.g. on a sheet of paper or a whiteboard), you could take a picture of each, paste those pictures into a MS Word document, and then save that document as a PDF. You must, however, ensure that whatever you create is reasonably legible to the reader (e.g. your professor).