Project Charter

Project Name Authorisations Author Approved

Student Engagement Tracking System (SETS)

Name Function Project Manager Project Sponsor Date Signature

Project Context & Background

The Ira A. Fulton Schools of Engineering at Arizona State University has thousands of undergraduate students and a diverse variety of undergraduate student groups. Within Fulton Engineering, there exists administrative staff that guide and consult students in scholarship, educational and career goals. This administrative staff currently collects data on undergraduate students and student groups and stores it in a very inaccessible manner. Additionally, there are many students and groups in comparison with the number of available staff, straining the available time administrative staff may spend on any given task. It is expected that customer satisfaction from the selected administrative users will be improved upon with this project. This will be measured by a customer satisfaction survey completed at the conclusion of the SETS project. Another target of SETS relates to the time required to complete tasks. SETS seeks to reduce the time required to search for student data by 50 percent. SETS also intends to reduce the time required to prepare for a student meeting by 50 percent. Therefore, increasing worker efficiency will also be an expected benefit. 1/21/2013
Proposed End Date

Expected Organization Benefits

Proposed Start Date Project Objectives

4/21/2013

Key Outputs /Deliverables Project Scope includes excludes Success Criteria

Methodology / Approach

The Six Sigma methodology used to build SETS will be focused around the DMEDI approach, a type of Design for Lean Six Sigma (DFLSS) projects. The primary reason to utilize DMEDI instead of DMAIC is due to SETS being a truly new, robust process, rather than a solution to reduce system variation and defects.

Project Resources Sponsor Project Manager Project Team Members

Dr. Anderson-Rowland Nancy Dickson Jose Encinas, Isaac Kashiwagi, and Brittney Reyman

Issues & Risks

Assumptions

The first assumption is that true example data will not be used in the initial design of SETS. The data to be used will be real data that has been scrambled slightly due to student privacy issues. Viewing the data as it is actually formatted will not be permitted in the early stages of SETS as the developers are not university employees. The second assumption is that this project will consist of building a framework system to be expanded upon in the future. Due to time limitations of one semester, it will not be possible to create a fully developed database. Instead, the intention is to create a system that can be expanded upon after stated goals and scope requirements have been achieved.

Reporting Meetings Faculty meeting Project Team meeting Reports Progress Reports Closure Report Every 3 Weeks Weekly Monthly End of Semester

Frequency

Who Project Team,Project Manager, End Users Project Team Project Sponsor Project Sponsor