Reference no: EM133711739 , Length: word count:2000

Business Process Management

Learning Outcome 1: Analyse the role of information technology in Business Process Mapping.

Learning Outcome 2: Demonstrate capability in the application of a process mapping tool.

GA1: Communication: The ability to communicate persuasively, both orally and in writing, with a diverse range of audiences.
GA3: Research: The ability to conduct and evaluate project.
GA4: Critical thinking & problem solving: The ability to pro-actively identify and solve problems creatively and in a structured and methodical way.
GA6: Flexibility: The ability to critically assess, evaluate and synthesise

Assessment Description

In this project, you will write a comprehensive report analysing the current As-Is of an organisation. You will evaluate the existing business processes and then using the concepts, BPM frameworks that you have learned in this unit you will design an As-Is business process model that addresses the main limitations and challenges of the previous scenario. There are many cases that students can explore. This includes services across different industries such as e-Health, telehealth, transportation, online banking, online studies etc. Students should discuss their topics first with the unit coordinator to confirm their preferred topic.

You are encouraged to attend the workshop on Referencing and Research Practice organised with the Academic Success Team (AST).

The structure of the project is a 2000-word report, the contents of which are detailed below. It is the report that requires submitting as the finished piece of work and this will be marked based on the rubric provided on page 5. Ad hoc work in whatever form will not be marked if submitted.
The word count is 2000 words. This is subject to plus or minus 10%. The word count does not include the executive summary, the table of contents, the list of references or any appendices. However, please note that appendices should be used for supplementary information only: they will NOT be considered for marking.

The report content will comprise of the following sections:

Title page: this must contain the title of the report and your names, unit name, unit number and date of submission.
Table of contents (TOC): ideally, but not necessarily, constructed using the hyperlink functions in Word. Lists of figures and tables are not required.

Executive summary: an executive summary provides an overview of the ENTIRE report. It is NOT an introduction section. It is NOT a background section. The purpose of an executive summary is to provide an understanding of the document without having to read the complete report. Ideally, half to one page in length (but no longer), the executive summary will contain a summary sentence or two on each section of the report. Do not use headings or titles in the executive summary; it should be written in essay narrative format and read seamlessly.

Introduction: the introduction informs the reader of the aims and methods applied in the project. It also defines the scope of the project (what is included and what is not). Whilst it may mention the chosen organisation by name, the introduction DOES NOT talk in detail about the chosen organisation or its industry.

Background: a background informs that reader of the context to the project. Here the organisation and its industry are described. Information about the past performance is presented along with any notes about major milestones. It is easy to ‘go overboard' with this section and consume much word count; one page is all that's needed to set the scene for the project.

Moreover, in this and other sections, too many students often over-rely on company websites. Most times, these websites present an organisation's promotions (advertising) or opinions masquerading as facts. Because of the convenience and profusion of this type of information, it is too easy for students to ignore the authoritative sources of data that can be reached through AIH library databases: however, the use of AIH library databases is the way to higher marks!

Methodology: This section highlights the methodologies applied to your given case. You need to clearly state a reason as to why they used that technique and provide supporting references especially if the technique is relevant for that particular industry.

Results: In this section, students will provide the results of their analyses. The results need to be provided in a logical sequence to ensure that the document is coherent and well synthesized. The results need to clearly show the application of the techniques covered in this unit and that the relevant assumptions in terms of the data have been given due considerations.

Key Findings: The findings of the analyses will be explained in this section. You are expected to be elaborate, and provide an in-depth explanation of the results and why they support or don't support the results of the analyses. You need to provide the necessary reference to support any claims to ensure that the findings are supported by others in that field.

Recommendations: The recommendation highlights any key findings from the analyses that would help the business and organisation address areas that can be improved based on the findings. Recommendation sections are usually concise and provide practical advice to an organisation on areas that needs to be addressed.

Conclusions: Through logical reasoning, this section should summarise how the project objectives have been achieved using appropriate business analytics tools and techniques.

List of references: this should be formatted in Harvard style.

Use Harvard referencing including the reference list