HeaderSIS.jpg

IS480 Team wiki: 2010T1 TouchPoint:TouckPoint Mid term Wiki

From IS480
Jump to navigation Jump to search

TouchPointLogo.png

Project Progress Summary

Project Highlights:

Since the Project Acceptance Presentation, below are some the key happenings for the project:

  • Research and created 2 additional versions of the User Interface design before finalizing it to the current version
  • Added the following functionalities/ features to the application:
    • View Promotions
    • 360° viewing of rooms
    • Hotel location with Geo-location capabilities
  • Re-organization of project schedule
    • Prioritize functionalities and develop core and important functionalities first
    • Group functionalities with similarities to develop
    • Create a new iteration, Construction 4
    • Pushed all administrator’s functionalities to Construction 4
  • Perform UAT Testing with Project Sponsor
  • As a result of the re-organization of the project schedule, the contingency period of the project was reduced from 30 days to 15 days.

Project Management

Project Schedule (Plan Vs Actual):

There has been a major re-organization of the initial proposed project schedule. Below are the key changes made to the project schedule:

  • Due to technical difficulties, the Mobile Check-in Use Case was pushed from Construction 2 to the next iteration as further research and discussion with the Project Sponsor is required. Amenities Booking, Cancel Amenities Requests and View Amenities functionalities are also pushed from Construction 2 to Construction 3.
  • Due to some unforeseen personal issues and commitments, the team faced difficulties with time. In order to minimize risks, the schedule was reorganized based on priorities of functionalities with the functionalities of high priority (or core functionalities) to be developed first.
  • An additional iteration, Construction 4 was added. All administrators’ functionalities are pushed to this iteration.

Tp mt 1.png Tp mt 2.png Tp mt 3.png Tp mt 4.png

Project Risk

Overall risks

TP midterm risks.png

Project Risks Risk statement Mitigation strategy Status (as of mid term)
Communication breakdown in team Without proper documentation, team members might not be on the same page and do not have common understanding of the project.
  • Use “Unfuddle” to manage work allocation and deadline
  • Use drop box for file sharing
  • Take clear minutes and store in dropbox after each meeting for future review and for any absent member.
This probability of this risk changed from Likely to Unlikely. The mitigation strategy has shown positive results and team members are comfortable with the current communication methods, minimising the risk.
New to ObjectiveC Team members are new to iPhone development platform. The steep learning curve might delay the project schedule.
  • Ken and Khoa who have some expertise in programming will provide training and guidance to the team.
The probability of this risk remains as very likely. Hence the additional of the new risk of finding bugs in Apple API.
Misinterpret client requirement We might misunderstand client’s requirements and hence cannot meet their expectation.
  • Show the client a mock screen shots of the application to illustrate the process flow.
  • Give client the prototype earlier in the development stage to get feedback.
  • Meet client and review the progress at the end of each iteration.
This probability of this risk changed from Very Likely to Not Unlikely. With multiple mock-ups and regular reviews, the project sponsor is constantly keep aware of the team development and able to provide feedback is requirements is misunderstood at any point.
Unavailability of team member Due to unforeseen circumstances, team member might not be available.
  • Assign tasks in a way that at least two people is working on the same thing, so one can take over when the other is not available.
  • Clearly document the progress of each task on Unfuddle to update the rest of the team members.
This probability of this risk changed from Likely to Very Likely because one of our team member indeed faced some personal problems during the project. This therefore increased the probability of the risk.
Unable to connect to the hotel’s back end system For some features, we need to connect to the hotel, without hotel’s permission, we cannot implement those features.
  • Focus on features that do not require connection to hotel back end system in the earlier stage of the project. Without the permission, we still can have a workable project that will benefit hotel clients.
This is no longer valid as both the team and the project sponsor have come to an agreement that we will not be connecting to the backend system due to complications and concerns. The team will instead develop a mock-up of the backend system, comprises of the backend server and database.
Application is rejected by iTunes store iTunes store is our main distribution channel, allowing us to reach more users.
  • Team need to read and be familiarised with iTunes application guidelines before designing the application.
This risk is no longer valid as the project sponsor has decided to keep the final outcome of the project as a prototype.
Inexperience in the luxury hotel industry We might not understand hotel guests’ needs and expectation, hence unable to provide best user experience
  • We need to work closely with the client.
  • Do a walk through of the program with the client at every feedback gathering meetings.
This probability of this risk changed from Very Likely to Very Unlikely. During the development of this project, the team has acquired great understanding and industry knowledge from sharing with our project sponsor and fellow member, who is taking a module related to hospitality, known as World Travel and Tourism. The team also did regular walkthroughs of the program, minimising the impact of inexperience in the industry.
Different level of technical expertise in the team Some team members have more experience in programming than the others. This might hinder the efficiency of job allocation and different working pace.
  • More experienced member will guide the less experienced ones.
  • Allocate longer time for weaker coders when planning the project schedule.
The probability of this risk changed from likely to unlikely. Tasks are allocated according to the each member's strength. Up to the mid point of the project, we have not seen any problem arising due to this issue.

New risks discovered after project acceptance

Project Risks Risk statement Mitigation strategy Status (as of mid term)
Unavailability of Project Sponsor Due to commitments, our project sponsor may not be available to meet us.
  • Update project sponsor though emails with current developments, screenshots of application and upcoming developments
  • Install app with completed components into his iPhone.
This is a new risk discovered and it is Very Likely to happen.
Bugs in Apple iOS 4.0 SDK affecting development During development, some bugs are discovered within Apple iOS 4.0 SDK and awaiting updates from Apple which may affects the feasibility of some proposed app features.
  • Conduct a review of scope and specifications after each iteration
This is a new risk discovered and it is Very Likely to happen.

Technical Complexity:

  • Understand and efficiently make us of iOS's massive library.
  • Find a way to work around bugs in iOS API.
  • Threading in iOS
  • Manual handling memory
  • UI design

Quality of product

Intermediate Deliverables:

User Interface Design

Version 1: Initially planned in an iPad

ScreenCatalog.png
ScreenF&B.png
ScreenMyAccount.png

Version 2 sketches - adapt to display on iPhone

Restaurant.jpg
Facilities.jpg
Spa.jpg
My Profile.jpg

Version 2

IMG 0063.PNG

Version 3 Enhance look and feel of the overall design. Re-organisation of information

TP culinary.PNG
TPRooms.PNG
TPRoom.PNG

Testing

Functional Test plan: Media:Fucntionla test mid term.docx

Functional testing is done at the end of each iteration, before the start of the next one. We have completed 3 internal testings.

Before the start of every meeting with our sponsor, we did a user testing with him to get his feedback at each stage of development.

We did one formal UAT testing with the project sponsor in week 6.

Deployment:

The application can be deployed in any iPhone, given that we have the device's UDID. We get the UDID of our sponsor's iPhone and sent him an ad-hoc built, so that he can use the app on his phone.

Reflection

Team Reflection:

Firstly, the team has acquired substantial amount of industry knowledge from research and sharing from our Project Sponsor. The team has utilised the knowledge and in designing the User Interface for a mobile app catering to the needs of Pan Pacific Hotel. In the process, the team has also learnt about the various techniques and types of user interactions that can be used to improve user experience in using the mobile app.

Secondly, the team, especially Ken and Khoa, has managed to learn new techniques in programming using the iOS 4.0 SDK and Objective-C. They are also able to acquire what they have been exposed during the WDC Apple Conference that they attended prior the start of the FYP.

Finally, the team has been exposed to executing project management to a real client. The team learnt how important to “Under Promise and Over Deliver” to manage expectations of the project sponsor and team members. The team has also learnt how to handle various risks and managed to realise how it affects the project schedule.

Benjamin Gan Reflection:

“The first development are promising, clear in the design and concept. The completion of the project will change the way both hotel associates and clients receive and share information. It will also open the gate to a wider spectrum of possibilities. Keep up the good job!”

Mr Jean P Lovotti

Rooms Division Manager

Pan Pacific Singapore