Difference between revisions of "IS480 Team wiki: 2012T1 Timber Werkz MidTerm Wiki"
(Undo revision 119906 by Joseph.choo.2010 (Talk)) |
|||
(42 intermediate revisions by 2 users not shown) | |||
Line 3: | Line 3: | ||
<big><big><big><big><font color="#4D268F" face="">'''MID-TERM WIKI'''</font></big></big></big></big> | <big><big><big><big><font color="#4D268F" face="">'''MID-TERM WIKI'''</font></big></big></big></big> | ||
|} | |} | ||
− | [[IS480_Team_wiki:_2012T1_Timber_Werkz|<font color="# | + | <big>[[IS480_Team_wiki:_2012T1_Timber_Werkz|<font color="#000000" face=""><ins>'''<< MAIN WIKI'''</ins></font>]]</big> <big>[[IS480_Team_wiki:_2012T1_Timber_Werkz_Final_Wiki|<font color="#D00303" face=""><ins>'''<< FINAL WIKI'''</ins></font>]]</big> |
+ | |||
<br> | <br> | ||
[[Image:Twa6.png|500px|right]] | [[Image:Twa6.png|500px|right]] | ||
Line 9: | Line 10: | ||
==<font color="#c93756">'''Project Progress Summary'''</font>== | ==<font color="#c93756">'''Project Progress Summary'''</font>== | ||
===<font color="#4D268F">Overview</font>=== | ===<font color="#4D268F">Overview</font>=== | ||
+ | |||
+ | <big>[https://docs.google.com/file/d/0BwXGnbL-305eWFhPNlJvUHRiQVE/edit Presentation Slides]</big> | ||
{| cellpadding="9" style="border: 1px solid darkgray; text-align: center; height:50px" | {| cellpadding="9" style="border: 1px solid darkgray; text-align: center; height:50px" | ||
|scope="row" width="1000" style="text-align: left; background: #FFF8C6"| | |scope="row" width="1000" style="text-align: left; background: #FFF8C6"| | ||
− | Timberwerkz | + | Timberwerkz has completed Sprint 8 on 3 October and Miletone 4 (6 in total) on 5 October 2012.<br> |
− | There are several key accomplishments since | + | There are several key accomplishments since the project inception on 7 May 2012: |
*Development using php Yii framework with little prior knowledge | *Development using php Yii framework with little prior knowledge | ||
*Completed our first Usability Test and currently implementing solutions to given feedback | *Completed our first Usability Test and currently implementing solutions to given feedback | ||
Line 53: | Line 56: | ||
|} | |} | ||
+ | |||
+ | |||
+ | <div style = "text-align:right; padding: 0px 30px 0px 45px;">[[IS480_Team_wiki:_2012T1_Timber_Werkz_MidTerm_Wiki#Top|Back to Top]]</div> | ||
+ | |||
+ | ===<font color="#4D268F">Technical Complexity</font>=== | ||
+ | |||
+ | Technical complexity listed in order of highest complexity:<br> | ||
+ | |||
+ | {| class="wikitable" style="text-align: center; height:200px" | ||
+ | |+ | ||
+ | |- | ||
+ | ! scope="col" width="100" style="background-color:#4D268F"| <font color="#ffffff">Complexity</font> | ||
+ | ! scope="col" width="700" style="background-color:#4D268F"| <font color="#ffffff">Description</font> | ||
+ | |- | ||
+ | |||
+ | ! scope="row" style="background-color:#FBF8C7"|1. Audition Assignment Algorithm (Scheduling Auditions) | ||
+ | |style="text-align: left;"| | ||
+ | *'''What the feature is''' | ||
+ | :*The decision by the system to allocate the best possible slot for an interviewee based on his/her top 3 preferences | ||
+ | *'''What was complex''' | ||
+ | :*Implementing an Audition Assignment Algorithm (based on Hungarian Algorithm) to allocate audition slots to be based on interviewees’ top 3 preferences | ||
+ | :*The Hungarian Algorithm is chosen because it can help us optimally assign these slots to the top 3 preferences of all interviewees | ||
+ | :*This is done by drawing up a Interviewee-Slot Matrix. The matrix consists of interviewees' priority numbers (ranges from 0 to 2, where 0 has the highest priority and 2 has the lowest priority) | ||
+ | :*The program will then allocate each interviewee a slot, such that the sum of the allocation will be the smallest | ||
+ | :*Refer to this '''[https://docs.google.com/file/d/0BwXGnbL-305ebGZKREpxRG8xaHc/edit document]''' for complete details | ||
+ | |||
+ | |- | ||
+ | |||
+ | ! scope="row" style="background-color:#FBF8C7"|2. Photo Upload Plugin | ||
+ | |style="text-align: left;"| | ||
+ | *'''What the feature is''' | ||
+ | :*A Production House or an Artiste can set a profile picture to best represent himself/herself when the portfolio is edited | ||
+ | *'''What was complex''' | ||
+ | :*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 | ||
+ | |- | ||
+ | |||
+ | ! scope="row" style="background-color:#FBF8C7"|3. Search Feature | ||
+ | |style="text-align: left;"| | ||
+ | *'''What the feature is''' | ||
+ | :*A Casting Manager can search for Artistes or have Artiste suggested to him/her by the system in the search page | ||
+ | :*An Artiste can search for a Casting Call or have one which is suggested by the system in the search page | ||
+ | *'''What was complex''' | ||
+ | ::*Embedding of search query to URL, so that the URL link can be copied to other users | ||
+ | ::*Search results are generated simultaneously as user is typing a search entry; and the frequency of querying the server will also be controlled to once every 1.5 seconds so as to reduce overheads on server. | ||
+ | |- | ||
+ | |||
+ | ! scope="row" style="background-color:#FBF8C7"|4. Uploading YouTube Video | ||
+ | |style="text-align: left;"| | ||
+ | *'''What the feature is''' | ||
+ | :*An artiste is required to upload a YouTube Video attachment when s/he is applying for a role in a Casting Call | ||
+ | *'''What was complex''' | ||
+ | :*Challenging process of making use of the YouTube API to retrieve an access token that will give permission to upload videos from external sites | ||
+ | |- | ||
+ | |||
+ | |} | ||
+ | |||
Line 71: | Line 134: | ||
! scope="row" style="background-color:#FBF8C7"|Manage Portfolio | ! scope="row" style="background-color:#FBF8C7"|Manage Portfolio | ||
− | |style="text-align: center;"|100% | + | |style="text-align: center;"|100% developed and deployed |
|style="text-align: center;"|1 | |style="text-align: center;"|1 | ||
|style="text-align: center;"|Genevieve | |style="text-align: center;"|Genevieve | ||
Line 83: | Line 146: | ||
! scope="row" style="background-color:#FBF8C7"|Manage Search | ! scope="row" style="background-color:#FBF8C7"|Manage Search | ||
− | |style="text-align: center;"| | + | |style="text-align: center;"|90% developed |
|style="text-align: center;"|1 | |style="text-align: center;"|1 | ||
|style="text-align: center;"|Nikita | |style="text-align: center;"|Nikita | ||
Line 89: | Line 152: | ||
! scope="row" style="background-color:#FBF8C7"|Manage Casting Calls | ! scope="row" style="background-color:#FBF8C7"|Manage Casting Calls | ||
− | |style="text-align: center;"| | + | |style="text-align: center;"|100% developed and deployed |
− | |style="text-align: center;"| | + | |style="text-align: center;"|1 |
|style="text-align: center;"|Wee Kiat & Regina | |style="text-align: center;"|Wee Kiat & Regina | ||
|- | |- | ||
! scope="row" style="background-color:#FBF8C7"|Manage Applications | ! scope="row" style="background-color:#FBF8C7"|Manage Applications | ||
− | |style="text-align: center;"| | + | |style="text-align: center;"|100% developed and deployed |
− | |style="text-align: center;"| | + | |style="text-align: center;"|1 |
|style="text-align: center;"|Jun Ru | |style="text-align: center;"|Jun Ru | ||
|- | |- | ||
Line 172: | Line 235: | ||
<br> | <br> | ||
+ | <big><big>'''Burn-down Charts'''</big></big><br><br> | ||
[[Image:Schedule_1.png|525px]][[Image:Schedule_2v2.png|525px]] | [[Image:Schedule_1.png|525px]][[Image:Schedule_2v2.png|525px]] | ||
<br><br> | <br><br> | ||
+ | |||
+ | <big><big>'''Schedule Ratio Charts'''</big></big><br><br> | ||
+ | [[Image:ScheduleRatioChart1.png|525px]][[Image:ScheduleRatioChart2.png|525px]] | ||
+ | <br><br> | ||
+ | <div style = "text-align:right; padding: 0px 30px 0px 45px;">[[IS480_Team_wiki:_2012T1_Timber_Werkz_MidTerm_Wiki#Top|Back to Top]]</div> | ||
====Bug Metric==== | ====Bug Metric==== | ||
− | [[Image: | + | [[Image:TW_Number_of_bugs.png|500px|left]] |
+ | [[Image:TW_BugSeverity.png|500px|left]] | ||
+ | <br><br><br><br> | ||
+ | {| class="wikitable" style="text-align: center; height:50px" | ||
+ | |+ | ||
+ | |- | ||
+ | ! scope="row" width="600" style="text-align: center; background: #FFF8C6"|'''Number of Bugs Found'''<br> | ||
+ | There was a pike in the number of bugs found in Sprint 5. This is due to the more rigorous testing conducted on our application in preparation for UT1 in Sprint 6. We began testing at least one week before the end of the sprint, as compared to a few days before for other sprints. | ||
+ | <br><br> | ||
+ | Also, there was one bug that is carried over from Sprint 6 to 7 because we did not have sufficient time to resolve it | ||
+ | |} | ||
+ | |||
+ | <br><br><br><br><br><br><br> | ||
{| class="wikitable" style="text-align: center; height:50px" | {| class="wikitable" style="text-align: center; height:50px" | ||
|+ | |+ | ||
Line 196: | Line 277: | ||
|style="text-align: left;"|Developers attempt to resolve bug immediately. Project Manager relieves member of his current task and set him in charge to resolve bug | |style="text-align: left;"|Developers attempt to resolve bug immediately. Project Manager relieves member of his current task and set him in charge to resolve bug | ||
|} | |} | ||
− | |||
{| class="wikitable" style="text-align: center; height:50px" | {| class="wikitable" style="text-align: center; height:50px" | ||
|+ | |+ | ||
|- | |- | ||
− | ! scope="row" width=" | + | ! scope="row" width="600" style="text-align: center; background: #FFF8C6"|'''Bug Metric Severity Chart'''<br> |
− | + | This Chart shows the corresponding severity score with the number of bugs found. Again, the impact was the highest in Sprint 5 because of UT1 preparation. | |
− | |||
|} | |} | ||
− | |||
{| class="wikitable" style="text-align: center; height:50px" | {| class="wikitable" style="text-align: center; height:50px" | ||
|+ | |+ | ||
Line 219: | Line 297: | ||
===<font color="#4D268F">Risk Management</font>=== | ===<font color="#4D268F">Risk Management</font>=== | ||
− | + | Prioritised Risks as at mid-term. Full entries as shown under the Project Management and Technological Implementation headings in the '''[[IS480_Team_wiki:_2012T1_Timber_Werkz_Risks| Risk Management Table]]'''. | |
{| class="wikitable" style="text-align: center; height:80px" | {| class="wikitable" style="text-align: center; height:80px" | ||
Line 234: | Line 312: | ||
!scope="row" style="background-color:#FAFDC3"| | !scope="row" style="background-color:#FAFDC3"| | ||
− | ''' | + | '''2''' |
|colspan="6" height:100px; style="background-color:#FAFDC3; text-align: left;"| | |colspan="6" height:100px; style="background-color:#FAFDC3; text-align: left;"| | ||
− | ''' | + | '''Client Management''' |
|- | |- | ||
! scope="row" | | ! scope="row" | | ||
− | '''1 | + | '''2.1''' |
|style="text-align: left;"| | |style="text-align: left;"| | ||
− | * | + | *Change requests expected from client as Casting3 application is built from scratch |
|style="text-align: left;"| | |style="text-align: left;"| | ||
− | * | + | *Scope and schedule of the project affected |
|style="text-align: center;"| | |style="text-align: center;"| | ||
− | + | High | |
|style="text-align: center;"| | |style="text-align: center;"| | ||
High | High | ||
|style="text-align: left;"| | |style="text-align: left;"| | ||
− | *A | + | *A Change Request Log is created to manage change requests more effectively |
|style="text-align: center; color:#D31601"| | |style="text-align: center; color:#D31601"| | ||
'''Mitigation strategy <br> in force''' | '''Mitigation strategy <br> in force''' | ||
|- | |- | ||
− | |||
− | |||
− | |||
− | |||
− | |||
! scope="row" | | ! scope="row" | | ||
− | ''' | + | '''2.2''' |
|style="text-align: left;"| | |style="text-align: left;"| | ||
− | * | + | *Clients do not know the exact requirements of the new application |
|style="text-align: left;"| | |style="text-align: left;"| | ||
− | * | + | *Application may not serve the needs of the company effectively |
|style="text-align: center;"| | |style="text-align: center;"| | ||
− | + | High | |
|style="text-align: center;"| | |style="text-align: center;"| | ||
Medium | Medium | ||
|style="text-align: left;"| | |style="text-align: left;"| | ||
− | * | + | *Using [http://bit.ly/prototype_1 Low fidelity prototype] (UI mockups) to communicate and ensure that requirements are properly understood. |
|style="text-align: center; color:#D31601"| | |style="text-align: center; color:#D31601"| | ||
'''Mitigation strategy <br> in force''' | '''Mitigation strategy <br> in force''' | ||
Line 279: | Line 352: | ||
<div style = "text-align:right; padding: 0px 30px 0px 45px;">[[IS480_Team_wiki:_2012T1_Timber_Werkz_MidTerm_Wiki#Top|Back to Top]]</div> | <div style = "text-align:right; padding: 0px 30px 0px 45px;">[[IS480_Team_wiki:_2012T1_Timber_Werkz_MidTerm_Wiki#Top|Back to Top]]</div> | ||
− | ===<font color="#4D268F"> | + | ===<font color="#4D268F">Change Request Management</font>=== |
− | + | *In every meeting with the client, change requests raised are logged into the change request log as shown below. | |
+ | *The red box shows an example entry. A decision of whether to implement the change is based on the priority of the request and time needed to develop the request. | ||
+ | *Priority is categorised as '''MUST, SHOULD, COULD or WON'T''' | ||
+ | *Time is categorised as '''VERY SHORT, SHORT, MEDIUM, LONG or VERY LONG''' | ||
+ | *<b> [https://docs.google.com/spreadsheet/ccc?key=0AuNjOu2GtpU7dFB0TmhtSkJSRzNPWlA4eE1FaWloMkE#gid=15 View Change Request Log]</b> | ||
+ | <br> | ||
+ | [[Image:TWChangeRequestLog.png|800px|center]] | ||
+ | <br style="clear:both" /> | ||
+ | [[Image:ChangeRequestDecision.png|600px|right]] | ||
− | {| class="wikitable" style="text-align: center; height: | + | <br><br><br><br><br><br> |
+ | {| class="wikitable" style="text-align: center; height:50px" | ||
|+ | |+ | ||
|- | |- | ||
− | ! scope=" | + | ! scope="row" width="600" style="text-align: left; background: #FFF8C6"| |
− | |||
− | |||
− | |||
− | + | *The following chart on the right shows our Change Management Decision Process (How we decide an implementation based on the priority and time)<br><br> | |
− | + | *'''Scenario #1:''' If a priority level is a MUST, then we will '''implement''' the request<br><br> | |
− | + | *'''Scenario #2:''' If a priority level is a SHOULD, then we will '''implement''' the request if the time to do so is '''VERY SHORT - MEDIUM'''<br><br> | |
− | + | *'''Scenario #3:''' If a priority level is a COULD, then we will '''implement''' the request if the time to do so is '''VERY SHORT'''<br><br> | |
− | + | *'''Scenario #4:''' If a priority level is a WON'T, then we will not '''implement''' the request<br><br> | |
− | + | |} | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | *''' | ||
− | |||
− | |||
− | |||
− | | | ||
− | |||
|} | |} | ||
− | + | <br style="clear:both" /> | |
− | |||
− | |||
<div style = "text-align:right; padding: 0px 30px 0px 45px;">[[IS480_Team_wiki:_2012T1_Timber_Werkz_MidTerm_Wiki#Top|Back to Top]]</div> | <div style = "text-align:right; padding: 0px 30px 0px 45px;">[[IS480_Team_wiki:_2012T1_Timber_Werkz_MidTerm_Wiki#Top|Back to Top]]</div> | ||
− | + | <br> | |
==<font color="#c93756">'''Quality of Product'''</font>== | ==<font color="#c93756">'''Quality of Product'''</font>== | ||
Line 392: | Line 433: | ||
|style="text-align: center;"|Deployment Diagram | |style="text-align: center;"|Deployment Diagram | ||
|style="text-align: left;"| | |style="text-align: left;"| | ||
− | *[[IS480_Team_wiki:_2012T1_Timber_Werkz_TechDiagrams#Deployment_Diagram|version 0. | + | *[[IS480_Team_wiki:_2012T1_Timber_Werkz_TechDiagrams#Deployment_Diagram|version 0.4]] |
*[[IS480_Team_wiki:_2012T1_Timber_Werkz_TechDiagrams#Versions|Earlier Versions]] | *[[IS480_Team_wiki:_2012T1_Timber_Werkz_TechDiagrams#Versions|Earlier Versions]] | ||
|- | |- | ||
Line 398: | Line 439: | ||
|style="text-align: center;"|Logical Diagram | |style="text-align: center;"|Logical Diagram | ||
|style="text-align: left;"| | |style="text-align: left;"| | ||
− | *[[IS480_Team_wiki:_2012T1_Timber_Werkz_TechDiagrams#Logical_Diagram|version 1. | + | *[[IS480_Team_wiki:_2012T1_Timber_Werkz_TechDiagrams#Logical_Diagram|version 1.2]] |
*[[IS480_Team_wiki:_2012T1_Timber_Werkz_TechDiagrams#Versions_2|Earlier Versions]] | *[[IS480_Team_wiki:_2012T1_Timber_Werkz_TechDiagrams#Versions_2|Earlier Versions]] | ||
|- | |- | ||
Line 422: | Line 463: | ||
:#'''[http://casting3.hopto.org Casting3 Staging Environment]''' | :#'''[http://casting3.hopto.org Casting3 Staging Environment]''' | ||
:#'''[http://dev-casting3.hopto.org/ Casting3 Development Environment]''' | :#'''[http://dev-casting3.hopto.org/ Casting3 Development Environment]''' | ||
− | :#'''[[IS480_Team_wiki:_2012T1_Timber_Werkz_TechDiagrams#Deployment_Diagram|Deployment diagram v0. | + | :#'''[[IS480_Team_wiki:_2012T1_Timber_Werkz_TechDiagrams#Deployment_Diagram|Deployment diagram v0.4]]''' |
<br> | <br> | ||
<br> | <br> | ||
Line 512: | Line 553: | ||
<br> | <br> | ||
Session 1 was successfully conducted on '''7 Sept 2012, 2 – 6pm at the office of Oak3 Films.'''<br> | Session 1 was successfully conducted on '''7 Sept 2012, 2 – 6pm at the office of Oak3 Films.'''<br> | ||
− | A total of 7 staff members from Oak3 Films assumed the role of a Casting Manager participated: | + | A total of '''7 staff members''' from Oak3 Films assumed the role of a Casting Manager participated: |
− | #Dennis (Head of Production) | + | '''#Dennis (Head of Production)''' |
− | # | + | #'''Jonathan (Producer)''' |
− | + | #'''Jeremy (Production Assistant)''' | |
− | #Jeremy (Production Assistant) | + | #'''PeiHua (Production Assistant)''' |
− | #PeiHua (Production Assistant) | ||
#Jazz (Graphics) | #Jazz (Graphics) | ||
#Dinesh (IT Executive) | #Dinesh (IT Executive) | ||
+ | #Ana (Secretary) | ||
<br><br> | <br><br> | ||
− | Feedback from Session 1 of the Usability Test is recorded in the [https://docs.google.com/spreadsheet/ccc?key= | + | Feedback from Session 1 of the Usability Test is recorded in the [https://docs.google.com/spreadsheet/ccc?key=0AskT4ENrBtHIdGhOVUFnTk1TQmFxVHpiOVdySWVQdnc#gid=0 User Feedback Document]<br> |
− | View also our [https://docs.google.com/spreadsheet/ccc?key= | + | View also our [https://docs.google.com/spreadsheet/ccc?key=0AskT4ENrBtHIdGhOVUFnTk1TQmFxVHpiOVdySWVQdnc#gid=1 Response Plan to Feedback (Casting Mgrs)]. |
<br><br> | <br><br> | ||
'''Most common feedback:''' | '''Most common feedback:''' | ||
Line 586: | Line 627: | ||
Inferring from the above table, we identified that some functions of the application may not be sufficiently intuitive (E.g. Items #2, 3 and 4). Perhaps this explains why some testers felt that the system is slightly complex (as shown in Chart 1). | Inferring from the above table, we identified that some functions of the application may not be sufficiently intuitive (E.g. Items #2, 3 and 4). Perhaps this explains why some testers felt that the system is slightly complex (as shown in Chart 1). | ||
− | One of the solutions to get around this is to introduce some simple tooltips to allow the user to get familiarized in using the system. We have also implemented some changes to improve the overall usability and intuitiveness of the application. View our [https://docs.google.com/spreadsheet/ccc?key= | + | One of the solutions to get around this is to introduce some simple tooltips to allow the user to get familiarized in using the system. We have also implemented some changes to improve the overall usability and intuitiveness of the application. View our [https://docs.google.com/spreadsheet/ccc?key=0AskT4ENrBtHIdGhOVUFnTk1TQmFxVHpiOVdySWVQdnc#gid=1 Response Plan to Feedback (Casting Mgrs)]. |
Nevertheless, many users expressed that on the whole, the system is easy to use, streamlined, is “time-saving” and user-friendly. | Nevertheless, many users expressed that on the whole, the system is easy to use, streamlined, is “time-saving” and user-friendly. |
Latest revision as of 17:53, 27 January 2013
MID-TERM WIKI |
Project Progress Summary
Overview
Timberwerkz has completed Sprint 8 on 3 October and 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. |
Technical Complexity
Technical complexity listed in order of highest complexity:
Complexity | Description |
---|---|
1. Audition Assignment Algorithm (Scheduling Auditions) |
|
2. Photo Upload Plugin |
|
3. Search Feature |
|
4. Uploading YouTube Video |
|
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 ManagementPrioritised Risks as at mid-term. Full entries as shown under the Project Management and Technological Implementation headings in the Risk Management Table.
Change Request Management
|
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.
|