ProjectCharter_RRD

					   One Purdue Role Request Web Application
DRAFT
                        PR OJESeptember ER
   RoleRequest 1.0- CurrentOJECT CHARTER 2007
                        PR for CT CHART 10,

PROJECT INFORMATION
PROJECT INFORMATION

Project Title: One Purdue Role Request Application
Project Manager: Cheryl Gray
Project Developer: Javona White Bear
Project Start: July 2007
Project Deadline: Nov 2007


PROJECT CONTEXT
PROJECT CONTEXT
Business Services currently manages requests for roles for positions through an online
form process. This form is submitted, printed, and circulated for approval. To improve
tracking, circulation, response time and add reporting features this is being expanded
into an application level interface facilitating communications between university
customers, the HR Clearing House, and One Purdue Security team. This application may
later be expanded to incorporate the Segregation of Duties matrix for roles.


PROJECT OBJECTIVES
PROJECT OBJECTIVES
The initial objectives are to:

     Enable addition, removal, updating, reporting on roles for administrative level
      users
     Enable role reporting for users within a role or roles assigned to a user, or position
      (dependant upon IAM resources)
     Enable addition, removal, saving, and tracking of role requests and role request
      status
     Enable online approval or denial of roles within a requests by approvers
     Enable identification of and assigning of special roles to authorized users
     Enable online tracking/updating status of request by OnePurdue team
     Enable automatic notification on request status, archiving of request history and
      tracking of user actions.
     Enable OnePurdue Security Team request assignment and notification.
     This system will track all data OLTP format in a SQL server database
     This system will be scripted primarily in Coldfusion for the web interface.
     This system will be built with scalability in mind for the later implementation of
      the Segregation of Duties matrix.
                                                                                          2

PROJECT APPROACH
PROJECT APPROACH
This project will follow a standard IT development timeline. The approach is as follows
with estimated dates of completion:

    Gather Requirements via Interview (1month)
        o 8/27/07
    Review existing tools and functionality (included above)
        o 8/27/07
    Develop a timeline for development of the database, request for service (pending)
    Develop the database and ERD (ENTITY RELATIONSHIP DIAGRAM) (2wks)
        o Assuming database access: 9/3/07
    Enter test data and database testing (1wk)
        o Assuming database access: 9/10/07
    Web form development and testing (4-6 wks)
        o 10/19/07
    User testing and review of application on development server (2-4 wks)
        o 10/19/07-11/16/07
    Application move to production (2wks)
        o Two weeks after testing complete
    Production Testing by developer (1wk)
        o 1 week after move to production
    Deployment (1wk)
        o After production testing, involves communication to users

PROJECT ASSUMPTIONS
PROJECT ASSUMPTIONS
    Web-delivered, user-interfaces of the application will follow the Business
     Services Web standards and abide by all Web Accessibility guidelines
    Windows XP/IE compatibility
    Continued support for Coldfusion & SQL servers
    Change management must be implemented.


PROJECT CONSTRAINTS
PROJECT CONSTRAINTS
    Must be scalable, reusable for later use with matrix.

PROJECT RISKS & RISK MANAGEMENT
PROJECT RISKS & RISK MANAGEMENT

Risk                            Risk Management
Lack of resources for timely    Have manual strategy in place
completion
Loss of support for             Have easily transplanted design
technology
                                                                                     3



PROJECT ROLES AND RESPONSIBILITIES
PROJECT ROLES AND RESPONSIBILITIES
Role                       Name               Responsibility
Project Sponsors           Lucia Anderson     Determine project priority for Business
                           John Beelke        Services. (high priority)
                           Jim David
                           Connie Lapinskas
                           Larry Pherson
                           Denise Laussade
                           John Shipley
                           Mike Szczepanski
Stakeholders               Cheryl Gray        Determine the appropriate functionality of
                           Brenda Walling     the application.
                                              Support the project and provide input and
                                              review as requested. Support the
                                              implementation of the project.
Project Manager            Cheryl Gray        Key resource to execute the project.
Project Developer Javona White Bear           Application Developer
Scope/Change               Cheryl Gray        Final Approval/Rejection of scope/change
Management                                    requests
Reviewers/testers Cheryl Gray                 Test the application and provide feedback.
                  Donna Foley
                  Brenda Walling
                  Jeff Smith
                  Rob Stanfield
                  Ben Lewis
                  (Lucia to provide a
                  couple names for
                  input/testing)

PROJECT CHARTER SIGN-OFF
PROJECT CHARTER SIGN-OFF


______________________________________                _______________
Mike Szczepanski                                      Date
on behalf of Business Services Directors


______________________________________                _______________
Cheryl Gray,                                          Date
HR Data Steward,
Project Manager
                                                                                             4



                             PROJECT SCOPE

PROJECT PRODUCT
PROJECT PRODUCT
This project will result in a web application capable of tracking roles, requests, and the
status of those requests.


PROJECT REQUIREMENTS
PROJECT REQUIREMENTS
    Application will provide compliance with Business Services Web standards and
     abide by all Web Accessibility guidelines
    Application will allow users to make requests, track those requests, and
     administrative users to update that request
    Application will have reporting for requests: incomplete requests, approval
     notification
    Application will allow entry and management of roles for administrative users
    Application will assign and manage administrative levels by security admin
    Application will allow interaction of requests and tracking of interaction with One
     Purdue Security team

PROJECT DELIVERABLES
PROJECT DELIVERABLES
The project will deliver the following:
    Project Charter
    Project Scope
    Project Scope/Change Management
    Project Timeline/Breakdown Schedule
    Functional database, reports, and web forms
    Basic Training/Instructions
    Deployment
    Validation Process

PROJECT VALIDATION PROCESS
PROJECT VALIDATION PROCESS
In order to validate the successful completion of the deliverables the validation process
will include:

    Brief QA period with developmental version of application provided to
     reviewers/testers to assess meeting of requirements
    Interview/Observation session with key stakeholders to allow feedback and final
     validation before production.
                                                                                         5



PROJECT SCOPE CHANGE MANAGEMENT
PROJECT SCOPE CHANGE MANAGEMENT
This project will have a formal Scope Change Management process. In order to request a
change to the Scope or any functionality greater than text change after the application is
in production the form will need to be submitted and signed-off by the Project Sponsor
and Project Change Manager (see assigned roles and responsibilities) before it will be
considered for change. The form is included in this documentation.


PROJECT SCOPE SIGN-OFF
PROJECT SCOPE SIGN-OFF


______________________________________                      _______________
Mike Szczepanski,                                                   Date
on behalf of Business Services Directors

______________________________________                      _______________
Cheryl Gray,                                                Date
HR Data Steward,
Project Manager
                                                                  6


   PROJECT SCOPE CHANGE REQUEST FORM

DATE
PROJECT NAME                  RoleRequest 1.0
REQUESTOR
DESCRIPTION



JUSTIFICATION




CHANGE APPROVAL SIGN-OFF
CHANGE APPROVAL SIGN-OFF


______________________________________          _______________
Mike Szczepanski,                                      Date
on behalf of Business Services Directors


______________________________________          _______________
Cheryl Gray,                                    Date
HR Data Steward,
Project Manager

				
DOCUMENT INFO