HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2010T1 OOLaLa"

From IS480
Jump to navigation Jump to search
Line 135: Line 135:
 
====Milestone 1 (Week 1 to Week 3)====
 
====Milestone 1 (Week 1 to Week 3)====
 
#Feature Includes:
 
#Feature Includes:
 +
##Login Management
 +
###User who is authorized will be able to login to the system
 
##SMS Management
 
##SMS Management
 
###User is able to create new SMSes and mass send it to the contacts
 
###User is able to create new SMSes and mass send it to the contacts

Revision as of 13:04, 18 September 2010

We are OOLaLa

Why OoLaLa!

"It's all in the name!" - Doug Gavel, 2000

This quote explains the rationale of our team name.

Not only do we aim to complete our project according to plan and budget, we aim to leave you a lasting impression. A feeling that will make you going, Ooh La La!


Team OoLaLa!

Who's in?

What makes projects fun?.....You are not doing an assignment by yourself!


Though so, expectations and responsibiltiies of each team mate may be confusing when it is not well established.
Therefore,we value planning and organization of roles and responsibilities to bring about the successful completion of specific project goals and objectives we set.

Specific Project roles are assigned for each meeting to make us more prepared on the day itself.Functions of each role, restrictions, allowances of power, required materials to bring are documented.

Team members

  1. Alan Tan Beng Heng - Programmer
  2. Lur May Yee - System Analyst
  3. Maybelline Goh Shu Qing - Programmer
  4. Png Lee Hong - Project Manager
  5. Woo Kai Ling - Design Analyst

Roles and Responsibilities

Roles & Responsibilities

Non – Rotational Roles
The ability of being versatile in every role and being equally competent in every role is impossible. In recognition of each other's personality, strengths, weaknesses and technical capabilities, we have chosen to assign non-rotational roles.

Project Manager
• Ensures Project Team completes the project.
• Develops the Project Plan with team.
• Manages team’s performance of project tasks.
• Secure acceptance and approval of deliverables from Project Sponsor and Stakeholders.
• Responsible for communication, including status reporting, risk management, escalation of isues that cannot be resolved in the team, and in general, making sure the project is delivered in budget, on schedule, and within scope.

Design Analyst
• Creates detailed interaction and UI designs based on User Centered Design techniques and logical processes.
• Deliver user testing data, use case scenarios and feature research.
• Creates “developer ready” detailed functional design specifications for new product features based on defined business requirements.
• Assists in the visual design of graphical user interfaces.
• Offers solutions to complex design issues during all phases of product development cycle.

System Analyst
• Preapre detailed flow charts and diagrams outlining systems capabalities and processes.
• Collect information to analyze ans evaluate existing or proposed systems.
• Troubleshoot and resolve hardware, software and connectivity problems.
• Record and maintain hardware and software inventories.
• Write and maintain system documentation.
• Document systems problems and resolutions for future reference.

Programmer
• Code, debug, test and document routine application programs.
• Assist with design, analysis, maintainance, documentation, and testing of software.
• Install and test routine software packages.
• Assist with procedural or minor technical problems.
• Determine source data (input), processing requirements (output), output formats, timing and cost estimates.
• Verify that system meets performance criteria.

Our Goals

Objective and Goal of FYP
Our Project Management Strategies

Ground Rules

Communication mode

  1. Urgent: Phone Call,SMS
  2. Not Urgent: Msn, Email

Penalty

  1. Late comers: Buy drinks for everybody
  2. Overdue work:

Supervisor

  • Chris BOESCH [1]

Sponsor

  • Mr. Joel Chiang - Chirpy Communications LLP’s Managing Partner



OoLaLa's Project Scope

SystemFunction.jpg
For more details regarding our project's motivation and stakeholders, please refer to our Proposal Document.

Functionalities

Project Description

This project has been conceptualized to perform SMS functions with management features. This Application will be able to facilitate users in managing responses from SMS replies. Users will be able to create contact groups, send mass SMSes and keep track of the responses. Also, it has an Event Management feature which allows users to send event invitations via SMS and generate summary reports of the events.

Stakeholders

Sponsor & Client: Mr. Joel Chiang - Chirpy Communications LLP’s Managing Partner

Objectives

With introduction of an innovative feature, event invitation on mobile service, users will experience an enhanced feel of convenience in the management their event. We aim to develop aCoupled with our simple-to-use and user-friendly SMS Management Application, it will cater to our client’s demands. Although similar systems exist in the market, they are either too expensive or complex to use. With the introduction of our application, Chirpy would be able to leverage on a simple and effective solution that is better enhanced compared to its competitors. This application will be delivered to the sponsor as an executable file that is easy to install on a local computer, to be used by one or more users.

Features

Functionalities

SMS Messaging Feature

Functionalities

includes the management of Contacts
Functionalities

Event Management Feature

Functionalities includes the management of Contacts
Functionalities

Intelligent Report Feature

Functionalities

X-Factor

Interactive SMS Services

1. Mobile Event Management

Iphone? Andriod? Smartphones? We don’t need them now!
With our SMS service, you can Create Events On The Go! Anywhere you are!

  1. Used in any environment - Internet is not needed. A mobile phone that has a basic sms-ing function is all it takes.
  2. Hassel Free - Event managment can be done without any installation of mobile app.
  3. Service is FREE!


2. Auto Responding/Follow-up SMS
With an automated responder service, you can precomposed your message. This autoresponding message will immediately be delivered to your prospects via SMS.

OoLaLa's Project Management

"By failing to plan, you're planning to fail"

Our Team aims to carefully planned, monitored and tracked every project details to provide optimal management of project development.

Our Project Management Strategies

Milestone

We have established our milestone with tremendous consideration of our individual capability and deliverables/grading deadlines.
Milestone.jpg

Milestone 1 (Week 1 to Week 3)

  1. Feature Includes:
    1. Login Management
      1. User who is authorized will be able to login to the system
    2. SMS Management
      1. User is able to create new SMSes and mass send it to the contacts
      2. User is able to view new SMSes in the inbox
      3. User is able to save SMSes as draft or template
    3. Contact Management
      1. User is able to create new contacts
      2. User is able to create group and assign the contacts into group
      3. User is able to import and export contacts

Milestone 2(Week 3 to Week 6)

  1. Feature Includes:
    1. Event Creator
        1. User is able to create, modify and delete events
        2. User is able to mass send event SMSes once the event is created
        3. User is able to track the attendance of the invitees when they reply Y/N to the system
        4. User is able to view the events created and generate the event attendnace report
    2. Event Invitees
      1. Invitee will receive a auto reply when they confirm their attendance
      2. Invitee will receive update SMS when the User updates the event

Milestone 3(Week 6 to Week 10)

  1. Feature Includes:
    1. Event Creator
      1. Create Event
      2. Modify Event
      3. Delete Event
      4. Track Attendance
    2. Event Invitees
      1. View Event Details
      2. Receive Event Updates

Milestone 4(Week 10 to Week 13)

  1. Feature Includes:
    1. Event Creator
      1. Managing Multiple Event
      2. Manage SMS Events Replies
      3. Auto Response
      4. Receive events replies
    2. Additional Feature Development

Work Breakdown Structure

In order to complete our functionalites on time, each complex function has been broken down into task in a hierarchical structure. Breaking down each function into the manageable and feasible tasks helps us in allocate resources and roles efficiently.

WBS plan shows work items and packages that are consistent with the milestone developed and shown in our proposal report.Vague terminologies are not used to prevent potential confusion and misunderstanding.

These following information were provided along with each work package.

  1. Description of each work item
  2. Work deliverables

All deliverables required for each package has been clearly defined to prevent confusion and misunderstanding.

  1. How we intend to get it done
  2. Resource and role allocation
    1. Work item should only be allocated to a single member. Allocated member will be responsible for the work item successful completion.


OUR WBS (Abstract Version)

  1. Entire project
    1. Project Preparation
      1. Define Project Management
        1. Roles and Responsibilities, Risk Analysis,WBS Schedule, Resource Evaluation, Milestones, Metric, Scope Management
    2. Define Design and Analysis
    3. Phase 1*
    4. Phase 2*
    5. Phase 3*
    6. Product Delivery
    7. Final presentation
  • Phase 1,2, and 3 are milestone phases follows iterative methodology and features higher frequency of application developmental procedures

Functionality WBS approach

  1. Establish Event Flow and Logic
  2. Implementation
  3. Test
    1. Functionality Test by Observer
    2. Interface Design Test by anyone (except for the team members)

Top-down Approach in developing our WBS

As a team we found that it would be better to focus on getting the top levl done well before refining the work into greater and greater level of detail.

Schedule

Project Developmental Strategies

  1. Milestone
  2. Adopted Iterative Process
  3. Iteration Deliverables

Strategy Used For Schedule Planning

  1. Tasks assignment and meetings arrangments were made with consideration of each other's schedule and commitments.
  2. Buffer Time are given to each task
  3. Schedule tasks realistically with risk analysis, schedule metric and prior experiences

Meeting Frequency

Team Regular Meeting Minutes

Regardless of each other's commitments, we will meet at least once a week(full attendance).
The following informations are discussed during our regular meeting:

  1. Meeting Agenda
  2. Progress Update
  3. Review of Each Other's Task
  4. Other information with regards to our schedules
Supervisor Meeting Minutes

Adopted Software Processes

There is no one-size-fit-all process
Every project complexity, team dynamic and project size demands a different project management strategy. With recognition of available software processes, the following best practices have been adopted.

  1. Pair Programming
  2. Continuous Integration
  3. Small Releases
  4. Coding Standards

These practices serve as a basis for planning, organizing, coordinating, and directing our system development.

Team Bonding Session

There should be a balance between work and play. We believe that having regular team bonding session is crucial as we strive to work cohesively as a team.
We make an effort to have lunch together before or after our regular meetings. After each iteration deliverables, we plan to treat ourselves to some rewarding outings.

Liaising with Sponsor

Supervisor Meeting

Metric

Metric is utilized to monitor both functional and non-functional aspects of our FYP project.

Functional Metric

    Mantis Online Bug Tracking System
      Our Goal : To monitor the number of bugs in the system and keep it below the recommended level
      Question : Do we consider small bugs? How do you determine that a bug is critical and one that isn't?
      How we measure : Daily? Weekily?

Non-Functional Metric

1. Schedule Metric

      Our Goal: Improve schedule estimation accuracy to within 10% actual
      Question:How accurate is our estimates
      Formula:Estimated/Actual Time
      How we measure
    1. Estimated Time for each Task
    2. Actual Time for each Task

2. Team Metric

      Our Goal: Improve quality of project menagement in the team
      Question: How do we make everyone happy? How do we define happiness?
      Formula:Current Happiness/Accumulated Happiness
      How we measure
    1. Specific questions with scale clearly defined
    2. By being honest

    Resource Analysis

    Technology Used

    Risk Management Analysis

    Risk identified in Business Requirement Gathering Risk identified in Hardware Compatibility Risk identified in Software Compatibility

    OoLaLa's Learning Outcome

    Learning Outcome

    Credits

    Proudly done by:

    Our Team