MGMT 240: Intro to Information Systems
Presentation Guidelines

 

 

Your team will present your project during the last week of classes. The presentations will be during regular class hours, in the regular classroom.


As specified in the syllabus, anyone who misses class on ANY presentation day without a really, really good reason will have 10% knocked off their final grade. Why? Because this is a very important time for you to support each other's work and learn from one another.


Why are we doing project presentations?

For two reasons. First, you should have the opportunity to present your work to your peers. You have worked hard on the project, and you should be proud of your accomplishment. So here's a chance to show it to each other. Second, I want you to go through the experience of crystallizing your project into a concise format. You will use this skill in company progress reports, trade shows, and even among your future professional teams.

What should our presentation be like?

This is entirely up to you! Your presentation should last approx 15-20 minutes and will have an additional 5 minutes at the end for questions and answers. Your presentation should provide the following information for the audience: 1) some orientation to the business context, 2) some description or demonstration of the business process, 3) some description or demonstration of the IS support for the process, and 4) any lessons learned or conclusions. These points should be organized in some creative, entertaining, and thoughtful way. The rest is completely open and up to you. Some groups have had role play demonstrations or live web-based demonstrations while others have performed games, etc. This is your opportunity to be creative, have fun, and impress everyone!

The Orientation section should let the person viewing your presentation "get into" the organizational context of your project, organization, and business process reasonably quickly. Especially effective presentations in previous classes have included photographs or samples of products, company-provided mission statements, company logos, etc.

The Business Process section of your presentation should quickly let the viewer understand the business process you studied and any existing organizational problems or opportunities associated with your business process. Included here could be description of business process (highlighting the CSF's, problems, opportunities, strategic value, etc.), quotes from users and owners that vividly illustrate the process and associated problems (e.g., "we lose $10,000 every month because we can't track inventory well enough" - Kevin Nealon, process owner), and even artifacts. For instance, one past group who studied the reporting system for a lawyer's office arranged (artistically) a bunch of incompatible reports in support of its problem statement.

The How the IS supports the process section of the presentation should quickly convey to the audience how the IS supports the business process. Topics you may want to include here are process performance data, mapping the IS capabilities to the mission statement or critical success factors, impacts of managing the supply chain, etc.

The Lessons Learned section of the presentation could perhaps integrate the major themes from your articles with your IS supported organizational business process. This section can include implementation issues, benefits, drawbacks, impacts of the IS on the organization, etc.

Some Additional Advice: Your group will be completely unable to present to the class everything that is contained in your paper. Don't even try to, it won't work and I will not be impressed. Therefore, choose two or three of the most important or interesting things you learned to present to the class. Practice, practice, practice! Decide what to include and what to exclude. I will be looking for presentations that clearly describe what the project is about, clearly describe the business process and the IS that supports it. At the end of your presentation, it is likely that I will ask questions of your team members.