IOM541, Fall 1997

Team Assignment Overview (as of 27 October 97)

• Your taxonomy may take the form of a hierarchical index of BPR case study sites or related materials
• Your team is responsible for the visual design, organization, and layout of your taxonomy
• The content of your taxonomy will evolve to include links to other team taxonomies and team projects!
• Your team assignment will be included as part of your final deliverable in your team project WWW site.

Team Project Overview (as of 27 October 97)

• This will entail eliciting, defining, and modeling a business process in its AS-IS form, as well as the TO-BE resulting from your process redesign effort.
• The redesigned process should use intranet or extranet technology, in some way.
• Ideally, the process through redesign may address or propose support through intranet or extranet mechanisms for electronic commerce.
• Your team should also consider use of a BPR modeling tool (e.g., available on the WWW if you search) to support the formalization of your process models.
• Your project deliverable will include a WWW-based presentation of your case materials, as well as a paper-copy version submitted on the last class meeting.
• Your team will make a project presentation using briefing materials posted on your team WWW site.
• It is highly recommended that your team also present your results to your sponsor who hosted your case study, as well as get their feedback (which should be documented in your case materials).
• Your team will prepare a "top-level" transition plan for how to help guide the transition from the AS-IS process to your proposed TO-BE redesigned process.
• A project documentation template will be provided to outline what information to be sure and include.
• The entire class will participate in reviewing and evaluating the team projects on the last class meeting.

Team Project Guidelines: Final Deliverables and Contents

Final Project Deliverables:

• Each team will post a final Web/Intranet-based (HTML) copy of their project on a USC server (e.g., www.usc-scf.edu) for final evaluation no later than 12noon, 10 Dec 97
• Each team will deliver a final printed (bound or covered) version of their project materials (described below) for final evaluation no later than 12noon, 10 Dec 97 to mailbox, Prof. Walt Scacchi, IOM Dept., BRI-400.
• Presentation format counts! Spelling and grammar errors should be avoided or corrected prior to submission. All URL links in your project materials should work properly. Use of graphics or multi-media is encouraged, if useful.
• Each course participant will complete and submit a Team Project rating or scoring form, to be distributed and returned on 8 Dec 97

Final Project Minimum Contents:

• Project cover/Home page: Team Name, Project Name, Team Members
• Team member names should have URL links to their on-line resume
• Project Table-of-Contents/Site Map page: Providing a hierarchical view of the Team Project materials
• Team member contributions pages: Each team member will provide a short description (Web page) of what they did, what tasks they performed, any software tools they used, sections of the final project deliverables they prepared, what they learned by doing the BPR team project, etc.,  as a member of their team.
• Project team assignment:
• Overview
• Taxonomy description
• Narrative version
• Web-based version
• Other highlights or significant results
• Description of links to other BPR taxonomies or team projects
• Project description
• Overview
• Case setting
• Company or organization background (including URL links to company site)
• Process(es) selected for redesign
• Redesign objectives, constraints, and challenges
• Legacy or AS-IS process
• Narrative version (including perceived problems)
• Process model (graphic or Web-based version)
• Redesigned or TO-BE process
• Narrative version (including alternative solutions)
• Process model (graphic or Web-based version)
• Identification and discussion of redesign heuristics used in developing the TO-BE process version
• Identification and discussion of any Intranet, Web-based, or Electronic Commerce systems, technologies, techniques, or concepts used in developing the TO-BE process version
• Description of any computer-based tools used to support process redesign
• Other materials used in the project (ROI/ROK/ROP analyses, simulations, process prototypes, etc.)
• Proposed process transition plan: what steps should be taken in what order to transition from the AS-IS to TO-BE versions of the process(es)
• Comments or feedback from company or organization participants regarding their view of the AS-IS and TO-BE processes, etc.
• Optional Extra Credit Contributions: (by individual team member)
• Any extra credit efforts must be submitted in writing/email for approval no later than class meeting on 1 Dec 97
• Description of extra credit task
• Description of any computer-based tools used to support the extra credit task
• Description of results:
• Narrative version
• Computer-based results, process models, graphics or Web-based version
• Concluding remarks on overall BPR team project experience
• Reference materials (off-line, BPR taxonomies, or other Web-based materials with URL links)

Final Exam Guidelines

• Each team will be allocated 15-20 minutes to present the results of their project, including up to 5 minutes of Questions and Answers
• Each team will present a Web/Intranet-based presentation of their project
• The presentation will include only materials that are part of the Team Project deliverables
• Each team member should participate in the final presentation
• Team members presenting Extra Credit work should do so as part of their presentation
• Alll course participants will be involved in rating or scoring the presentations of the other teams
• All course participants should communicate any dietary restrictions to Prof. Walt Scacchi by 1 Dec 97, prior to his ordering and delivery of Pizza and Beverages for all course participants. (Students may elect to bring additional beverage items).

This interactive presentation page is maintained by Walt Scacchi who can be reached at the e-mail address noted above. This page was last updated on 24 November 97. 

This presentation can be found on the WWW at: