Difference between revisions of "IS480 Team wiki: 2011T1 TheTalkies Midterm"

From IS480
Jump to navigation Jump to search
Line 1: Line 1:
==Project Progress Summary==
==Project Progress Summary==

Revision as of 15:01, 23 September 2011

Project Progress Summary

  • Between acceptance presentation(10 Aug 2011) and midterm presentation(26 Aug 2011), there were 3 iterations completed.
  • During iteration 3, our team has completed trend page in which users can see top 5 trends in SMU area. We also had completed School of Economics/School of Social Science (SESS) model.
  • During iteration 4, we have completed LostnFound page which is a kind of trending page. In this case, user can report what he has found and search what lost in school from our application, by using location key tags such as #SISL1, #SESSL2, #LIBRARYL3, etc. We also completed Library model.
  • During iteration 5, we had completed Tweet/Discuss and report function, in which both twitter user and non-twitter user can discuss, and report in Trend page and LostnFound page. In the mean time, we had completed School of Business (SOA) model.
  • We finished all the features planned for these 3 iteration at the end of iteration 5, even though, during iterations, we faced some delays and we had been behind schedule for up to a week, the cause of which will be mentioned details in Project Highlights.
  • For the time being, we are in the middle of 6th iteration. With iteration 5 finished, we have completed most of our main features, and in following iterations, we will be implementing back-end features such as statistics collection and fine-tuning of the app to increase the performance and user-friendliness of application. We are confident that our planned features for post mid-term presentation, can be done in time if all team members are putting the same efforts as they are doing right now.

Project Highlights:

Unexpected things happened along the way -

  • Germanium API was updated from 1.3 to 1.5 and our client wants us to use more updated version of API i.e. 1.5.
  • Some delay in schedule and team has put more efforts in order to catch up the schedule. The reason for that delay was mainly because almost all our team members involved in an cultural show event of one of our CCAs which was in first 3 weeks of school term. Although we anticipated some part of tight schedules beforehand, team members were busier and had to commit more effort in organizing the event than expected which led to decrease in individual as well as team efficiency. We had been behind the planned schedule for up to one week (7 days) in iteration 3. In subsequent iteration, we tried to catch up the planned schedule but the delay gap was too wide that we could not manage to be back on schedule as planned. However, we managed to narrow down the gap and the delay was reduced to 5 days which was recorded as further delay in iteration 4. Major catching up happened in iteration 5 when the event was over and the timetables for other classes were not as occupied. We maintained the momentum and the determination to complete the features in time as planned in this iteration. The better commitment from every team member allowed us to finish all the planned features for iteration 5 as well as those leftover tasks from previous iterations. Finally, after iteration 5, our team was back on track as planned in term of time.

Project Management

Provide more details about the status, schedule and the scope of the project. Describe the complexity of the project.

Project Status:

Highlight changes to modules, the completion status (implemented, UAT done, client approved, deployed, etc), the confidence level (0-1 where 0 is no confident of getting it done, 1 is 100% confident in getting it done) and comments (who has been assigned to do it, new scope, removed scoped, etc). Please use a table format to summarize with links to function details.

Task/function/features, etc Status Confident Level (0-1) Comment
Customer CRUD Fully deployed and tested 100% 1 Fiona
Trend Analytic 25% 0.9 Ben is researching analytic algoritms

Project Schedule (Plan Vs Actual):

The following is a comparison of the project plan during acceptance with the actual work done at this point. Everything went as plan until now, but for future iteration, according to some limitations such as performance aspect of our application, we will plan for improving performance and User-interface in coming iteration.

Has the project scope expanded or reduced? Until now, we implemented features according to plan and in iteration 6, we would be implementing Logging and Statistic function and building School Of Accountancy (SOA) model as plan. In iteration 7, we will implement UI revamp and Friend Stream function in following iteration. <Thandar>

Iterations Planned Actual Comments
3 (11 Aug - 24 Aug 2011) Modelling SESS 11 Aug - 19 Aug 2011 11 Aug - 31 Aug 2011 Aung and Soe Thet are busy and pushed iteration 3 back.
Database 11 Aug - 19 Aug 2011 11 Aug - 19 Aug 2011 Thandar and Khaing come out with database structure and create database.
Server side (Trend Page) 11 Aug - 24 Aug 2011 11 Aug - 10 Sep 2011 Phyo and Thandar faced unexpected difficulties such as learning cron job, changing database structure to update trend keywords.
Client Side (Trend Page) 20 Aug - 24 Aug 2011 11 Aug - 31 Aug 2011 Soe Thet and Khaing need to wait for server side since there is delay in server side.
Germanium (Trend Page) 11 Aug - 24 Aug 2011 11 Aug - 10 Sep 2011 Moe Hein and Aung implement codes to connect the 3D model and the trend page accordingly.
Mock Up 11 Aug - 24 Aug 2011 11 Aug - 24 Aug 2011 Moe Hein and Aung create full mock up pages for wireframing as Sponsor requested.
Test Plan 11 Aug - 17 Aug 2011 11 Aug - 17 Aug 2011 Khaing and Aung create test plan for unit testing.
Misc 11 Aug - 24 Aug 2011 11 Aug - 24 Aug 2011 Khaing and Aung improve wiki based on the Acceptance Presentation Feedback.
4 (25 Aug - 6 Sep 2011) Leftover from iteration #3 25 Aug - 3 Sep 2011 25 Aug - 12 Sep 2011 Project Manager Soe Thet and the whole team were busy with Myanmar Festival Gala on 3rd September and so we delayed further
Server Side (Trend Page) 4 Sep - 6 Sep 2011 4 Sep - 10 Sep 2011 Phyo and Soe Thet finalize server side coding, test cron job and results
Client side (Lost and Found)
  • Filter by time and school
4 Sep - 6 Sep 2011 4 Sep - 11 Sep 2011 Aung and Soe Thet implement time filter in Lost and Found page based on Trend feature
3D Model of Library 4 Sep - 6 Sep 2011 4 Sep - 12 Sep 2011 Khaing and Aung was responsible to draw Library Model
  • Port to API 1.5 from 1.3
  • BBL Object
  • Accordion Effect
4 Sep - 6 Sep 2011 4 Sep - 12 Sep 2011 Because of Germanium API changes, Moe Hein and Thandar adjust current codes as well as implement Accordion Effect in BBL Tree Object.
5 (7 Sep - 20 Sep 2011) Leftover from iteration #4 7 Sep - 12 Sep 2011 & Sep - 12 Sep 2011 Project Manager Soe Thet and the whole team were able to finish implementing features from previous iteration and Testing.
Tweet/ Report/ Discuss 13 Sep - 20 Sep 2011 13 Sep - 20 Sep 2011 Aung and Phyo has finished tweet/report and discussion feature in Trend Page and LostnFound Page.
SOB 3D Model 13 Sep - 20 Sep 2011 13 Sep - 20 Sep 2011 Khaing was responsible to build School Of Business (SOB) model
Germanium (Level, Placemark Position) 13 Sep - 20 Sep 2011 13 Sep - 20 Sep 2011 Thandar set placemark position on Campus Ground amd Level according to position #(hash tag).
UI Improvement 13 Sep - 20 Sep 2011 13 Sep - 20 Sep 2011 Moe Hein was responsible for User interface improvement and design changes for UAT1 and Mid-term presentation.

Project Metrics:

Summary of analysis for the metrics collected. You may refer to another page for the details about the metrics and how it is collected.

Project Risks:

Update the proposal assumptions and risks. Describe what you learn from the risk update and mitigation steps taken.

Risk Probability Impact Mitigation
Sponsor want to use Joomla instead of Drupal High High Team evaluating Joomla to write an impact analysis report
Sponsor deployment machine approval and support High Medium (now it is low) Use UPL machine

Be sure to prioritize the risks.

Technical Complexity:

Describe and list the technical complexity of your project in order of highest complexity first. For example, deploying on iPhone using Objective-C, customizing Drupal with own database, quick search for shortest flight path, database structure, etc.

Quality of product

Provide more details about the quality of your work. For example, you designed a flexible configurable system using XML.config files, uses Strategy Design Pattern to allow plugging in different strategy, implement a regular expression parser to map a flexible formula editor, etc.

Intermediate Deliverables:

There should be some evidence of work in progress.

Stage Specification Modules
Project Management Minutes Sponsor weeks -10 -5 3 7 Supervisor weeks -2 3 5 7
Metrics Bug metrics
Requirements Story cards CRUD Customer, Trend Analytic
Analysis Use case overall
System Sequence Diagram client, server
Business Process Diagram Here
Screen Shots CRUD Customer, Trend Analysis
Design ER Diagram 1, 2, 3
Class Diagram 1, 2, 3
Testing UAT test plan instructions

Not all parts of the deliverables are necessary but the evidence should be convincing of the progress. Try to include design deliverables that shows the quality of your project.


In an iterative approach, ready to use system should be available (deployed) for client and instructions to access the system described here (user name). If necessary, provide a deployment diagram link.


Describe the testing done on your system. For example, the number of UAT, tester profile, test cases, survey results, issue tracker, bug reports, etc.


In this section, describe what have the team learn? Be brief. Sometimes, the client writes a report to feedback on the system; this sponsor report can be included or linked from here.

Team Reflection:

Any training and lesson learn? What are the take-away so far? It would be very convincing if the knowledge is share at the wiki knowledge base and linked here.

Benjamin Gan Reflection:

You may include individual reflection if that make sense at this point. The team is uncooperative and did not follow my instructions.