9.1 Resource identication Multiple roles are needed to be lled to undertake each task and successfully complete the project. System Administrator, Software Engineer, Ul 1 UK Designer, Creative Lead, Marketing Coordinator, Market Research Specialist, Accounts Ofcer 5: Procurement Coordinator are all roles that have been identied with the project. Majority of these roles can be derived from the company, although the design team can be sourced from an external company that will develop the interface and support the IT team. 9.2 Resource Scheduling After analysing the tasks that need to be completed it was decided that there would be one person in each of these positions leading a team. The leaders would be in direct contact with each other and have the chance to speak to the other leaders together during a weekly meeting. Some of these teams were originally grouped together, after the change control process was implemented these teams were split and became eight groups of three. The project consists of a labourforce that is made up of one leader and two employees in their respective roles, this gives us a human resource count of 24. After there was an increase in groups it was found that output was greater as each team had less to focus on, the overall Iabourforce was slightly increased, although costs would not be greater as the ti mefra me has decreased. 9.3 Resource Risks Due to an increase in labour it was a concern that there could be too many individuals involved in the project that would not have the same effect as a smaller more engaging team. It was decided that as long as the team leaders communicate and keep each other informed the project would be successful. Weekly meetings would avoid the risk of confusion among all involved in the development of the app. A limited supply of skilled workers would contradict the plan of increasing the workforce in order to increase productivity. All personnel working on the project will undergo thorough training and development. It was also a concern that time would be wasted passing information on to other teams, operations would be threatened to come to a hult until all project information was transferred to the other departments. This should nt cause any delays as the project schedule has taken the leadership meetings into consideration