Difference between revisions of "IS480 Team wiki: 2011T1 Motiva"
Line 675: | Line 675: | ||
===Individual Reflection=== | ===Individual Reflection=== | ||
− | ====<font size=' | + | ====<font size='4' color='DarkOrange'>Daniel Ong</font>==== |
− | =====Learning Outcome===== | + | =====<font color='white'>Learning Outcome</font>===== |
− | |||
{| class="wikitable" style="border:1.5px solid #000000" | {| class="wikitable" style="border:1.5px solid #000000" | ||
|- valign="top" | |- valign="top" | ||
Line 769: | Line 768: | ||
|} | |} | ||
− | =====Reflections===== | + | =====<font size='3'>Reflections</font>===== |
+ | *To be filled | ||
===Sponsor Comment=== | ===Sponsor Comment=== | ||
*To be filled | *To be filled |
Revision as of 00:56, 17 July 2011
Contents
Team Members
Name | Role |
---|---|
Tay Hui Juan | Project Manager |
Ong Wee Chian | Assistant Project Manager & UAT Administrator |
Chong Liang Jin Eugene | Lead Developer |
Ting Wen Zhong | Technical lead & Creative Designer |
Ong Shin Jie Daniel | Business Analyst & Communication Director |
Click here for role description.
Project Scope
Project Description
Buy One Give One is a non-for-profit organization that provides systems and structure to inspire the community about a world full of giving. Buy1Give1 is currently registered and headquartered in Singapore. B1G1 currently works with businesses in 15 countries. Through B1G1 those businesses now support close to 700 projects in 29 countries.
To make giving a habit and to move away from the normal guilt-driven and event-driven fund raising, B1G1 uses a transactional based business model where businesses and individuals can continuously contribute to various projects with a focus NOT on the funds donated but on the IMPACT created. The current B1G1 online portal serves as a platform for business to enrol to these programs. As a result of the most recent IS480 project, B1G1 is moving now to attract more personal users to its previously heavily SME focussed platform with what it calls the ‘Design Your Giving Life’ initiative.
Stakeholders
Organisation | Name | Position |
---|---|---|
Buy One Give One | Masami Sato | Founder, Director |
Buy One Give One | Paul Dunn | Chairman |
Modules
User Management
New and existing users will be able to create a new contributor account at B1G1. With Facebook and Twitter connect, user may use their existing social media account as login information. Mandatory data such as names and email will be collected and stored in B1G1 database for bookkeeping. All user information is linked to the B1G1 customer database meaning any activity done through the web and iPhone application will be automatically synced. Additional privacy settings are available in user profile. The account management tool also allows users to manage the account settings such as changing and resetting of password. |
Project Listing Management
All funding projects are listed by different lifestyles (dining, shopping, etc) or pre-defined categories (Country, organization, types of targeted beneficiaries such as education, health and welfare, environment and so on — broadly in line with UN Millennium development goals). |
Contribution Management
A major (and new) key here is user-personalisation. We aim to create ‘Giving Goals’ to allow an individual user to link giving to personally defined goals (it might be weight loss, gym attendance even kissing a spouse!). It means that users can then create fun challenges and link them directly to giving.
Once a goal is selected, the user can then (through iPhone ‘dials or drop downs’ link to major giving areas (based on the 8 UN Millennium goals for example) and from that to specific projects. This feature serves as a central management for all contribution by B1G1 users. Users will be able to make payment for all selected projects. Information such as donation preferences (e.g. for every coffee purchased), the project you embarked on, the amount to donate will be automatically saved in user’s preset profile. This module will trigger an update to the achievement module and the live feeds on his/her profile. When a user initializes a contribution, the information stated on the presets will be made together with their location taken from the in-app location based services. Once the user accumulates to a donation amount he/she can check out to the payment module. The user will also be able to set a wide variety of reminder to aid in making giving a habit (in a fun way as well) |
Connectivity & Engagement
Our team plans to utilize the location-based elements already built in to the current B1G1 platform to allow individual users to locate (and then shop with) business users. We also plan to use information from the App as a resource to share with simple processes across common social networks (as a minimum, Facebook and Twitter). From every contribution, user can do photo tagging with information gathered from its GPS location, lifestyle activity and related project details. These data will first be updated to a database and all users from B1G1 Facebook group could view this information as wall feeds. User may choose to post it on their personal wall as well. In addition, B1G1 will also design a new web-based dashboard to keep track of real-time contribution and activities from B1G1 users worldwide. |
Achievement Management
User achievements are directly related to the number of projects they have helped and their total monetary contributions. Medals and Trophy will be awarded to users based on the pre-determined levels. User may view all their contribution history. To improvise the application with more interactivity and challenging factors, there will be different number of achievements for users to attain. |
Deliverables
Storyboard
- Click here to download the storyboard (sketched mock design).
User Interface (UI)
- Coming soon
Use Case
Application Architecture
Deployment
- To be filled
X-Factor
- Launch of application to Apple App Store
- Users are able to geo-tag their lifestyle photos with the donation activities on Facebook
Project Management
Scope Management
Scope management is one that plays a crucial part in project management. Managing the scope well would prevent the team from doing unnecessary rework. It allows us to plan ahead and to prevent breakdowns if there are scope changes. Drawing out the scope would enable everyone to have a clear picture of project and gets work done more efficiently. We have to know what is to be built before building it.
Scope Management Process
I. Collect Requirements
We collected requirements through interviews with the client and through brainstorming.
II. Define Scope
Scope:
Click here to view our project scope.
Deliverables:
Click here to view our project deliverables.
III. Create Work Breakdown Structure (WBS)
Work Breakdown Structure (WBS) - Abstract:
IV. Control Scope
There are bound to be changes in the scope during the course of the project. We are unable to predict when will a change occur. As such, we would adopt the following process if a change needs to happen.
V. Verify Scope
To verify the scope, we have to compare the deliverables with the project requirements. This is crucial to ensure that the project does meet the requirements. This will be done before the UAT where the client evaluates our deliverables.
Time Management
To ensure that work is done and deadlines are met, time management is important. In order to prevent overruns and inefficiency in our course of project, we made use of a project schedule. The project schedule is important in helping us plan ahead and estimate the amount of time we have for each function. Proper time management would be a key to success.
Process Description Actions to be taken Define Activities Adopted the decomposition technique by further breaking down the core functions into tasks Sequence Activites Determine the precedence of each tasks in a relationship diagram, using the Precedence Diagramming Method (PDM) Estimate Activity Resources Discussion as a team Estimate Activity Duration Discussion as a team Develop Schedule Draw up schedule in MS Project Control Schedule Adopt a schedule metric to determine whether we are Early/On-time/Late
Project Timeline
Project Schedule
Click here for detailed project schedule.
Schedule Metric
- coming soon
Relationship Diagram
- coming soon
Quality Management
It is important that we understand the quality expectations of the client. As such, we manage the quality of our project by settings goals and taking measurements.
Process Description Actions to be taken Plan Quality Set goals. (Eg. Number of bugs, bug metric) Perform Quality Control Quality checklist (Test cases), Constant testing after each iteration, Track bugs using Bug Metric Perform Quality Assurance Obtain feedback from UAT and Client Evaluation
Bug Metric
- coming soon
User Acceptance Test (UAT)
- coming soon
Test Plans
- coming soon
Test Cases
- coming soon
Communications Management
To ensure that everyone in the team is aware of the event and tasks, we make use of a communication plan. Communication is important in preventing any breakdowns or errors.
Communication Plan
Event Rationale Frequency Deliverables Team Meetings Project discussions, updates on project developmentProject discussions, updates on project development Weekly Meeting minutes to be uploaded Client Meetings Clients’ feedbacks, project updates Weekly Meeting minutes to be uploaded Supervisor Meetings Supervisor feedbacks, update on project progress Fortnightly Meeting minutes to be uploaded Client Updates Update client on deliverables after each milestone After each milestone Meeting minutes to be uploaded Sharing Sessions Peer feedbacks, comments and thoughts about the team Monthly Resolved issues, Peer feedback Team Bonding Sessions To maintain team cohesion Monthly Have dinner/movies/outings
Team Meetings
Date of meeting Meeting Minutes Venue 27th April 2011 Minutes 01 SIS GSR 2.1 14th May 2011 Minutes 02 SIS GSR 3.1 18th May 2011 Minutes 03 SIS GSR 2.5 23rd May 2011 Minutes 04 SOB GSR 2.7 31st May 2011 Minutes 05 SOB GSR 2.10 04th Jun 2011 Minutes 06 SOB GSR 3.4 11th Jun 2011 Minutes 07 SOB GSR 2.7 17th Jun 2011 Minutes 08 SIS GSR 2.1 24th Jun 2011 Minutes 09 SIS GSR 2.5 01st Jul 2011 Minutes 10 SIS GSR 2.5 09th Jul 2011 Minutes 11 Library Level 2 14th Jul 2011 Minutes 12 SIS GSR 2.5
Supervisor Meetings
Date of meeting Meeting Minutes Venue 07th July 2011 Minutes 01 SIS Level 5 Room 34
Risk Management
Risk Breakdown Structure
Risk Analysis
Technical Risk
Risk Description Impact (Low/Medium/High) Probability (Low/Medium/High) Rating Mitigation Strategy Impact of Strategy Minimal professional training on Cocoa (API) and Objective-C programming language used in Mac application development Medium Medium B Source for Apple training program and reading up eBooks from library and internet More time spent on research, peer sharing sessions and self-learning for the team. Quality issues like application bugs and synchronization with B1G1 database may surface. Medium Medium B Design more test cases and increase testing frequencies each iteration. Engage a higher number of users during User Acceptance Test (UAT) More time incurred for carrying out more tests and design more test cases
Business Risk
Risk Description Impact (Low/Medium/High) Probability (Low/Medium/High) Rating Mitigation Strategy Impact of Strategy Conflicting clauses in placing charitable transaction based services in the application for Apple AppStore billing system High Medium A Use an external link which brings user out from the application to a web browser for further payment process Reduces user experience.
External Risk
Risk Description Impact (Low/Medium/High) Probability (Low/Medium/High) Rating Mitigation Strategy Impact of Strategy Client requirements may change during the course of project resulting in change of scope High High A Enforce the scope change process. Ensure that all documentations are up to date and that all members of the team are aware of the scope changes. More time required on ensuring proper documentation for each change.
Risk Metric
LOMS
Learning Outcome
Description | Plan to Realize Learning Outcome(s) | Method(s) of Measurement |
---|---|---|
IT Architecture Design and Development Skills | ||
System Requirements Specification Skills |
|
|
Software and IT Architecture Analysis, Design Skills |
|
|
User Experience Simulation & Design (Internal) | Understand Business and Consumers needs to provide an intuitive workflow with minimal learning curve on the application |
|
Implementation Skills |
|
|
Technology Application Skills |
|
|
Project Management Skills | ||
Scope Management Skills |
|
|
Risk Management Skills |
|
|
Project Integration and Time Management Skills |
|
|
Configuration Management Skills |
|
|
Quality Management Skills |
|
|
Learning to Learn Skills | ||
Methodology for Group Learning |
|
|
Collaboration (or Team) Skills | ||
Improve Effectiveness of Group Processes and Work Products |
|
|
Communication Skills | ||
Presentation Skills |
|
|
Writing Skills |
|
|
Project Progress Summary
Highlights
- To be filled
Challenges
- To be filled
Achievements
- To be filled
Reflection
Team Reflection
- To be filled
Individual Reflection
Daniel Ong
Learning Outcome
Description | Plan to Realize Learning Outcome(s) | Method(s) of Measurement |
---|---|---|
IT Development Skills | ||
System Requirements Analysis and Gathering |
|
|
Software System and User Interface Design |
|
|
User Experience Simulation & Design |
|
|
Implementation Skills |
|
|
Technology Application and Programming Skills |
|
|
Project Management Skills | ||
Scope Management Skills |
|
|
Risk Management Skills |
|
|
Time Management Skills |
|
|
Documentation Skills |
|
|
Quality Management Skills |
|
|
Communication Skills | ||
Presentation Skills |
|
|
Documentation Skills |
|
Reflections
- To be filled
Sponsor Comment
- To be filled