Instructor: Aleksi Aaltonen, Section 002

Team project

A team project calls you to apply IT and innovative thinking to solve a business problem. The project must offer a solution to an existing business problem or propose a new product or service.

This requires you to identify, analyze and propose a solution to a problem and demonstrate its business benefits. It important that the problem definition, technical solution and the business benefits (business case) are coherent.

DELIVERABLES

There are three main deliverables from the team project.

Deliverable 1: Project deck

  • What is interesting about this project, why should we care?
  • Financial, competitive, and architectural analysis of why an organization needs to solve this problem or needs the proposed new product or service
  • List and analyze the enterprise architecture and systems impact of the solution – what it will mean for other systems? What will you need from other systems?
  • What is the underlying business model of your idea? What implications will it have?
  • Description of the proposed solution

Deliverable 2: Appendixes and a related website

Appendixes and a related website provide important additional information about the project that is not suitable for the presentation format.

See below for further details.

Deliverable 3: A functioning prototype

The prototype must demonstrates your solution. It should should include:

  • Well designed key screens and forms that are functional and represent the final solution
  • The screens should be based on an appropriate data model (ERD or Schema)
  • If you are working on a mobile app, the prototype should function as a mobile prototype (e.g., demo on a mobile device). If it is a website, then it should function as a website.
  • Concentrate on illustrating just the key ideas. Ignore the following:
    • User accounts and logging in – hard code illustrative accounts
    • Server and database setup and use – create the data model inside the prototyping tool as if it would running from a server
    • Error recovery, help and documentation
  • We recommend using Justinmind for prototyping. If you wish to use another tool, please check with the instructor.

ASSESSMENT AND GRADING

Status reports

25% of the team project grade is based on a) meeting all the deadlines and b) the quality of the materials at each deadline.

  • There are five status reports during the term. See the course schedule and these instructions for what is expected for each status report.
  • Each status report is worth 5% of the team project grade.
  • If you are unprepared for the status report or the deliverable for that status report is incomplete, the team will receive zero for that milestone.

Deck and prototype (Deliverables 1 and 3)

  • 75% of the team project grade is based on the overall quality of the final deliverable (deck and prototype).
  • The peer evaluation from your team members is factored into your individual grade.

Appendixes (Deliverable 2)

The additional documentation includes the project charter, a detailed budget spreadsheet, a data model, a process model, and a systems architecture diagram.

  • You will be required to submit draft versions of these documents at five checkpoints throughout the semester.
  • For each piece of documentation received at a checkpoint, you will receive a pass/fail evaluation from your instructor.
  • You cannot receive credit for the final deliverable until your team receives a “pass” evaluation for all components.
    • The deadline for receiving a “pass” for all components is the presentation dry-run on 11/27/2018 – after that, your team will receive no credit for the final project.

BE CAREFUL! Failure to deliver this part of the project will render your team unable to pass the course with a C.

Grading by mentors

Each team will also receive a mentor grade in addition to the team project grade.

FURTHER INFORMATION

Project proposal

You need to submit an informal project proposal soon after the course begins (see schedule).

  1. Describe in a few sentences what you would like to work on and if you already know the names of team members, list those as well.
  2. Only one team member needs to post. If you do not have a team that is okay. Just describe your idea.
  3. Email the proposal to instuctor. The instructor will respond with questions and comments.

Team, progress meetings and reports

Form a team of not more than 4 people. The team will provide regular progress reports as listed in the schedule using one of the following approaches:

  1. Face to face with the instructor or mentor.
  2. Online using WebEx.

The instructor or mentor will select the approach and may create additional deadlines and schedule additional meetings with each team. All meetings will start with a review of the project. To facilitate the review a) bring printouts (or display online) of Project charter and Status update form, and b) post the documents on the team private group. The documents should be updated prior to each meeting. One team member should start the meeting with a review of the changes in the documents since the last meeting.

Document sharing. Submit all project related documents via OWLbox. Create a new folder in OWLbox called MIS4596S18_LastName1_Lastname2_Lastname3_Lastname4 (i.e., the last names of each team member). All team members should have access to this folder.

Grading. You will receive a grade for each progress meeting. The grade is for progress made since the last meeting and for the quality of the documents. All team members are required to participate in all progress meetings. The team will receive a letter grade reduction for each missing team member. There are no exceptions to this policy. The progress grades will use the following model:

A – Excellent
B – Good but more can be done
C – Okay but lots more needs to be done
D – Mediocre
F – Unacceptable

Project site

Create a standalone site on the Community platform that describes and documents the team project.

  • The site should be professional and attractively designed. Use one of the following themes: Infinity Pro, Digital Pro, Enterprise Pro or Centric Pro. To get access, first create a site using the standard Fox MIS theme and then contact the instructor to request access to the selected theme. (Changing the theme won’t cost you anything!)
  • Include a short description and selected documents from the project. Include a downloadable version of your deck.
  • Add screenshots from the prototype and other relevant graphics such as artifacts and pictures from your research.
  • Include names and pictures of team members and links to their personal e-portfolio.

You can receive 50 professional achievement points if you also complete steps 5 and 6 as described here.

More about the three deliverables

  1. A main project deck of 12 slides or less that covers:
    1. Problem – what is the problem you are trying to solve? Why is it important? Why should we care? (use the materials from the project charter)
    2. Solution – what is your solution? How does it work? (use the materials from the project charter)
    3. Competitive analysis and market – who are the competitors? Which market does it fit in? Who are the clients? (use the disruption innovation material)
    4. Data and process model overview – what is the data model of the solution? What is the process model (MIS 2502 and MIS 3504)
    5. Systems architecture overview – what is the overall architecture? (MIS 2501)
    6. Basic financials for years 1, 2, and 3 including income (sales and other sources) and expenses (marketing, salaries, computing, servers, etc). (use the template)
    7. Implementation plan – what steps do you need to take to put your solution into operation? How did you get here? (MIS 3535)
  2. Appendix including the following additional documentation:
    1. Project charter
    2. Detailed budget spreadsheet
    3. Detailed data model
    4. Detailed process model
    5. Detailed systems architecture diagram
    6. All relevant screen prints from the prototype
  3. Project website as described above.
  4. Prototype demonstration in class. (MIS 3504)

Grading: Submit the relevant documents on OWLbox. For the project website include the URL. Each team member needs to complete the team member evaluation and submit confidentially to the instructor via email.

MIS Project Showcase

After the final presentation dry-run during the regular class session, your instructor will choose three teams to present in the MIS Project Showcase. These teams will present in front of all MIS4596 students and external evaluators including MIS faculty and your mentors. The external evaluators will choose a winning team; that team will receive a prize!

Attendance by all students, regardless of whether or not your team is selected to present, is mandatory.

The final presentation for the project is a complete presentation that will include:

  1. A PowerPoint deck of 12 slides or less about the project
    The prototype presentation of your solution

The structure and format of the final presentation is:

  • You have a total of 12 minutes, this includes setup and Q&A – assume and plan for 9–10 minutes of presentation and 2–3 minutes of Q&A.
  • You are responsible for making sure your slides and/or demo is ready and able to project on the day of your presentation. Please have all your materials preloaded in advance.
  • If you are doing a demonstration please make sure in advance that the room will have the appropriate software.
  • The PowerPoint deck should be emailed to the instructor by 10:00 AM on the day of the presentation.