IS480 Team wiki: 2016T2 Friendchise Change Management

HOME

ABOUT US

PROJECT OVERVIEW

PROJECT MANAGEMENT

DOCUMENTATION

 

Project Schedule

Metrics

Risk Assessment

Change Management

Steps for Change Management

Iteration	Date Requested (DDMMYYYY)	Feature	Description	Reason for Change Request	Feasibility	Accept/Reject	Status
5	2/11/2015	Blacklist job applicants	To include a blacklist feature in the administrator web application.	Client would like to ease the filtering process of retaining or removing the type of job applicants from the actual application assessing process.	Team has decided that this suggestion would not value add to the app and its users in the short run.	Reject	-
5, 6, 7	10/11/2015	Remove Web Dashboard modules	To remove web dashboard modules from project scope.	Team has to re-plan project scope due to a change in the number of group members. These modules will be taken into consideration again once the core and important functions are completed and if time persists.	Team has decided the role of each team member to better cater to the needs of the group.	Accept	To be completed in iteration 8 - done
8	21/12/2015	Change in team roles	To revise the role of each team member.	Roles of each team member has to be revised because of a change in the number of group members.	Team has decided the role of each team member to better cater to the needs of the group.	Accept	To be completed in iteration 8 - done
12	15/2/2016	Jobs Available	To include full-time job positions. The target audience for the full-time job positions in the RWS Jobs app would be similar to that of the existing part-time/casual job seekers.	Client would like to cater more jobs (full-time/part-time/casual) to the similar target audience.	Team has decided that this suggestion would indeed meet the client’s goal to reach a greater number of applicants in similar age-groups.	Accept	To be completed in iteration 12 - done
11	2/2/2016	New application statuses	To add more application statuses to the existing statuses (Shortlisted, Rejected, Blacklisted, Confirmed).	Addition of applications can cater to a more detailed job application process.	Team has decided that this suggestion would be beneficial for a more comprehensive job application process.	Accept	To be completed in iteration 12 - done
12	15/2/2016	Identification Number field label for “Non-Singaporean”.	To change the identification number field label for “Non-Singaporean” citizenship type to “FIN & Passport No.”.	Client expressed that both the FIN and passport number of a non-Singaporean job applicant is necessary for job applications.	Team has decided that this suggestion would indeed meet the requirements of the client.	Accept	To be completed in iteration 12 - done
12	15/2/2016	Mandatory NRIC field in registration page.	To add a “*” symbol to the NRIC field in registration page.	To add a “*” symbol to indicate that the NRIC field for “Singaporean” citizen type is mandatory.	Team has decided that this suggestion would indeed meet the requirements of the client.	Accept	To be completed in iteration 12 - done
12	15/2/2016	Email address and password as login credentials.	To change the unique identifier of a user to their email address instead of a username.	Usernames of users have no use to the client, thus rendering it redundant.	Team has decided that this suggestion would indeed meet the requirements of the client.	Accept	To be completed in iteration 12 - done
12	15/2/2016	Login app via LinkedIn.	To allow users to login app via their LinkedIn accounts.	Ease of registration and login for users.	Client has decided that the login feature via LinkedIn is redundant as they do not require any user information from LinkedIn.	Reject	-
12	15/2/2016	Full Name field label in registration page.	To label the Full Name filed as “Full Name (as in NRIC)”.	Client requires each job applicant to indicate their full name as indicated in their NRIC.	Team has decided that this suggestion would indeed meet the requirements of the client.	Accept	To be completed in iteration 12 - done
12	15/2/2016	Camera detection feature	To use camera feature to capture passport details (including passport photo) or NRIC details.	The objective of this feature is to avoid any duplicate users/applicants.	Team has decided that this suggestion would be beneficial for a more comprehensive job application process.	Accept	To be done in iteration 14 - done
12	15/2/2016	Forget Password feature	To implement a “Forget Password” feature.	This feature allow users to reset forgotten passwords.	Team has decided that this is an essential feature.	Accept	To be completed in iteration 12 - done
12	15/2/2016	Disable “Email Address”, “NRIC” and “Birthdate” fields	Disable “Email Address”, “NRIC” and “Birthdate” fields in “My Profile” page.	Client expressed that users should not be allowed to edit the following fields: “Email Address”, “NRIC” and “Birthdate”.	Team has decided that this suggestion would indeed meet the requirements of the client.	Accept	To be completed in iteration 12 - done
12	15/2/2016	Physical differentiating label for seen/unseen job postings	To implement physical differentiating label for seen/unseen job postings.	The objective of this feature is for better usability for all job postings.	Team has decided to focus on another feature (Adding thumbnail icons to each job posting).	Reject	-
12	15/2/2016	Thumbnail tagged to each job posting	Thumbnails can be uploaded from web application.	The objective of having thumbnails for each job posting is to improve visibility of the job posts.	Team has decided that this suggestion would be beneficial for the aesthetic of the app.	Accept	To be completed in iteration 12 - done
12	15/2/2016	Email notification to job applicants when job status is “Confirmed”	Email notification to job applicants to request for other necessary documents (i.e. bank statement, bank book, etc.).	The objective of this feature is to complete the full hiring process.	Team has decided that this suggestion would be beneficial for a more comprehensive job application process.	Accept	To be completed in iteration 12 - done
12	15/2/2016	UI/UX Implementation of About Us page	To include client’s social media pages in About Us page.	The objective of this feature is to create awareness for the organization.	Team has decided that this suggestion would indeed meet the requirements of the client.	Accept	To be completed in iteration 13 - done
12	15/2/2016	Character limit for job description and job requirement fields	To implement a character limit for both job description and requirement fields upon creation of a new job posting.	This feature is to keep the length of a job description and requirement succinct.	Team has decided that this suggestion would indeed meet the requirements of the client.	Accept	To be completed in iteration 12 - done
13	1/3/2016	Project Management - change in role	Role of Mandes is changed to administrative and documentation management.	Team decided that this would increase the efficiency of completing outstanding project tasks.	Team has decided that this suggestion would indeed increase team efficiency.	Accept	-
14	18/3/2016	Job application statuses	To assign a different colour to each job application status.	Supervisor expressed that the different colours would be able to better differentiate each of the statuses.	Team has decided that this suggestion would indeed meet the requirements of the client and supervisor.	Accept	To be completed by iteration 14 - done
14	18/3/2016	Mobile app user registration	To add commitment period in user registration.	Client expressed that this is a good-to-have field for data gathering.	Team has decided that this suggestion would indeed meet the requirements of the client.	Accept	To be completed by iteration 14 - done
15, updated from iteration 12	28/3/2016	Image thumbnails for each job post	To replace image thumbnail with expected salary/hr for each job position.	Friendchise expressed that this would better value add to the information displayed for each job post.	Team has decided that this suggestion would indeed meet the requirements of the client.	Accept	To be completed by iteration 15 - done
15	30/3/2016	Notifications	To differentiate each notification according to their types.	Client expressed that this would be more intuitive for users.	Team has decided that this suggestion would indeed meet the requirements of the client.	Accept	To be completed by iteration 15 - done