What to Expect
Successful technology projects and enhancements require commitment, coordination, and communication both within ITS and across campus.
Every project has a life cycle that is comprised of four phases: initiation, planning, execution and closing. Project management is the process and tools used to guide an initiative through a Project Lifecycle.
See the step by step description of the Drake ITS project management process below:
Step One: Initiating
- Request a project
- The first step is to submit a technology project request.
- When submitting an idea, consider how the project will impact the university and align with Drake's strategic goals. Focus more on the need you are trying to address than on a specific product.
- Review of requests by ITS
- A project manager will review the idea and follow up with you if more information is necessary.
- Your idea may not be classified as a project, it could be an IT service request or a system enhancement. In these cases, the project manager will inform you and transfer the request to the appropriate ITS team.
- If the request is determined to be a major project, the project manager will contact your department's Executive Sponsor for confirmation that the project should be considered in the next project prioritization cycle.
- The Executive Sponsor approves development of a business case. If your idea is not approved at this stage, you can work with your leadership to resubmit the idea or find an alternate solution.
- Develop a business case
- An ITS project manager will schedule a meeting to help you get started writing your business case.
Key elements of the business case include:
- Goals and Objectives
- Strategic Alignment
- Non-ITS resource requirements
- Cost Benefit Analysis
- Share the business case with your Executive Sponsor and secure their approval.
- Send the completed business case to the project manager, by the deadline for the next posted project prioritization cycle (on the IT Project Management website).
- ASAC (Administrative Systems Advisory Council) reviews business cases in the first and third quarters of the year. ASAC provides a project priority recommendation to President's Council.
- President's Council makes the final decision on projects that will move into the planning phase.
Step Two: Planning
- Getting Started
- A project manager will be assigned to your project. They will work with you to finalize the project team, scope, schedule, deliverables, risks, etc. and develop a Project Definition Document (PDD).
- Depending on the type of technology solution being implemented, additional discovery and/or vendor selection may be required.
- Project Kick Off Approval
- The PDD will be reviewed and signed off by the Executive Sponsor. The project manager will review the PDD with you and the Executive Sponsor or send the document directly to the sponsor if they prefer to review it independently.
- Upon signature of the PDD the project manager will schedule the kick off meeting with the project team.
Step Three: Executing
- A detailed project schedule will be created and tasks are assigned to team members. Regular team meetings are scheduled and the project manager provides regular status reports to the team and campus (as needed).
- The project manager and functional lead(s) work with stakeholders to complete business process analysis and finalize requirements.
- Technical design and test plans are finalized.
- A cycle of development and testing continues until system is ready to go live.
- The project manager constantly monitors tasks and risks that are or could delay the project or impact the solution, then makes adjustments to keep the project on track.
- After testing sign off, the functional and technical leads and Executive Sponsor provide approval to move the system into production.
- Functional and technical production validation is completed and implementation is complete.
Step Four: Closing
- Project Manager will send a project satisfaction survey for the team to evaluation successes and areas for improvement.
- A Closeout Lesson’s Learned meeting is held and any outstanding issues are addressed.
- Sponsor signs a Project Acceptance and the project is officially closed.
- Project Manager archives all required documentation.
NOTE: May not show outages under 15 minutes.