HeaderSIS.jpg

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

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




[ Aug-01 ] : Progress Update / Risk Assessment

Agenda

  • Discuss progress on prototype
  • Discuss technical challenges and constraints
  • Review client engagement
  • Review project risks
  • Prepare for Project Acceptance Presentation


Decisions

# Item Details
01 Prototypes are on-track and functional Able to show a full system flow (all dynamic)
02 Risk review
  • Risk #1: Modular architecture to mitigate risk from integration of complex technologies. Team is comfortable with the architectural design.
  • Risk #2: Through reading and interacting with industry players, team has gained considerable maturity in understanding the industry's current and future constraints.
03 Risk #4: Over-reliance on Microsoft technologies Response: Modular architecture to allow for future component changes. For now, Microsoft technologies used to allow for rapid prototyping and facilitate overall system flow.
04 Risk #5: Reliability of Skype API in school network Response: Affects demo plans. To switch to 3G network tethering if possible.


Tasks

# Item Details In-Charge Deadline Status
01 Update project schedule Alvin and Edwin 5 Aug 2010 Completed
02 Update presentation of features Wei Han 5 Aug 2010 Completed
03 Update use cases Marcus 5 Aug 2010 Completed
04 Plan for demo during Project Acceptance Presentation Lucas 5 Aug 2010 Completed
05 Update learning outcomes Fengnan 5 Aug 2010 Completed




[ Aug-10 ] : Project Acceptance Presentation

Agenda

  • Discuss project aims, direction, schedule, risks and learning outcomes


Learning Points

# Item Details
01 Storyboarding was good, but we did not manage to execute well due to technical difficulties Plan for technical contingencies in the future
02 Value proposition was not clear enough Need to focus project selling points and value to client
03 Risk #6: Large project scope - dealing with very large system components Response: Reassess project scope and system components. Assess possibility of integrating open-source projects to reduce developmental effort.


Tasks

# Item Details In-Charge Deadline Status
01 Evaluate system components and alternatives Reassess developmental effort and necessity, as well as open-source alternatives All 15 Aug 2010 Completed




[ Aug-15 ] : Progress Update / Risk Assessment

Agenda

  • Reassess project aims, direction, schedule and risks
  • Prepare for next developmental phase


Decisions

# Item Details
01 Risk #5 became a liability during presentation Switch over to external network during presentation
02 Opportunities for more efficient technical architecture
  • Component redesign/simplification and introduction of open-source projects (e.g. WordPress and jqPlot)
  • Mitigate Risks #4 and #6 at the same time


Tasks

# Item Details In-Charge Deadline Status
01 Investigate and prototype new system architecture Changes to components and inter-component communications All 21 Aug 2010 Completed




[ Aug-22 ] : Redesign of System Architecture

Agenda

  • Streamline system architecture to reduce development and system resource requirements
  • Model new data structures to support the system architecture


  • Architectural changes are detailed over at


Tasks

# Item Details In-Charge Deadline Status
01 Update various components based on new architecture All 29 Aug 2010 Completed




[ Aug-24 ] : Meeting with new Project Supervisor, Prof Chris Boesch

Agenda

  • Sharing project plans, direction and aims
  • Getting feedback on real-world deployment issues and concerns on sponsor engagement


Learning Points

# Item Details
01 Building the system is half the battle Need to build and grow a community around it
02 Our model of hybrid collaboration with sponsor (IRRI) is acceptable Complete deliverables well and extend offerings with proof-of-concept


Tasks

# Item Details In-Charge Deadline Status
01 Investigate and plan community building opportunities Set aside time to test and deploy system with an extend research community Lucas 29 Aug 2010 Completed




[ Aug-29 ] : Progress Update / Risk Assessment

Agenda

  • Assess project schedule and risks


Decisions

# Item Details
01 Project phases going according to plan, team is comfortable with the pace. Technical complexities are manageable and new system architecture works.
02 Team is comfortable with the risks managed. Mitigation strategies are working.


Tasks

# Item Details In-Charge Deadline Status
01 Prepare for deployment to team server All project components and services to be hosted there All 05 Sep 2010 Completed




[ Aug-30 ] : Teleconference with IRRI

Agenda

  • Discuss available resources and interest


Highlights

# Item Details
01 IRRI remains interested in the system concept, but is tied up with system deployment at the moment and unable to provide close technical collaboration. Team to proceed with planned functionality for IRRI's short-term and long-term needs.
02 IRRI remains interested in the analytics functionality, but is unable to provide live access to data due to security concerns. Analytics design is flexible enough to be independent of data source. Low impact on developmental effort.