IS480 Team wiki: 2012T1 Timber Werkz MidTerm Wiki
MID-TERM WIKI |
Project Progress Summary
Overview
As at 3 October, Timberwerkz has completed Sprint 8 and will be reaching Miletone 4 (6 in total) on 5 October 2012.
Timberwerkz is confident of completing the project within the stipulated schedule shown below: |
Project Highlights
Event (#) | Highlights / Issue Description |
---|---|
Sprint 1 | Unexpected delays in schedule in the last 6 days of Sprint 1 During the first sprint, we realised that we did not schedule sufficient buffer time for change requests from the client. Towards the last week of the sprint, we have several change requests for the View Artiste Portfolio and Edit Artiste General Information stories that resulted in a delay of schedule. Since then, we made sure that there is 25-35% of buffer time scheduled for each sprint duration to handle change requests, bug fixing etc. |
Sprint 2 | Request from Client to adopt Joomla over Yii Framework During Sprint 2, the client had suddenly raised a change request to switch from using Yii Framework to Joomla CMS as it will provide them with a non-technical interface to edit pages of the web application. However, after a thorough analysis of the two technologies, we came to the conclusion that Joomla CMS is better catered to the development of websites, which have limited user interactivity - such as blogs, new feeds and product catalogues. Secondly, while additional features can be introduced to the CMS by installing from Joomla’s suite of extensions, the implementation of these extensions will still need to be customized so as to suit the requirements of the clients, and will still ultimately take up time. Most importantly, as Oak3’s business process of managing auditions is very complex, the automation of this process using Joomla CMS will prove to be a challenge. Hence, after discussing these concerns with Oak3, we have decided to remain on using the Yii Framework, which will allow us to implement features according to their requirements, as we are essentially masters of our own code.
|
Sprint 7 | Discovered the need for a new User Management story under Manage Account Chapter The purpose of the User Management system is to improve accountability and communication between a Casting Manager and an applicant. Suppose a scenario: there is an Artiste X who was invited by a first Casting Manager A and both parties have made some correspondence. If Artiste X would like to communicate with Casting Manager A in private, this message can be viewed by more than one users of the same Production House account and this may lead to potential miscommunication. Thus, we decided to introduce a feature where a main Casting Manager serves as an administrator to add/remove a user account within the production house account. |
Project Management
Project Status
Scope (Planned Vs Mid Term)
2. Version 2 Scope
2. Latest Scope (Version 3)
Schedule (Planned Vs Mid Term)
Project MetricsSchedule MetricThe diagram below shows the burn-down charts of the 8 sprints we have completed thus far.
2. Sprint 3:
Bug Metric
Risk ManagementAs at mid-term, we have added two entries as shown under the Project Management and Technological Implementation headings in the Risk Management Table.
Technical ComplexityTechnical complexity listed in order of highest complexity:
|
Quality of Product
Intermediate Deliverables
Stage | Specification | Modules |
---|---|---|
Project Management | Minutes | |
Metrics | ||
Requirements | Product Backlog | |
Change Requests Log | ||
UI Mockups & Videos | ||
Analysis | Use Case | |
Design | Deployment Diagram | |
Logical Diagram | ||
Testing | User Test Plan |
Deployment
- Staging & Development Environment: deployed on Amazon EC2 Micro Instance
- Database: Amazon RDS Instance
- Web Services: Amazon Simple Email Service & Amazon Storage Web Services
- Web Links:
Usability Test 1
Objectives
Scope of Test
Session 1 (Casting Mgrs)
Session 2 (Artistes)Session 2 was conducted from 9 - 14 Sept 2012
View our testing methodology and supporting documents.
|