Scenario Motorhome Spares Wales (MSW) is a company that sells new and second-hand replacement parts for motor homes and camper vans. It does this primarily from its network of 13 shops in and around Wales and the South West. As well as being able to buy items in store, purchases can also be made by contacting a call centre or by mail-order. MSW produces a quarterly parts catalogue. The catalogue is distributed by mail to existing customers or can be picked up in store. MSW does not currently sell its goods online. It does however recognise the potential of online selling to increase local sales and, more importantly, to gpen up its business to new markets throughout the rest of the UK (and beyond). It is, therefore, currently considering investing in the development of a web site that will allow users to browse and purchase items. Another significant benefit of having the web site is that it will allow MSW to provide customers with a stock list that is complete and up to date (currently the catalogue only gets updated four times a year and does not list second-hand parts). In time, the web site will allow MSW to stop producing the quarterly catalogue. MSW is already extensively computerised, but the current systems that are in place are very dated. Existing software will only run on a now obsolete operating system. The existing hardware does not have the capacity to support web-based sales. A decision has therefore been made to replace all existing software and hardware (if, and when, the new web site development gets the go-ahead). Any new computer system must be able to support all existing functionality: mail-order and call centre ordering in-store sales despatch of goods to customers stock control sales forecasting (based on recent and historic sales figures) links to the financial accounting software running on another system The new system must also support web-based sales, and will therefore require the following extra features: a web server and associated software front-end database driven web site (allowing users to view and order goods) on-line payment system back-end content management system (CMS) a suitable relational database management system security software MSW plan to outsource the entire project to local company Wales Software Solutions (WSS). WSS will be responsible for sourcing and installation of all hardware and the development and deployment of all software. MSW have used WSS for several previous projects and have been pleased with the cost and quality of their work, However, before any firm decision is made regarding the project, WSS must produce a Project Initiation Document (PID). This document will help MSW decide if the project goes ahead or not. Your team Your team works for WSS and has been tasked with preparing the Project Initiation Document for the project You must assume that estimates of project costs, benefits and resources already exist (see below). In addition, an initial analysis of the project has resulted in a preliminary set of required tasks, their duration and required resource (see below). Reduced mail-order and telephone sales should allow MSW to reduce call centre staff by 3 (currently costing 18,000 each per year including overheads) but only after the new system has been running smoothly for 6 months. The new system will remove the need for quarterly catalogue production, printing and distribution costs (currently 10,500 per quarter). 2 years after web site deployment there will be overall marketing savings to MSW of 12,000 per year Project Costs Initial estimates for project costs are given below. These costs are based on a specific solution option. Alternative options may be considered as part of project Stage 1. One-off hardware Business Case You are required to assess the financial viability of the proposed project using the estimated costs and benefits given above. Assume a discount rate of 5.5%. You must then recommend whether to proceed with the project or not. You should consider how critical the benefit estimate and discount rate values are to your calculation. You might also want to make suggestions for how the profitability of the project could be increased. Assume that the product development takes place throughout the duration of project Year O. The system will "go live" at the start of Year 1 and is expected to have a 7-year lifespan. . Dedicated servers: 35,000 Workstations: 10,000 Ethernet, routers and other connections: 20,000 : Printers and scanners: 10,000 Annual software cost (Year 0 onwards) 0 ) If you can justify other costs or benefits, you may include them in the calculation. Suggested project tasks Task Resource ERP software (licence): 45,000 Server software (including database): 20,000 : Developer software: 25,000 Duration (days) 1.1 1.2 Stage 1 Formal progress review meeting Prepare/amend detailed plans for Stage 1 3 Annual support (Year 1 onwards): 1 only Software: 11,500 Hardware: 8,500 1.3 1.4 1.5 1.6 1.7 1.8 1.9 1 1 1 3 3 6 1 1 4 Quality review Stage 1 plans Formal progress review meeting Provide Stage 1 plans to lecturer Prepare critical path of Stages 2 to 5 Produce Project Initiation Document Formal progress review meeting Produce final review, compile all documents ready for submission Formal progress review meeting to sign off work One-off development ERP software (replaces most existing systems): 100,00 In-store sales software: 30,000 Sales forecasting module: 20,000 E-commerce software (new system, including database and CMS): 105,000 MSW staff: 100 staff days at an average of 300.0 per day 1.10 1 Annual data cost (Middle of year 0 onwards) 2.1 2.2 Stage 2 Confirm user requirements Produce options for solution to user requirements Quality review Stage 2 30 25 Systems analyst Systems analyst Geodemographic data: 60,000 2.3 8 Quality review team Annual staff cost (Year 1 onwards): 1 systems manager: 55,000 systems technicians: 30,000 each 3.1 3.2 3.3 Stage 3 Produce design documentation Quality review design Source and purchase hardware 55 8 8 3.4 Project benefits Initial estimates for project financial benefits are: Source and purchase software 6 Systems analyst Quality review team Computer technician Purchasing officer Software developer Web/database developer Purchasing officer Software developer Software developer Web/database developer Purchasing officer Increased sales 3.5 3.6 Develop in-store sales software Web site development 10 15 Net profit to increase by 150,000 in the calendar year after the system goes live, 350,000 the year after that, and 550,000 each year thereafter. 3.7 Source and purchase data 8 Reduced costs 4.1 4.2 Stage 4 Install servers Load software 7 6 Computer technician Computer technician Web/database developer Computer technician 4.3 5 The PID must define Stages 2 to 5 of the proposed project, setting out the reason for the project, justifying the expenditure, specifying the expenditure and time plans and allocating responsibilities for the project. . 4.4 5 Computer technician Install all cabling for workstations and printers Install workstations, printers and internet connection Perform hardware test Quality review hardware installation Customise and configure software The PID must be structured as follows: 4.5 4.6 4.7 5 3 50 4.8 Perform basic test of software 8 Computer technician Quality review team Software developer Web/database developer Software developer Web/database developer Software technician Software technician Software technician Software technician Computer technician 4.9 4.10 4.11 4.12 Prepare user instructions Prepare user training Prepare user acceptance test plans Load and configure data 10 8 8 8 9 Title and contents pages (team letter and team member enrolment numbers must be included on this page) Project definition, including project scope and completion criteria (4 marks) Project justification including a NPV spreadsheet of income and expenditure plans for 7 years. For NPV calculation assume that development takes place during Year O and deployment takes place at start of Year 1 (the Gantt chart is likely to indicate otherwise) (15 marks) Precedence table produced for each stage- it is suggested you use MS Project (10 marks) Time plans for Stages 2 to 5 of the project in CPA network diagram and Gantt chart formats - these must be produced using MS Project (or equivalent software) (8 marks) * Resource usage table (3 marks) 7 5.1 5.2 5.3 5.4 Stage 5 Train end users Perform user acceptance test Quality review the acceptance test Review project 7 5 10 Software technician Software technician Quality review team Project team Gantt chart, Excel document and MS Project files can be included as part of your submission if you want. Your team may be required to demonstrate your MS Project CPA and Gantt chart to your module tutor. Notes: (1) Stage 1 represents coursework Deliverable A. The tasks shown for Stage 1 are therefore illustrative - you need to change these tasks to reflect what you plan to do. Also note - you can manage Stage 1 using any appropriate project management framework (subject to approval). (2) You may amend tasks in Stages 2 to 5 if you think tasks are not needed, or some have been omitted, or some should be split up. You must discuss any changes with Mark Ware; be prepared to justify any changes. (3) You must decide the predecessors for the tasks. As a general.cule, run tasks in parallel wherever possible to reduce the total project duration. (4) Stages 2 to 5 must be conducted Mondays to Fridays, and not during public holidays. The Gantt chart for Stages 2 to 5 must show calendar dates starting 28th February 2022. (5) Stages 2 to 5 must adopt a Waterfall approach to stage scheduling- Deliverable B-Evidence of coursework management (40 marks) This coursework can be regarded as a project and must be managed appropriately. Your submission must therefore include detail on how you managed the coursework. This is your opportunity to demonstrate and showcase your knowledge and understanding of the project management approaches taught in class. As part of the project management process, it is important for your team to meet regularly (either in-person or virtually) these meetings should be documented. You must provide clear evidence of how the coursework was managed. Deliverable C - Individual Review (20 marks) Each team member must produce an individual review of the coursework. The review should describe and analyse how the coursework was conducted and include detail on: who did what; who checked what; what went well; and, what you would do differently if you had to do it again. Resources At any given time, the following resources will be available to Stages 2 to 5 of the project: The review must adopt the following format: 1 page of A4 paper, font - black 11-point Arial. Page heading showing title, team letter and student number Submission Instructions Quality review team x 1 Web/database developer x 1 Software developer x 1 Software technician x 1 Systems analyst x 1 Application programmer x 1 Computer technician x 1 Purchasing officer x 1 Deliverables A, B and C should be submitted as a single zipped folder/file via Unilearn/Blackboard. This zipped folder/file should be named IS25561_CW1M_San Teamx where X is your team letter. Each deliverable must list the enrolment numbers of all team members. There should be 1 submission per team. Text-based documents must be submitted in MS Word or PDF format. Your Task This coursework has 3 deliverables. . Gantt chart, Excel document and MS Project files can be included as part of your submission if you want. Your team may be required to demonstrate your MS Project CPA and Gantt chart to your module tutor Any additional evidence of work undertaken should be included as an appendix Deliverable A - PID (40 marks) Your Team has been tasked with producing the Project Initiation Document (PID) for the project outlined above. Scenario Motorhome Spares Wales (MSW) is a company that sells new and second-hand replacement parts for motor homes and camper vans. It does this primarily from its network of 13 shops in and around Wales and the South West. As well as being able to buy items in store, purchases can also be made by contacting a call centre or by mail-order. MSW produces a quarterly parts catalogue. The catalogue is distributed by mail to existing customers or can be picked up in store. MSW does not currently sell its goods online. It does however recognise the potential of online selling to increase local sales and, more importantly, to gpen up its business to new markets throughout the rest of the UK (and beyond). It is, therefore, currently considering investing in the development of a web site that will allow users to browse and purchase items. Another significant benefit of having the web site is that it will allow MSW to provide customers with a stock list that is complete and up to date (currently the catalogue only gets updated four times a year and does not list second-hand parts). In time, the web site will allow MSW to stop producing the quarterly catalogue. MSW is already extensively computerised, but the current systems that are in place are very dated. Existing software will only run on a now obsolete operating system. The existing hardware does not have the capacity to support web-based sales. A decision has therefore been made to replace all existing software and hardware (if, and when, the new web site development gets the go-ahead). Any new computer system must be able to support all existing functionality: mail-order and call centre ordering in-store sales despatch of goods to customers stock control sales forecasting (based on recent and historic sales figures) links to the financial accounting software running on another system The new system must also support web-based sales, and will therefore require the following extra features: a web server and associated software front-end database driven web site (allowing users to view and order goods) on-line payment system back-end content management system (CMS) a suitable relational database management system security software MSW plan to outsource the entire project to local company Wales Software Solutions (WSS). WSS will be responsible for sourcing and installation of all hardware and the development and deployment of all software. MSW have used WSS for several previous projects and have been pleased with the cost and quality of their work, However, before any firm decision is made regarding the project, WSS must produce a Project Initiation Document (PID). This document will help MSW decide if the project goes ahead or not. Your team Your team works for WSS and has been tasked with preparing the Project Initiation Document for the project You must assume that estimates of project costs, benefits and resources already exist (see below). In addition, an initial analysis of the project has resulted in a preliminary set of required tasks, their duration and required resource (see below). Reduced mail-order and telephone sales should allow MSW to reduce call centre staff by 3 (currently costing 18,000 each per year including overheads) but only after the new system has been running smoothly for 6 months. The new system will remove the need for quarterly catalogue production, printing and distribution costs (currently 10,500 per quarter). 2 years after web site deployment there will be overall marketing savings to MSW of 12,000 per year Project Costs Initial estimates for project costs are given below. These costs are based on a specific solution option. Alternative options may be considered as part of project Stage 1. One-off hardware Business Case You are required to assess the financial viability of the proposed project using the estimated costs and benefits given above. Assume a discount rate of 5.5%. You must then recommend whether to proceed with the project or not. You should consider how critical the benefit estimate and discount rate values are to your calculation. You might also want to make suggestions for how the profitability of the project could be increased. Assume that the product development takes place throughout the duration of project Year O. The system will "go live" at the start of Year 1 and is expected to have a 7-year lifespan. . Dedicated servers: 35,000 Workstations: 10,000 Ethernet, routers and other connections: 20,000 : Printers and scanners: 10,000 Annual software cost (Year 0 onwards) 0 ) If you can justify other costs or benefits, you may include them in the calculation. Suggested project tasks Task Resource ERP software (licence): 45,000 Server software (including database): 20,000 : Developer software: 25,000 Duration (days) 1.1 1.2 Stage 1 Formal progress review meeting Prepare/amend detailed plans for Stage 1 3 Annual support (Year 1 onwards): 1 only Software: 11,500 Hardware: 8,500 1.3 1.4 1.5 1.6 1.7 1.8 1.9 1 1 1 3 3 6 1 1 4 Quality review Stage 1 plans Formal progress review meeting Provide Stage 1 plans to lecturer Prepare critical path of Stages 2 to 5 Produce Project Initiation Document Formal progress review meeting Produce final review, compile all documents ready for submission Formal progress review meeting to sign off work One-off development ERP software (replaces most existing systems): 100,00 In-store sales software: 30,000 Sales forecasting module: 20,000 E-commerce software (new system, including database and CMS): 105,000 MSW staff: 100 staff days at an average of 300.0 per day 1.10 1 Annual data cost (Middle of year 0 onwards) 2.1 2.2 Stage 2 Confirm user requirements Produce options for solution to user requirements Quality review Stage 2 30 25 Systems analyst Systems analyst Geodemographic data: 60,000 2.3 8 Quality review team Annual staff cost (Year 1 onwards): 1 systems manager: 55,000 systems technicians: 30,000 each 3.1 3.2 3.3 Stage 3 Produce design documentation Quality review design Source and purchase hardware 55 8 8 3.4 Project benefits Initial estimates for project financial benefits are: Source and purchase software 6 Systems analyst Quality review team Computer technician Purchasing officer Software developer Web/database developer Purchasing officer Software developer Software developer Web/database developer Purchasing officer Increased sales 3.5 3.6 Develop in-store sales software Web site development 10 15 Net profit to increase by 150,000 in the calendar year after the system goes live, 350,000 the year after that, and 550,000 each year thereafter. 3.7 Source and purchase data 8 Reduced costs 4.1 4.2 Stage 4 Install servers Load software 7 6 Computer technician Computer technician Web/database developer Computer technician 4.3 5 The PID must define Stages 2 to 5 of the proposed project, setting out the reason for the project, justifying the expenditure, specifying the expenditure and time plans and allocating responsibilities for the project. . 4.4 5 Computer technician Install all cabling for workstations and printers Install workstations, printers and internet connection Perform hardware test Quality review hardware installation Customise and configure software The PID must be structured as follows: 4.5 4.6 4.7 5 3 50 4.8 Perform basic test of software 8 Computer technician Quality review team Software developer Web/database developer Software developer Web/database developer Software technician Software technician Software technician Software technician Computer technician 4.9 4.10 4.11 4.12 Prepare user instructions Prepare user training Prepare user acceptance test plans Load and configure data 10 8 8 8 9 Title and contents pages (team letter and team member enrolment numbers must be included on this page) Project definition, including project scope and completion criteria (4 marks) Project justification including a NPV spreadsheet of income and expenditure plans for 7 years. For NPV calculation assume that development takes place during Year O and deployment takes place at start of Year 1 (the Gantt chart is likely to indicate otherwise) (15 marks) Precedence table produced for each stage- it is suggested you use MS Project (10 marks) Time plans for Stages 2 to 5 of the project in CPA network diagram and Gantt chart formats - these must be produced using MS Project (or equivalent software) (8 marks) * Resource usage table (3 marks) 7 5.1 5.2 5.3 5.4 Stage 5 Train end users Perform user acceptance test Quality review the acceptance test Review project 7 5 10 Software technician Software technician Quality review team Project team Gantt chart, Excel document and MS Project files can be included as part of your submission if you want. Your team may be required to demonstrate your MS Project CPA and Gantt chart to your module tutor. Notes: (1) Stage 1 represents coursework Deliverable A. The tasks shown for Stage 1 are therefore illustrative - you need to change these tasks to reflect what you plan to do. Also note - you can manage Stage 1 using any appropriate project management framework (subject to approval). (2) You may amend tasks in Stages 2 to 5 if you think tasks are not needed, or some have been omitted, or some should be split up. You must discuss any changes with Mark Ware; be prepared to justify any changes. (3) You must decide the predecessors for the tasks. As a general.cule, run tasks in parallel wherever possible to reduce the total project duration. (4) Stages 2 to 5 must be conducted Mondays to Fridays, and not during public holidays. The Gantt chart for Stages 2 to 5 must show calendar dates starting 28th February 2022. (5) Stages 2 to 5 must adopt a Waterfall approach to stage scheduling- Deliverable B-Evidence of coursework management (40 marks) This coursework can be regarded as a project and must be managed appropriately. Your submission must therefore include detail on how you managed the coursework. This is your opportunity to demonstrate and showcase your knowledge and understanding of the project management approaches taught in class. As part of the project management process, it is important for your team to meet regularly (either in-person or virtually) these meetings should be documented. You must provide clear evidence of how the coursework was managed. Deliverable C - Individual Review (20 marks) Each team member must produce an individual review of the coursework. The review should describe and analyse how the coursework was conducted and include detail on: who did what; who checked what; what went well; and, what you would do differently if you had to do it again. Resources At any given time, the following resources will be available to Stages 2 to 5 of the project: The review must adopt the following format: 1 page of A4 paper, font - black 11-point Arial. Page heading showing title, team letter and student number Submission Instructions Quality review team x 1 Web/database developer x 1 Software developer x 1 Software technician x 1 Systems analyst x 1 Application programmer x 1 Computer technician x 1 Purchasing officer x 1 Deliverables A, B and C should be submitted as a single zipped folder/file via Unilearn/Blackboard. This zipped folder/file should be named IS25561_CW1M_San Teamx where X is your team letter. Each deliverable must list the enrolment numbers of all team members. There should be 1 submission per team. Text-based documents must be submitted in MS Word or PDF format. Your Task This coursework has 3 deliverables. . Gantt chart, Excel document and MS Project files can be included as part of your submission if you want. Your team may be required to demonstrate your MS Project CPA and Gantt chart to your module tutor Any additional evidence of work undertaken should be included as an appendix Deliverable A - PID (40 marks) Your Team has been tasked with producing the Project Initiation Document (PID) for the project outlined above