Build a project business case
Due Date: Click or tap to enter a date.
|
Team Lead:
|
Status: Choose an item.
|
· Budget max 100,000 $
· You will be doing an event to improved Frosh week/orientation
· Assume you will be working with 6 members
· We need to present a strong need and business case for the project.
· Tools we can use to demonstrate this include:
o Identifying and Proving the Problem or Need this Project Addresses
o Opportunities and Benefits this Project Provides
o Benefits to each Stakeholder Group of the Project
o Proposed Payback Period
o Proposed Average Rate of Return
o Weighted Factor Model for Why This Project BEST Meets Stakeholder Goals as compared to Other Project Options
o SELL IT!
Executive Summary Highlighting the key points from the proposal
Background Brief background to the proposal including current situation. May also mention any related or dependent projects
NeedsAssessment The core issues or gaps that the projectwill work to address (Can be from the perspective of different stakeholders)
Objectives The main aim of the project. Goals to address stakeholder needs
Value Proposition The business case for why this project is important.What the expected yield of the project will be
Proposed Scope Overview of the proposed solutions or activity that address these stakeholder needs (i.e. What you are proposing)
Proposed Approach An approach that will get the client this solution (i.e. Project Methodology, Communication, Project Management, Support, Training, Quality, Transitioning
Proposed Timeline & Budget Estimates for how much and how long to delivery project
Team Bios Description of group and their skill sets proposing to do the work
Case Studies Any relevant past experience that can be applied
Define: Stakeholder Requirements
Due Date: Click or tap to enter a date.
|
Team Lead:
|
Status: Choose an item.
|
· We need to show we understand stakeholder requirements so that we can develop a project that aligns with stakeholder needs.
· Remember stakeholder requirements are typically expressed as “MUST”, “SHOULD”, and “MUST NOT”. As a guideline, your goal will be to identify at least 5 “Musts”, 3 “Shoulds”, and 1 “Must Not” for each stakeholder.
· Consider creating a stakeholder register using a matrix that outlines stakeholder requirements. For example:
Stakeholder Name
|
Stakeholder Category
|
Requirement
“MUST….”
|
Requirement
“SHOULD….”
|
Requirement
“MUST NOT.”
|
Students
|
User 1
|
|
|
|
Professors
|
User 2
|
|
|
|
(eg. Name of a specific person or dept. at GBC)
|
Customer
|
|
|
|
|
Sponsor
|
|
|
|
|
Project Team
|
|
|
|
|
Subject Experts
|
|
|
|
|
Project Manager
|
|
|
|