Information Systems Integration – Tony Messina

Schedule

Note: You are expected to attend every class meeting. Job interviews and work conflicts are NOT acceptable reasons for missing class. 

Week/
Session
Topics/Exercises Reading
Due
1.1
(1/16)
1.2
(1/18)
  • Systems and Enterprise IT
  • Thinking about “systems”
2.1
(1/23)
  • Systems and Enterprise IT
  • The role of business processes in systems
 

2.2
(1/25)
  • Systems and Enterprise IT
  • Case: Information Technology at Cirque du Soleil (HBS coursepack)
  • Case: Information Technology at Cirque du Soleil (post to Owlbox)
  • T: Project proposal
3.1
(1/30)
  • Structure and Role of the IT organization
  • The right “IT structure” for the organization; cost and profit centers
3.2
(2/1)
FIRST STATUS REPORT TO CLASS – PITCH
Focus: Overview of project charter, business case, project importance
  • T: Status report, charter, and deck (post to Owlbox)
  • First Community Site post (Last name: M – Z)
4.1
(2/6)
  • Structure and Role of the IT organization
  • Applying the four Built-to-Purpose roles
4.2
(2/8)
  • Structure and Role of the IT organization
  • Wyeth Case; Guest Expert: TBA
  • Case: The Globalization of Wyeth (HBS coursepack)
  • Case: The Globalization of Wyeth (post to Owlbox)
  • First Community Site post (Last name: A – L)
5.1
(2/13)
EXAM 1
5.2
(2/15)
SECOND STATUS REPORT TO CLASS – TECHNICAL ARCHITECTURE
Focus: Process model, data model, system architecture diagram
  • T: Status report, process model, data model, system architecture diagram, and deck. (post to Owlbox)
6.1
(2/20)
  • IT Value
  • Metrics for IT valuation; calculating value: NPV and expected Value
  • Second Community Site post (Last name: M – Z)
  • Community Site Comment 2 & 3 (Last name: A – L)
6.2
(2/22)
  • IT Value
  • Scorecards, assessing risk

 

  • Exercise: Valuation of your capstone project
  • Defining revenues and expenses
  • Finding supporting evidence
7.1
(2/27)
  • Disruptive Innovation
  • Signals of change and systems thinking
7.2
(3/1)
  • Disruptive Innovation
  • Where disruption theory goes wrong.

 

  • Exercise: Identifying disruptive potential
  • Is your capstone project “disruptive?”
  • Second Community Site post (Last name: A – L)
  • Community Site Comment 2 & 3 (Last name: M – Z)
(3/6 & 3/8) SPRING BREAK – NO CLASS MEETING
8.1
(3/13)
  • Exercise: Designing your capstone prototype
  • What should it do?
  • Reflecting the technical architecture. 
  • Sketching it out.
  • Third Community Site post (Last name: M – Z)
  • Community Site Comment 4 & 5 (Last name: A – L)
8.2
(3/15)
  • Disruptive Innovation
  • Applying disruptive innovation
  • Case: Cognitive Computing and Artificial Intelligence
  • Case: Cognitive Computing and Artificial Intelligence (post to Owlbox)
9.1
(3/20)
THIRD STATUS REPORT TO CLASS – BUSINESS CASE AND PROTOTYPE
Focus: Revised overview, charter, business case (spreadsheet), prototype 
  • T: Status report, charter, business case (spreadsheet), prototype, and deck. (post to Owlbox)
  • T: First progress grade from mentor
9.2
(3/22)
NO CLASS MEETING
ALL TEAMS MUST MEET WITH INSTRUCTOR
10.1
(3/27)
  • Putting it all together: value, innovation, models
  • Guest expert: TBA
  • Third Community Site post (Last name: A – L)
  • Community Site Comment 4 & 5 (Last name: M – Z)
10.2
(3/29)
FOURTH STATUS REPORT TO CLASS – TECHNICAL ARCHITECTURE AND PROTOTYPE
Focus: Updated technical architecture, revised prototype, and project site
  •  T: Status report, updated data model, process model, system architecture diagram, and site. (post to Owlbox)
11.1
(4/3)
EXAM 2
11.2
(4/5)
PROJECT WORK, Exam Feedback, Course Wrap-up
12.1
(4/10)
FIFTH STATUS REPORT TO CLASS – PROJECT OVERVIEW, BUSINESS CASE, PROTOTYPE
Focus: Revised charter, final draft of prototype, updated project site
  • Community Site Comment 6 (All)
  • T: Status report, charter, prototype, business case (spreadsheet), and site
12.2
(4/12)
PROJECT WORK
13 .1
(4/17)
TEAM PROJECT PRESENTATION DRY RUN
(the ‘dress rehearsal’ in class)
  • T: Business case (spreadsheet), data model, process model, system architecture diagram. (post to Owlbox)
13.2
(4/19)
TEAM PROJECT PRESENTATION DRY RUN
(the ‘dress rehearsal’ in class)
  •  T: Second  progress grade from mentor
14.1
(4/24)
SHOWCASE: FINAL TEAM PRESENTATIONS
CLASS WILL MEET FROM 6:00 PM – 8:00 PM, Location: TBA FOR SPRING 2018
  • Team project (all deliverables due)
14.2
(4/26)
NO CLASS MEETING