|
|
Line 379: |
Line 379: |
| |} | | |} |
| | | |
− | <br> | + | <br><div style = "text-align:right; padding: 0px 30px 0px 45px;">[[IS480_Team_wiki:_2012T1_Timber_Werkz_ProjectDocumentation#Top|Back to Top]]</div> |
| | | |
| ===Supervisor Meeting=== | | ===Supervisor Meeting=== |
Revision as of 18:20, 28 November 2012
HOME
|
|
PROJECT OVERVIEW
|
|
|
PROJECT MANAGEMENT
|
|
DOCUMENTATION
|
|
<< MID-TERM WIKI << FINAL WIKI
Change Request Log
View Change Request Log
Change Request Management
- 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
- The following chart on the right shows our Change Management Decision Process (How we decide an implementation based on the priority and time)
- Scenario #1: If a priority level is a MUST, then we will implement the request
- 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
- Scenario #3: If a priority level is a COULD, then we will implement the request if the time to do so is VERY SHORT
- Scenario #4: If a priority level is a WON'T, then we will not implement the request
|
Meeting Minutes (Sorted Latest First)
Client Meeting
Minutes as at MIDTERM
|
Minutes as at FINALS
|
Date
|
Link
|
Agenda
|
Supporting Documents
|
09 NOV 2012
|
Client Minutes 11
|
- Show audition platform video
- Soft launch arrangement
- Updates on change requests made last meeting
- Show handover process checklist
- Invitation to FYP Final Presentation
|
-
|
09 NOV 2012
|
Client Minutes 10
|
- Update Oak3 on New Features, Gather Elaboration and Change Requests
- Change Requests for Schedule Audition
- Elaboration for Manage Messages
- User Testing 2: Soft Launch
|
-
|
16 OCT 2012
|
Client Minutes 9
|
- Updates Oak3 on New Features, Gather Elaboration and Change Requests
- Schedule Audition & Apply for Casting Call
- User Testing 2
- Production Environment Admin Matters
|
-
|
17 SEP 2012
|
Client Minutes 8
|
- Demonstration and updates
- Propose new feature to support more than one accounts to each production house
- Change in project schedule
- Updates on usability test 1
|
|
27 AUG 2012
|
Client Minutes 7
|
- Demonstration of current application
- Confirmation of Process Flow to schedule for auditions
|
-
|
16 AUG 2012
|
Client Minutes 6
|
- Confirm Usability Testing Dates
- Obtain User Data
- UI Mockup for scheduling an interview
- Going through updated features & gathering feedback
|
|
2 AUG 2012
|
Client Minutes 5
|
- Update on project progress
- Artist Portfolio Page
- Edit Portfolio Page
- Search by Production House
- View Casting Call
- Admin Console
- Production Portfolio Page
- Get Feedback on UI Mockup for Manage Experience
- Miscellaneous
|
-
|
19 JUL 2012
|
Client Minutes 4
|
- Update & get feedback on project progress:
- Show Edited Artiste Portfolio page
- View Main Search Page
- View Search Result Page
- Set & View Favourite on Search page
- Get Feedback on UI Mockup - View Casting Call
- Receive Requests for how Production House Portfolio's UI should look like
- Get Approval for stories pending approval
|
|
2 JUL 2012
|
Client Minutes 3
|
- Update on project progress:
- Changes in the product backlog (added new chapters)
- Updates to Sprint 2
- Stories Completed and being worked on
- Approval of stories that have been implemented (seen in demo videos)
- Get Feedback on UI Mockup for Search & Experience
- Joomla Discussion
|
|
7 JUN 2012
|
Client Minutes 2
|
- Update and questions on project management, functional specifications and technical specifications
|
|
23 MAY 2012
|
Client Minutes 1
|
- Sharing of functional requirements by client
- Questions from team:
- Technical requirements for project
- User interface of project
- Project schedule requirements
- Contacts for communication
- Stakeholder reporting
|
|
Team Meeting
Minutes as at MIDTERM
|
Minutes as at FINALS
|
Date
|
Link
|
Agenda
|
Supporting Documents
|
30 OCT 2012
|
Team Minutes 14
|
- Additional Discussion for User Testing 2
|
-
|
9 OCT 2012
|
Team Minutes 13
|
- User Testing 2 Discussion
- Elaboration of User Management, Create Audition stories
- Team Administration
|
-
|
2 OCT 2012
|
Team Minutes 12
|
- Discuss presentation flow for Mid Terms
|
-
|
11 SEP 2012
|
Team Minutes 11
|
- Review Feedback from user testing
- Prepare for artiste testing
|
-
|
7 AUG 2012
|
Team Minutes 10
|
- Acceptance presentation: Preparation and Tasking
|
-
|
30 JUL 2012
|
Team Minutes 9
|
- Update Jun Ru, Calvin and Nikita on team's progress
|
-
|
16 JUL 2012
|
Team Minutes 8
|
- Update on Team Progress
- Update on UI Mockup - Casting Calls
- Issues to confirm with client
- Acceptance presentation plan
- Updating of logical & deployment diagram
|
-
|
25 JUN 2012
|
Team Minutes 7
|
- Update on Product Backlog issues
- Prepare UI Mockup for Experience & Search
- Create demo videos for client
- Update Sprint 2
|
-
|
11 JUN 2012
|
Team Minutes 6
|
- Selenium team sharing
- Review UI Mockup, decide changes to be made from client meeting
- Decide stories to be completed in Sprint 2
|
-
|
28 MAY 2012
|
Team Minutes 5
|
- Review Sprint 1’s schedule
- Finalize IS480 Proposal
- Decide objectives and content for meeting with Prof. Gan and Clients' meeting
|
-
|
23 MAY 2012
|
Team Minutes 4
|
- Resume knowledge sharing session
- Discussion on group admin issues
- Arrange meetings with client & supervisor
|
-
|
22 MAY 2012
|
Team Minutes 3
|
- Knowledge sharing session on jQuery Air and CSS
- Knowledge sharing session on the yii framework
- Complete setting up of systems (development environemnt etc.)
|
-
|
14 MAY 2012
|
Team Minutes 2
|
- Collective development of project proposal
- Sharing of SCRUM cloud platforms
- Knowledge sharing session to be carried out at next meeting
|
-
|
7 MAY 2012
|
Team Minutes 1
|
- Assigning of roles and responsibilities
- Establishing project milestones
- Start development of project proposal
- Elaborate on functional requirements
- Elaborate on technical requirements and decide upon development framework & project management framework
|
-
|
Supervisor Meeting
Minutes as at MIDTERM
|
Minutes as at FINALS
|