HeaderSIS.jpg

IS480 Team wiki: 2010T1 The Green Reapers: Communication and Decision Log - Sep

From IS480
Jump to navigation Jump to search

Communication and Decision Log: Jul | Aug | • Sep • | Oct | Nov

Back to Home Page



Key

ColorRepresents
 Client / User / Supervisor Interactions
 Progress Updates / Risk Assessments
 Integration and Testing
 Architectural Reviews
 Presentations




[ Sep-03 ] : Team Server Setup and Initial Component Deployment

Agenda

  • Set up deployment environment and services on team server (Windows 2008 Server)
  • Deploy basic system components (from Iteration 1) on team server
  • Identify possible integration challenges


Learning Points

# Item Details
01 Text-to-Speech functionality broken due to differences in server hardware. To be resolved with the hosting service provider, and hosted on a local machine in the meantime.
02 Overall architecture was easy to deploy on the server. Modular architecture and use of standardized, open-source technologies made it easy to set up the components.
03 Core deployment services configured and running Wordpress, MySQL, XAMPP, IIS




[ Sep-12 ] : Integration and Testing

Agenda

  • Deploy updated system components (from Iteration 2) on team server
  • Manually test entire system flow, with emphasis on inter-component communications


Learning Points

# Item Details
01 (Rollover from previous integration) Text-to-Speech functionality broken due to differences in server hardware. To be resolved with the hosting service provider. Text-to-Speech functionality to be tested and hosted on local development machines in the meantime.
02 IVR system unable to post to CMS for the moment. Self-coded web services on both ends need to be tweaked.




[ Sep-12 ] : Progress Update / Risk Assessment

Agenda

  • Assess project schedule and risks


Decisions

# Item Details
01 Team server has problems hosting Text-to-Speech functionality. We're investigating the issue independently and with the hosting provider. We expect this issue to be solvable. Development not affected in the meantime.
02 Development is going according to plan, team is comfortable with the pace. New architecture has very much reduced developmental headaches and requirements.
03 Team is comfortable with the risks managed. Mitigation strategies are working.




[ Sep-14 ] : Meeting with Project Supervisor and Dean (by chance)

Agenda

  • Sharing project plans, direction and aims
  • Getting feedback on pitching, project management and progress


Learning Points

# Item Details
01 Need to be sharp about framing the value and nature of the project
  • Define user profiles and needs
  • Be clear to edit the scope of the project to focus on the users
02 Real-world testing is important; can't just build in a vacuum
  • UAT for the various targeted user profiles - scientists and field workers




[ Sep-21 ] : Integration and Testing

Agenda

  • Deploy and integrate updated system components (from Iteration 3) on team server
  • Test entire system flow, with emphasis on inter-component communications


Learning Points

# Item Details
01 (Rollover from previous integration) Text-to-Speech functionality broken due to differences in server hardware. To be resolved with the hosting service provider, and hosted on a local machine in the meantime.
02 (Rollover from previous integration) IVR system unable to post to CMS for the moment. Self-coded web services on both ends need to be tweaked.
03 Other analytics, IVR configuration and CMS components deployed successfully. Data structure and system architecture work great.


[ Sep-24 ] : Meeting with Supervisor

Agenda

  • Review project pitch
  • Review current and planned functionality
  • Review project direction and scope


Learning Points

# Item Details
01 Pitch
  • Ensure project pitch is simple and strong
  • Prepare a short pitch as well as a long pitch
02 Goal and Direction
  • Ensure goal and direction is certain
  • Review IRRI's role in the project
  • If IRRI is interested, would we be prepared to do more, i.e. facilitate more functions
03 Risks
  • Project very reliant on client data
  • Deployment on client server might be essential, which poses another risk

[ Sep-25 ] : Progress Update / Risk Assessment

Agenda

  • Assess project schedule and risks
  • Prepare for Mid-Term Presentation


Decisions

# Item Details
01 Development is going according to plan, team is comfortable with the pace. Certain bugs remain, but team is confident of addressing them.
02 Found possible resolutions for Text-to-Speech issue on team server Team has identified possible hardware and software solutions, and are testing them with the hosting provider.
03 Team is comfortable with the risks managed. Mitigation strategies are working and we foresee no new risks.
04 Reviewed Project Acceptance Presentation performance in preparation for Mid-Term Presentation
  • Need to sharpen introductory pitch
  • Need to smoothen demo
  • Reflect on risk management and learning outcomes




[ Sep-27 ] : Functional Testing with IRRI (at NUS)

Agenda

  • Share project progress and ideas
  • Demonstrate and discuss current and planned functionality
  • Seek preliminary feedback on functional requirements and usability


Learning Points

# Item Details
01 NMS utilizes a Globe Telecom toll free number Current NMS system in Phillipines uses a toll free number supported by the telco Globe Telecom for its call-in IVR system
02 Information on Cereal Knowledge Bank not suitable for mobile As the information on CKB is too lengthy, it is not suitable for access on mobile phones. We need to find a way to streamline information to be more concise for mobile users
03 Public contribution might not be useful Information contributed from the public might not be as credible and professional, so it might not be as useful to the farmers who will be accessing the system. Tara suggested removing the portion of public contribution
04 User restriction on data analytics Data analytics page should be restricted to use by researchers and extension workers only, it is not of general use to the public.
05 Possible NMS extension to compliment micro financing One of the possible future implementations of the NMS system is the addition for mobile banking functions to bring micro financing to users using the NMS system. This will compliment the fertilizer recommendation and sale through the NMS system




[ Sep-29 ] : Mid-Term Presentation

Agenda

  • Show-case what we have done so far
  • Architectural Changes
  • Progress update on our exchanges with IRRI
  • Validation
  • What we plan to do


Learning Points

# Item Details
01 Demo was good but lacked real data Dummy data were used for the demo, real world data could have been used from IRRI's knowledge database to populate our CMS and IVR
02 Schedule shows a lot of buffer There is a huge chunk of buffer in the month of october which could have been filled
03 Analytic functions are too basic Only bar charts and simple charting functions available, insufficient depth in the data analytic department.
04 No real UAT done UAT needs to be done by users unassisted on their own or it will be more like a demo to the user instead of a user acceptance test.