|
|
Line 325: |
Line 325: |
| |style="text-align: left;"| | | |style="text-align: left;"| |
| *[[IS480_Team_wiki:_2012T1_Timber_Werkz_TechDiagrams#Deployment_Diagram|version 0.4]] | | *[[IS480_Team_wiki:_2012T1_Timber_Werkz_TechDiagrams#Deployment_Diagram|version 0.4]] |
− |
| |
− |
| |
| |} | | |} |
| <div style = "text-align:right; padding: 0px 30px 0px 45px;">[[IS480_Team_wiki:_2012T1_Timber_Werkz_Final_Wiki#Top|Back to Top]]</div> | | <div style = "text-align:right; padding: 0px 30px 0px 45px;">[[IS480_Team_wiki:_2012T1_Timber_Werkz_Final_Wiki#Top|Back to Top]]</div> |
Revision as of 19:41, 28 November 2012
<< MAIN WIKI
<< MID-TERM WIKI
Project Progress Summary
View our one minute pitch HERE
- Timberwerkz has completed 13 sprints in total and is now finishing its final milestone.
- This is where we are on the timeline:
|
Project Highlights
Event (#)
|
Highlights / Issue Description
|
Sprint 10
|
Audition Scheduling: Hungarian Algorithm changed to First-Come First-Served Algorithm
Client requested to change the current audition scheduling algorithm from Hungarian Algorithm to FCFS algorithm to better suit the auditioning process flow of the company.
Team accepted the change request and put in extra hours to fulfill the change requirement.
|
Sprint 11
|
Business Development Executive (Point-of-Contact from Client) left her position
The Business Development Executive, who is the POC from our client has left the company. We had to work with another Executive Assistant during the interim period for about 1 week. Subsequently on November 9, we had to update the new Business Development Executive about the system and to manage new change requests.
Refer to Client Meeting 10 for our first meeting with the new Business Development Executive.
|
Project Challenges
Event (#)
|
Challenges
|
Developing the Audition Assignment Algorithm
|
- Developing the Audition Assignment Algorithm required thorough research and self-study of the Hungarian Algorithm
- Team also had consultations with Professor Hady Wirawan Lauw from the School of Information Systems, SMU
- Considered as a technical complexity
- However, a change request required us to change this algorithm to a First-Come First Served one to better suit the client's business requirements
|
Usability Test 2
|
- Faced difficulties in getting a real Casting Call for a field test because it does not coincide with our UT2 schedule.
- Managed to conduct a UT2 Lab Test instead on 25 October 2012
|
Project Achievements
1. Usability Testing Methodology
- Methodology was beneficial in providing a high visibility and clear approach in managing improvements from participants' feedback
- Invited by Professor Benjamin Gan to his IS306 Interaction Design Prototyping class to share lessons learnt and improvements that can be made.
Presentation Slides
2. Change Request Management Process
- Process was beneficial in prioritising and managing change requests from the client
- It also helps us to keep within the project schedule by focusing on the 'important or necessary' requests
|
Project Management
Schedule (Planned VS Actual)
Brief Summary
Since the Mid Terms, everything went as planned, except for the following changes to the project schedule:
Change #1: Minor changes to the dates to reflect the actual date of User Testing 2 and Final Presentation
Change #2: Addition of a new Field Test session. Oak3 Films is using our application in one of its Casting Call auditions
High resolution timeline link
|
Metrics
Schedule Metric
The diagrams below show the burn-down & schedule ratio charts of Sprints 9 - 13 since MidTerms.
- Burn-down Charts
-
- Schedule Ratio Charts
-
Key Issues
1. Sprint 10:
- Delay in the last 3 days of Sprint 10.
- Team needs to settle the following important change requests:
- 1. Change Hungarian algorithm-based audition scheduling to first-come-first-served basis
- 2. Export audition schedule to CSV file
- 3. Submit required video with YouYube URL
- 4. Include time interval of 15 minutes for scheduling
Links
1. Schedule Metric Calculation
2. Schedule Metric Documentations
|
Bug Metric
- Number of Bugs Discovered Chart and Bug Severity Chart
-
Technical Complexity
Technical complexity listed in order of highest complexity:
Complexity
|
Description
|
1. Multifunctional Calendar
|
- Simplify the complex process of scheduling auditions using commonly recognized calendar interface
- Casting Manager can create an audition schedule by clicking and dragging slots
- Artistes can select slots that are available
- Implementing drag and drop efficiently in the calendar
- Assign elements to be “draggable”
- Auditionee slots that exist on the calendar
- Auditionees that has not selected a slot
- Assign elements to be “droppable”
|
2. Photo Upload Plugin
(Similar from Mid Term)
|
- A Production House or an Artiste can set a profile picture to best represent himself/herself when the portfolio is edited
- Process considerations & implementation such as:
- Select Photo (using HTML5 Canvas API)
- Cropping (JavaScript API, ebserver crops photo)
- Uploading Photos to Amazon S3 Bucket
- Cross browser support and Cropping aspect ratio
|
3. Video Upload Plugin
(Maroon text reflects addition from Mid Term)
|
- An artiste is required to upload a YouTube Video attachment when s/he is applying for a role in a Casting Call
- Get Access Token: Youtube Developer API
- Request for one-time access token
- Convert one-time access token to persistent session token
- Upload new video from file
- Set video metadata. E.g. Title, Description -> upload URL
- Use existing YouTube video via URL
- Locate thumbnail preview and display title
|
Quality of Product
Project Deliverables
Stage
|
Specification
|
Modules
|
Project Management
|
Minutes (Brown colour code for minutes after Mid-Terms)
|
|
Metrics
|
|
Requirements
|
Product Backlog
|
|
Change Requests Log
|
|
UI Mockups & Videos
|
|
Analysis
|
Use Case
|
|
Design
|
Deployment Diagram
|
|
Logical Diagram
|
|
Testing
|
Usability Test 1
|
|
Usability Test 2
|
|
Handover
|
Manuals
|
*User Manual
|
Code
|
|
Deployment Diagram
|
|
Quality
Deployment
Casting3 has 3 separate deployed environments. These are development, staging and production environment.
The responsibilities for each of these environment are for code integration, product testing, and public release respectively.
Usability Test 2
Objectives
1. Determine that the usage of the features in the application are consistent to the expectations of real users (Casting Managers & Artistes)
2. Obtain feedback from users such as to improve the usability (learnability, efficiency, errors, satisfaction) and aesthetics of our application
|
Lab Test Details & Outcome
Usability Test 2: Real users (Artistes) participating in the test at Oak3 Films
UT2 Lab Test was successfully conducted on 25 October 2012, 2–6pm at Oak3 Films.
These are the following participants:
- 1 Casting Manager
- 5 Artistes
- Detailed Breakdown of Participants Involved
Feedback Links:
- 1. Casting Manager Feedback
- 2. Artistes Feedback
- 3. Response Plan to Artiste Feedback
- 4. Quantitative Feedback
Extract of Solutions to Most Common Feedback:
|
Field Test
Objectives
1. Determine if users are capable of handling the application on their own (without any guidance from us) in the actual environment where they would be using the application
2. Obtain feedback from users such as to improve the usability (learnability, efficiency, errors, satisfaction) and aesthetics of our application
|
Field Test Details & Outcome
Field Test was conducted from 28 November 2012 to 1 December 2012 remotely at the artistes' own comfort. With the help and support of Oak3, we managed to get some artistes to sign up as a user of Casting3, and to apply for an ongoing casting call, "Koffee did it". They will be provided with a link to an evaluation form, where they will asked to give us their feedback.
As of the submission date of this wiki page (28 Nov), the field test is ongoing and results have yet to be collated. The results will be later concluded in the following links:
Feedback Links:
- 1. Profile of artistes who have signed up
- 2. Survey for Artistes and their feedback
- 3. Response Plan to Artiste Feedback
Reflections
Team Reflection
What we could have done better... in future!
-
-
- The "Remaining Effort" Line in the Burn Down Chart can be tweaked to form a curve based on the past trends of Burn Down Charts as shown:
- Our team's Burn Down Charts typically start with a huge gap at the beginning since we included buffer time in each sprint for change requests and other unforeseen circumstances. Hence, by comparing remaining efforts required to the remaining time available in the form of a curve, it allows us to detect any schedule delay early.
- Refer to the current burn down chart here.
- Bug Resolution Effort Metric
- It will also be good to track the amount of time we took to resolve a bug
- This will provide us with greater visibility, instead of the current way which is to calculate manually from a Sprint Documentation
- Change Request Management
- Gather statistics & display them graphically using the following data:
- No. of Change Requests Raised
- No. of Requests Implemented
- No. of Requests Placed On Hold/Not Implemented
- This will allow our team to monitor change requests more effectively
- It can also be used as a tool for the client to be kept informed and updated
|
Individual Reflection
Casting3 will enhance talent management processes in the entertainment industry. Creating a new community on this interactive networking platform, potential actors/actresses can upload auditions virtually to secure a role while casting managers can source from a larger pool of talent more efficiently.
The team at Timber Werkz has helped to create a platform suited to the industry’s needs. Self-motivated and enthusiastic, they have often advised on feasibility of technical requests and provided innovative solutions during the development of this project.
- ~ Oak3 Films
- 28 November 2012
|
|