HeaderSIS.jpg

IS480 Team wiki: 2010T1 dAPi

From IS480
Jump to navigation Jump to search
Team dAPi


Our People

Team Supervisor

Chris Boesch when he's coding Chris Boesch

SIS Practice Professor
School of Information Systems
Email: cboesch@smu.edu.sg
Phone: +(65) 6808 5110

Team dAPi

Alex aka Hurley Cedric aka Carebear Ivy aka Broccoli May aka Bear Sarah aka Benditlikebeckham
Alex Cedric Ivy May Sarah

Our Liaison Officer

Mrs Koh Lian Chee
Standard Chartered Bank iLab Program Manager
SIS Senior Instructor
School of Information Systems
Email: lckoh@smu.edu.sg
Phone: +(65) 6828 0569

Mrs Koh

Our Client/Sponsor

Christine Tan Su Yong
iLab Project Manager
TSD Channels
Standard Chartered Bank
Email: Tan.Christine-Su-Yong@sc.com

Christine

The Team

Our team name is inconspicuously related to our project in a simple and playful manner. In fact, if you carefully spell our team name backwards, you will figure it out. How the name came about was a short and sweet story with a twist of serendipity. At one of our first few meetings, we were just tossing ideas around for a team name until we started to manipulate the word iPad. An iPad spelled backwards forms the word dapi, simple yet rather elegant even though it would be cool if it was a palindrome. The name aligns with our team motto, to keep things "short and simple".

Roles

Role Responsibilities Member(s)
Project Manager
  • Manage any project issues
  • Manage and track schedule
  • Identify, manage and mitigate risk
  • Ensure quality of solution
  • Proactively manage the scope of the project to meet requirements and deadlines
  • Collect metrics to give a sense for how the project is progressing and whether the deliverables produced are acceptable

Alex

Secretary
  • Record the minutes of every meeting within the group and with the sponsors
  • Remind project manager of deadlines
  • Disseminate project information to all stakeholders

Sarah

Business Analyst / Liaison
  • Ensures that the requirements set forth by the clients are captured correctly before the solution is developed and implemented.
  • Ensure that any project implementations or changes are understood by the clients and the project team
  • Help in defining the acceptance criteria for completion of the solution
  • Main point of contact with client

May

Lead Designer
  • Understand the business requirements and design a solution that will best meet the business needs.
  • Go into the minute level of designing; UI, programs and other components
  • Determine the data required
  • Drafting of design documents; use case, SD, SSD

Ivy

Chief Developer
  • Actualize the design plans
  • Decide and set the coding convention
  • Responsible for the integration and deployment of the application

Cedric


Scrum Roles

Role Description Responsibilities Member(s)
Scrum Master The Scrum Master is responsible for the Scrum process. He ensures everybody plays by the rules. He also removes impediments for the Team
  • Manage the Scrum process
  • Facilitate communication
  • Holds daily 15 minute team meeting (Daily Scrum)
  • Removes obstacles Shields the team from external interference
  • Maintains the Sprint Burndown Chart
  • Conducts Sprint Retrospective at the end of a Sprint
  • Is a facilitator not a manager
Alex
Product Owner The Product Owner represents the interests of everyone with a stake in the project (Stakeholder) and he is responsible for the final product
  • Accountable for product success
  • Elicit product requirements
  • Responsible for prioritizing product features
  • Maintains the Product Backlog
  • Manage the release plan
May
Pigs People who are accountable for the success and deliverables of the project Ivy,

Sarah, Cedric

Chickens People who are not accountable for the success and deliverables of the project Christine,

Lian Chee, Chris

Our Project

Project Description

Technologies Involved

Technology Description
QR Code
dAPi QR Code
  • A QR Code is a matrix code (or two-dimensional bar code) created by Japanese corporation Denso-Wave in 1994. The "QR" is derived from "Quick Response", as the creator intended the code to allow its contents to be decoded at high speed. QR Codes are common in Japan, where they are currently the most popular type of two-dimensional codes. Most current Japanese mobile phones can read this code with their camera.
  • For the purpose of our project, we would like to incorporate this technology into our application. We intend to leverage the capabilities of QR technology to export information to customers seamlessly through the use of simple imaging devices. They could simply capture the QR code generated by our application, using a QR reader readily available in the market to decode and extract the information.
Apple iPad
iPad
  • Apple’s latest toy for the tech savvy, the iPad will pave the way for a new user experience on mobile devices. Created as an heir to the well-received iPhone, the iPad will be a hot contender for the netbooks.
  • As such, with its mobility and interactive capabilities, we aim to provide the end users with a rich user experience at the bank.


Plan

Project Milestones

Milestones Description Week Date Term Week
1 Finalize initial requirements 07 16 Jun N/A
2 Iteration 1 09 01 Jul N/A
3 Present prototype solutions to sponsor 12 22 Jul N/A
4 Project acceptance 15 13 Aug N/A
5 Iteration 2 16 16 Aug 01
6 Iteration 3 17 23 Aug 02
7 Iteration 4 19 06 Sep 04
8 Iteration 5 20 13 Sep 05
9 Iteration 6 - Final UAT 22 27 Sep 07
10 Deployment 23 03 Oct 08
11 Documentation and end-user training 23 04 Oct 08
12 Initiate handover 28 01 Nov 12

Workplan

Week Term
Week
Date Description Iteration Remarks
Iteration 1 : Develop Prototype
9 N/A 01-Jul Present paper prototype to Christine 1
10 N/A 05-Jul Create xib files for functions UI 1
11 N/A 12-Jul Implement navigation 1
12 N/A 22-Jul Present iPad UI prototype and collect feedback from sponsor 1
13 N/A 26-Jul Review Application UI 1
14 N/A 02-Aug Preparation for Project Acceptance -
15 N/A 13-Aug Project Acceptance -
Iteration 2 : Implement Basic Functionalities 1
16 1 Function 1 2 Meet Supervisor
16-Aug • Refine User Interface
16-Aug • Implement View Navigation
18-Aug • Develop functionalities
20-Aug • Integration of Views and Functionalities
22-Aug • Testing
Function 2 2
16-Aug • Refine UI
16-Aug • Implement View Navigation
18-Aug • Develop Functionalities
20-Aug • Integration of Views and Functionalities
22-Aug • Testing
Iteration 3 : Implement Advance Functionalities 1
17 2 Function 3 3 Meet Sponsor
23-Aug • Refine UI
23-Aug • Implement View Navigation
25-Aug • Develop Functionalities
27-Aug • Integration of Views and Functionalities
29-Aug • Testing
Function 4 3
23-Aug • Refine UI
23-Aug • Implement View Navigation
25-Aug • Develop Functionalities
27-Aug • Integration of Views and Functionalities
29-Aug • Testing
26-Aug Iteration 2 “Mini” UAT (Sponsor) 3
18 3 Function 5 3 Meet Supervisor
30-Aug • Refine UI
30-Aug • Implement View Navigation
01-Sep • Develop Functionalities
03-Sep • Integration of Views and Functionalities
05-Sep • Testing
Iteration 4 : Implement Basic Functionalities 2
19 4 Function 6 4 Meet Sponsor
06-Sep • Refine UI
06-Sep • Implement View Navigation
08-Sep • Develop Functionalities
10-Sep • Integration of Views and Functionalities
12-Sep • Testing
Function 7 4
06-Sep • Refine UI
06-Sep • Implement View Navigation
08-Sep • Develop Functionalities
10-Sep • Integration of Views and Functionalities
12-Sep • Testing
09-Sep Iteration 3 “Mini” UAT (Sponsor) 4
Iteration 5 : Implement Advance Functionalities 2
20 5 Function 8 5 Meet Supervisor
13-Sep • Refine UI
13-Sep • Implement View Navigation
15-Sep • Develop Functionalities
17-Sep • Integration of Views and Functionalities
19-Sep • Testing
21 6 Function 9 5 Meet Supervisor
20-Sep • Refine UI
20-Sep • Implement View Navigation
22-Sep • Develop Functionalities
24-Sep • Integration of Views and Functionalities
26-Sep • Testing
23-Sep Iteration 4 “Mini” UAT (Sponsor) 5
Iteration 6 : Final UAT & Tweaking
22 7 27-Sep
(TBC)
Overall Testing & Feedback from Sponsor 6
28-Sep Final Amendment 6
23 8 03-Oct Deployment -
05-Oct Documentation -
08-Oct End-User Training -


Housekeeping

Punctuality

How do we deal with members who are late for meetings? We have implemented a fine system to deal with such problems, and seriously it is effective!

The "Fine" Table

Assuming that the meeting is at 10.00 am. Once late, initial fine is $2.00. Every subsequent 5 minutes will cost another $0.50! Fortunately, the fine is capped at $5.00 so we don't end up starting our very own loanshark business.

Time of Arrival Fine
9.59 am $0.00
10.00 am $0.00
10.01 am $2.00
10.15 am $2.00
10.16 am $2.50
10.20 am $2.50
10.21 am $3.00
10.41 am $5.00
11.00 am $5.00
ArrayOutOfIndex Exception
Amount fined Scenarios
Late for the first 15-mins
$2

10AM meeting but member arrived at 10.05AM

Late for the more than 15-mins
$2 + additional $0.50 for each subsequent 5 mins

10AM meeting but member arrived at 10.16AM ($2 + $0.50)

Note: Fines will be collected immediately!! Ouch.. : )

Communication Protocol

CommProtocol.jpg

Wonder how we remind each other about our team meeting?

  • Reminder will be sent 1 day before actual meeting day via SMS
  • Reminder will be sent in a sequential cycle (refers to above image)
  • Each team member is responsible to remind another team mate
  • The first person to send the reminder will be the last person to receive it


Learning Outcomes