You are about to embark on a technology-related project, but where do you start? Who should be involved and how will the work get done? Will you have time to meet, review, and test? These guidelines explain some key elements in managing a project successfully.
Please email Technology Service Desk with the following items:
As a client requesting project support, you and your team are entering into a partnership with Technology Services. Consider timing and reasons for the project. Some key questions to ask:
- What objectives will completing this project achieve?
- Do you have time to invest in developing a solution?
- Is now the right time?
- How will this project benefit your department? Your constituents? The university?
Stakeholder - A person with an interest in the outcome of the project. Stakeholders may have functional or technical roles and may be designated as primary or secondary stakeholders. Primary stakeholders provide sign-off on functional requirement specification documents.
Sponsoring Team or Department - The future administrator and owner of the tool or component that is the outcome of the project. This entity usually owns most or all of the data involved in the work.
Project Lead - The functional project lead is the subject matter expert who is responsible for driving the project forward as a leader, being present for most or all project meetings, managing testing from the functional side, and signing off on design documents and change requests. The technical project lead is usually a developer but may be the business analyst or TS project manager.
Testing Team - This group is usually composed of key stakeholders and end users and is responsible for ensuring the end product functions correctly and meets all requirements.
Functional Team Member - This person is responsible for ensuring completion of functional tasks, including the development of project requirements with the TS Business Analyst, day-to-day operations, procedures, documentation, training, and testing. A functional team member may also be, but isn't always, a stakeholder.
TS Business Analyst - This role works with stakeholders and the functional team to define detailed project requirements through the assessment and analysis of needs.
TS Project Management Office - The PMO facilitates the management of TS projects by providing guidance on scope, work assignments, and timelines.
Each project is unique, but has five major phases:
In this phase of the project, you will meet with the project manager, business analyst, or other technical experts to define your needs and the scope of the project. Depending on the outcome of this meeting, we will work with you to analyze the business processes and data involved in developing a solution. Once we understand the specifications of the project, we will build a timeline and assign roles and tasks to members of the team. During this phase, you will need to make time in your schedule for discovery meetings and analysis work.
Depending on the nature of the project, this phase may involve building diagrams and models, creating mockups, and developing security plans. If data is involved, we’ll be defining it clearly.
This is the phase in which we build! Even though TS will be the heavy-lifters in this phase, you will be expected to respond to questions (usually within one business day) in order to keep the project moving forward.
Prior to testing, TS will work with you to develop a complete, efficient test plan. Your team will be responsible for testing in a thorough and timely manner. It is our goal to minimize the number of times we test and retest, so careful documentation is essential.
This phase of the project involves communication to and training for those affected by the project, as well as planning for any future maintenance needed to keep things working smoothly.