Difference between revisions of "IS480 Team wiki: 2012T2 box.us Project Overview"
Qyang.2010 (talk | contribs) |
Qyang.2010 (talk | contribs) |
||
(16 intermediate revisions by 2 users not shown) | |||
Line 55: | Line 55: | ||
|} | |} | ||
− | + | ||
− | |||
=<p><div class="NavHead" style="background-color:#2F55A4;-moz-border-radius:4px; text-align: left; padding: 5px; font-size: 70%;"><span style="color: White"> '''Project Description''' </span></div></p>= | =<p><div class="NavHead" style="background-color:#2F55A4;-moz-border-radius:4px; text-align: left; padding: 5px; font-size: 70%;"><span style="color: White"> '''Project Description''' </span></div></p>= | ||
Line 104: | Line 103: | ||
=<p><div class="NavHead" style="background-color:#2F55A4;-moz-border-radius:4px; text-align: left; padding: 5px; font-size: 70%;"><span style="color: White"> '''Project Scope''' </span></div></p>= | =<p><div class="NavHead" style="background-color:#2F55A4;-moz-border-radius:4px; text-align: left; padding: 5px; font-size: 70%;"><span style="color: White"> '''Project Scope''' </span></div></p>= | ||
+ | View our Detailed Scope: | ||
+ | *[https://docs.google.com/spreadsheet/ccc?key=0AsGBoq64IRhgdEE2VExnZmJCZWhZUkpIZE1mU3NMenc#gid=13 Project Scope on Google Docs] | ||
+ | *[https://wiki.smu.edu.sg/is480/Image:Project_Scope_2.0_31102012_Empact.xlsx Project Scope v2.0] | ||
+ | *[https://wiki.smu.edu.sg/is480/Image:Project_Scope_3.0_01112012.xlsx Project Scope v3.0] | ||
+ | *[https://wiki.smu.edu.sg/is480/Image:Project_Scope_4.0_04112012.xlsx Project Scope v4.0] | ||
+ | *[https://wiki.smu.edu.sg/is480/Image:Project_Scope_5.1_08122012.xlsx Project Scope v5.0] | ||
+ | *[https://wiki.smu.edu.sg/is480/Image:Project_Scope_6.0_13112012.xlsx Project Scope v6.0] | ||
+ | *[https://wiki.smu.edu.sg/is480/Image:Project_Scope_7.0_10012013.xlsx Project Scope v7.0] | ||
+ | *[https://wiki.smu.edu.sg/is480/Image:Project_Scope_8.0_23012013.xlsx Project Scope v8.0] | ||
+ | *[https://wiki.smu.edu.sg/is480/Image:Project_Scope_v9_%28Box.us%29.xlsx Project Scope v9.0] | ||
{| class="wikitable" style="text-align: left; height:50px; width:800px" | {| class="wikitable" style="text-align: left; height:50px; width:800px" | ||
Line 260: | Line 269: | ||
|} | |} | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | =<p><div class="NavHead" style="background-color:#2F55A4;-moz-border-radius:4px; text-align: left; padding: 5px; font-size: 70%;"><span style="color: White"> ''' | + | ===Project Scope (Acceptance Vs MidTerms):=== |
+ | |||
+ | |||
+ | [[Image:ScopeAtAcceptance.jpg | 500px | Schedule Ratio over Time]] | ||
+ | [[Image:ScopeAtMidterms.jpg | 500px | Schedule Ratio over Time]] | ||
+ | |||
+ | |||
+ | '''Changes made''' | ||
+ | |||
+ | 1) Added Interview Form | ||
+ | |||
+ | Enabled Empact to review through the information that was keyed in during the interview with the users | ||
+ | |||
+ | |||
+ | 2) Added Feedback Form | ||
+ | |||
+ | Enabled volunteers to give inputs to Empact about whether the activity completed | ||
+ | |||
+ | |||
+ | 3) Added Dashboard | ||
+ | |||
+ | Enabled users to access their information quickly | ||
+ | Enabled Empact to view vital information about their system quickly | ||
+ | |||
+ | |||
+ | 4) Dropped Mobile Functionalities | ||
+ | |||
+ | Mobile functionalities are a subset of the functionalities of the system | ||
+ | Allows team to focus more on developing a good web application | ||
+ | |||
+ | =<p><div class="NavHead" style="background-color:#2F55A4;-moz-border-radius:4px; text-align: left; padding: 5px; font-size: 70%;"><span style="color: White"> '''Project Handover''' </span></div></p>= | ||
+ | |||
+ | Our project handover plan takes into account the following information: | ||
+ | *identifying and managing key stakeholders including the group who will receive the handover | ||
+ | *a clear date for handover of the project | ||
+ | *a communication plan that starts early in the life of the project and includes the target group | ||
+ | *change management issues and how these will be handled | ||
+ | *getting the target group involved as early as possible including someone being on the project team who also acts as a change agent | ||
+ | *developing appropriate training for this group or ensuring it is included in the handover plan | ||
+ | *clear risk management | ||
+ | *having clear roles for the recipients in the department taking on the new work e.g. it may not be your responsibility for organising the training, it could be their responsibility | ||
+ | <br/> | ||
+ | Source: [http://www.pmhut.com/the-project-handover-checklist Project Handover Checklist @PMHut.com]<br/> | ||
+ | |||
+ | |||
+ | '''Our Project Handover Plan''': [https://docs.google.com/document/d/1U5bX8Nw8Rg-HK6_Jip_wmbx0bbw2Sh7qcIJqb3Pfisw/edit?usp=sharing Project Handover Plan (Box.us)]<br/> | ||
+ | '''Our Handover To-Do List''': [https://docs.google.com/spreadsheet/ccc?key=0AsGBoq64IRhgdHhsMmdFVDRRMGVFYmpvVjVpSk9VZVE&usp=sharing Handover To Do List]<br/> | ||
+ | '''Risk Management Plan''': [https://docs.google.com/spreadsheet/ccc?key=0AsGBoq64IRhgdHVVRkhza3VvSEVsd2ZIMG51ekV3eUE#gid=4 Risks for Project Handover (Box.us)]<br/> | ||
+ | '''Technical Understudy Programme''': coming soon | ||
+ | |||
+ | =<p><div class="NavHead" style="background-color:#2F55A4;-moz-border-radius:4px; text-align: left; padding: 5px; font-size: 70%;"><span style="color: White"> '''Release Planning''' </span></div></p>= | ||
+ | |||
+ | We release the first version on 11 March 2013. | ||
=<p><div class="NavHead" style="background-color:#2F55A4;-moz-border-radius:4px; text-align: left; padding: 5px; font-size: 70%;"><span style="color: White"> '''Project Dictionary''' </span></div></p>= | =<p><div class="NavHead" style="background-color:#2F55A4;-moz-border-radius:4px; text-align: left; padding: 5px; font-size: 70%;"><span style="color: White"> '''Project Dictionary''' </span></div></p>= |
Latest revision as of 13:01, 21 April 2013
HOME | PROJECT OVERVIEW | PROJECT MANAGEMENT | DOCUMENTATION |
Contents
Project Description
ORGANIZATION BACKGROUND Empact is a social enterprise with a mission to serve and empower the non-profit and social enterprise communities. One of Empact’s core business is to matchmake volunteers together with social enterprise so as to provide social enterprises with quality professional services affordable to Non-Profit organizations (NGOs) and Social Enterpises (SEs).
PROJECT FOCUS
In this project, Team Box.us would be developing a Micro-Volunteering System to automate the process of matching volunteers with the relevant jobs. Upon conception, the system would help Empact to ease their matching process bottleneck and provide a mobile application for championing micro-volunteerism among its volunteers.
MOTIVATION
- Reduce the bottleneck in locating for suitable volunteers.
- Reducing the amount of manual labor needed in the process of each task
- Facilitate better communication among NPO/SE, Empact and Volunteer
GOALS
The project aims to accomplish the following objectives:
- Increase micro-volunteerism take up rates among potential pool of volunteers
- Decrease volunteer wait time after registering as a volunteer with Empact
- Decrease NPO/SE wait time after consulting Empact for resource help
- Increase communication between NPO/SE and volunteers in answering simple questions
- Reduce manual task of matching volunteers
DELIVERABLES
Based on their current Volunteer Matching Process, the client requires:
- The development of a new web system that would be able to allow automated volunteer matching, online management of volunteers and NPO/SE, task management for Empact employees and push notification capability for volunteers.
- Deployment of new web system to ensure that it fits the core business process of Empact
In addition, the team would be required to perform solutioning of the web application, deployment of web application and make suggestions to meeting the business goals highlighted.
BUSINESS OBJECTIVES OF PROJECT
These are the business objectives of Empact:
- Solve current bottleneck in matching process
- Facilitate better communication between the different stakeholders in the matching process
- Reduction of Manual Tasks in Matchin Process
Project Scope
View our Detailed Scope:
- Project Scope on Google Docs
- Project Scope v2.0
- Project Scope v3.0
- Project Scope v4.0
- Project Scope v5.0
- Project Scope v6.0
- Project Scope v7.0
- Project Scope v8.0
- Project Scope v9.0
Modules | Module Name | Scope details |
---|---|---|
BASIC FEATURES | ||
Manage Account |
All Users
| |
Manage Profile |
All Users
Empact
NPO
Volunteer
| |
CORE FEATURES | ||
Manage Task |
All Users
Empact
NPO
Volunteer
| |
Manage Task Approval Workflow |
NPO
Empact
| |
Manage Questions |
All Users
NPO
Volunteer/Empact
| |
Manage Search |
All Users
NPO
Volunteer
| |
VALUE-ENHANCING FEATURES | ||
Statistical Reporting |
Empact
| |
Manage Records |
Empact
Volunteer
|
Project Scope (Acceptance Vs MidTerms):
Changes made
1) Added Interview Form
Enabled Empact to review through the information that was keyed in during the interview with the users
2) Added Feedback Form
Enabled volunteers to give inputs to Empact about whether the activity completed
3) Added Dashboard
Enabled users to access their information quickly Enabled Empact to view vital information about their system quickly
4) Dropped Mobile Functionalities
Mobile functionalities are a subset of the functionalities of the system Allows team to focus more on developing a good web application
Project Handover
Our project handover plan takes into account the following information:
- identifying and managing key stakeholders including the group who will receive the handover
- a clear date for handover of the project
- a communication plan that starts early in the life of the project and includes the target group
- change management issues and how these will be handled
- getting the target group involved as early as possible including someone being on the project team who also acts as a change agent
- developing appropriate training for this group or ensuring it is included in the handover plan
- clear risk management
- having clear roles for the recipients in the department taking on the new work e.g. it may not be your responsibility for organising the training, it could be their responsibility
Source: Project Handover Checklist @PMHut.com
Our Project Handover Plan: Project Handover Plan (Box.us)
Our Handover To-Do List: Handover To Do List
Risk Management Plan: Risks for Project Handover (Box.us)
Technical Understudy Programme: coming soon
Release Planning
We release the first version on 11 March 2013.
Project Dictionary
Process Terminologies
- Question: Items posted by the NPO/SE that do not require any necessary approval by Empact
- Task: Items posted by the NPO/SE that needs to be executed by the volunteer and is matched using the system.
- Assignment: Items that can be broken down into many tasks and executed by the volunteer.
- Reviewers: Volunteers/Empact staff who ensure that a task has been completed and meets the certain quality standards.
- Feedback(System): Responses given by the volunteers within the system, after completing their task.
System Terminologies
- Question Module: The sub-system that allows different stakeholders to add, delete, update and manage questions within the system.
- Task Module: The sub-system that allows different stakeholders to add, delete, update tasks within the system.
- Task Review: The portion of the Task Module that encompasses the task review process by task reviewers and Empact staff
- Timesheet: The module that links with the Task Module to capture the hours committed by volunteers
- Feedback Form: The module that captures the feedback given by the volunteers
- Volunteer Records: The module that displays an overview and breakdown of all the activities committed by the volunteer
- Search: The functionality that allows users of the system to find items from a given list
- Statistics: The functionality that displays the key indicators of Empact's business performance and goals
- Dashboard: Front-page of the system that captures the key indicators for Empact's daily operations.
- Registration: The functionality that allows users to register to be an Empact volunteer
- Profile: The functionality that captures and displays the key information of the stakeholders within the system
System Description
DESCRIPTION
Team Box.us would be responsible for the design, development and implementation of a web application system and an iOS phone application. The web application would help Empact to perform automated matching of volunteers and provide an integrated management platform for its volunteers, its clients and its staff to handle volunteer matchings.
WEB APPLICATION
The Web Application would consist of the following functionalities: