MGT8022 PROJECT-BASED MANAGEMENT ASSIGNMENT 1 MARK SHEET Student name RAJESH SUNDARESAN Student number (starts with 00xxxxxxxx) 0061073495 It is recommended that you start writing your assignment on the last page of this document. Alternatively, you can attach your assignment to this mark sheet but be careful that formatting is the same for both documents before doing so. Assignments submitted without this mark sheet will lose marks. This mark sheet: • provides students with details of the marking criteria for this assignment including penalties for non-compliance with specific requirements, • acts as a checklist to ensure that students have addressed all requirements, and • is used by markers for providing feedback and marks for the assignment. FORMATTING You may have to adjust the page formatting before attaching your assignment. It is suggested that you use the following formatting for your assignment before pasting it onto the last page of this mark sheet: TOP MARGIN – 2.5 cm BOTTOM MARGIN – 2.5 cm SIDE MARGINS – 2.5 cm FILE NAMING GUIDELINES Your assignment file name should be MGT8022_2017_S1_A1 IMPORTANT NOTE Remember to submit a copy of your assignment (without this mark sheet and appendices) to Turnitin and to obtain an Originality Report for submission through EASE www.turnitin.com See the Introductory Materials for more information MGT8022 ASSIGNMENT 1 MARK SHEET – PROJECT-BASED MANAGEMENT (Note to markers – indicate level of achievement for each row by highlighting relevant text or cell - do not provide a numerical score for each row) Non-compliant Poor/inadequate Basic Adequate Good Excellent Mark Comments ASSIGNMENT REQUIREMENTS (out of 60) 0 0 to 29 30 to 38 39 to 44 45 to 50 51 to 60 19/60 Critical analysis essay Introduction to the essay No introduction provided Poor introduction provided, or irrelevant information Basic introduction provided Adequate introduction provided Good clear introduction provided Clear, concise and comprehensive introduction providing essential details Analysis: Write a critical analysis of the chosen project business case in the form of an essay about the issues that you think are important in the context of the business case for your chosen project. IMPORTANT NOTE: THIS IS A CRITICAL ANALYSIS OF THE USE OF THE BUSINESS CASE AND NOT OF THE WHOLE PROJECT. No analysis of the nominated topic Poor or inadequate analysis of the topic Basic analysis of the topic, with limited use of theory to support the analysis Adequate analysis of the topic using appropriate theory Good analysis of the topic using appropriate theory Clear, concise and comprehensive analysis of the topic, supported by appropriate theory, figures and tables. Conclusions drawn from the analysis No conclusions provided Poor or inadequate conclusions provided Basic conclusions provided Adequate conclusions derived from the preceding analysis Good conclusions derived from the preceding analysis Clear, concise and comprehensive conclusions derived from, and justifiably supported by, the preceding analysis RESEARCH & ACADEMIC THEORY (out of 30) 0 0 to 14 15-22 23 to 30 10/30 Quality of critical analysis - uses appropriate theoretical principles as a framework for analysis No use of theoretical principles Poor or inadequate use of theoretical principles Basic use of theoretical principles Adequate use of theoretical principles Good use of theoretical principles Extensive use of theoretical principles and appropriate application to the project and its environment Argument is well structured, logical, and well reasoned (compelling) No logical argument provided Poor or inadequate structure and argument Basic structure and argument Appropriate structure and argument Good structure and argument Well structured, logical, and well-reasoned Figures and tables are appropriately used and adapted in the analysis to clearly illustrate/ compare/contrast theoretical principles with project practices. No use of tables and/or figures where their inclusion is justified Poor or inadequate figures and tables where used Basic figures and tables where used Adequate figures and tables where used. Good figures and tables where used Excellent adaptation of figures and tables where used Evidence of research is provided to support the analysis and argument. No evidence of research into the topic Poor or inadequate evidence of research Basic evidence of research Adequate evidence of research beyond the study materials and set text Good evidence of research beyond the study materials and set text Evidence of extensive research beyond the study materials and set text to support the analysis and argument Evidence of knowledge of study materials and general knowledge of the project management domain is provided No indication of knowledge of study materials Poor or inadequate indication of knowledge of study materials Basic indication of knowledge of study materials Indication of adequate knowledge of study materials Indication of good knowledge of study materials Evidence of extensive knowledge of study materials and of PM domain Quality of resources – evidence of use of research resources from quality sources (e.g. journal articles, texts, conference papers, etc) No use of research resources Poor quality sources of reference materials (e.g. websites, Wikipedia, etc.) Basic quality sources of reference materials (e.g. websites, Wikipedia, etc.) Adequate quality of sources of research Good quality of sources of research Excellent sources of research resources, including journals, texts, conference papers, etc. Citations are effectively and appropriately provided (and consistent with the Harvard referencing system) No use of citations Poor or inadequate use of citations within the text Basic use of citations within the text Adequate use of citations within the text Good use of citations within the text Extensive and appropriate use of citations to reflect use of theory in analysis and argument List of references is provided and shows quality sources No list of references Poor or inadequate list of references (<10) Basic list of references (<10) Adequate list of references (>10) Good list of references (>10) Comprehensive list of relevant references Harvard referencing system is used and conforms to Harvard style as defined on USQ Library website (e.g. alphabetical order) No use of Harvard referencing system Poor or inadequate use of Harvard system of referencing Basic use of Harvard system of referencing Adequate use of Harvard system Good use of Harvard system Comprehensive use of Harvard system in accordance with conventions of AGPS 6 style PRESENTATION OF REPORT (out of 10) 0 0 to 4 5 to 7 8 to 10 4/10 Page Numbering - page numbering to comply with normal conventions (e.g. see Summers & Smith - Communications Skills Handbook) No page numbering at all Incorrect use of page numbering Limited or basic use of page numbering Correct use of page numbering Language Skills - grammar, spelling, clear and concise writing style, correct punctuation Very poor language skills Poor language skills Basic language skills Adequate language skills Good language skills Excellent language skills Word count Significantly over or under nominated word count Slightly over or under word count margins (+/- 10%) Within word count margins * Total Assessment Mark (out of 100) 33/100 Penalties applied to... Marks to be deducted for... Maximum penalty Actual deduction Mark sheet – to be attached to front of assignment No mark sheet 10 Turnitin Report – to be submitted with assignment No Turnitin originality report (mark of 1/100 allocated until report submitted) 10 ** Total Deducted Mark (TDM) 0 Overall Results * Total Assessment Mark (TAM) 33 ** Total Deducted Mark (TDM) 0 Final Assignment Mark = TAM – TDM (capped at 1/100 until Turnitin originality report received) 33 Comments and feedback from Marker: • Attention is needed to this essay. The assignment requirements were to evaluate the project’s business case, its importance, contents and how it improves the project outcomes. Your discussion focuses on the implementation of the project itself rather than the business case. A suggested methodology would be do undertake a concise theoretical evaluation of the purpose of a business case and its contents. After developing this, describe what is contained in your business case and include brief examples. After this comes analysis by comparing theory with what is contained in the business case highlighting what was done well, what was not done well and opportunities for improvement. Findings then become the conclusions and recommendations. As mentioned previously however, the focus must be on the business case. o Considerable attention is needed to the grammar, referencing style, format and set out. Refer to the Communication Skills Handbook, Assignment Guidelines, Assignment Requirements and the Harvard Referencing System. o Provide page numbers. o Use 12 point font. Use 1½ times line spacing. Refer to the Assignment Guidelines. o Provide an additional line break between paragraphs. It provides a definite break between paragraphs and is far easier to read. o There are many large paragraphs. Try to break them into several smaller ones. It is much easier to read and more visually appealing. o Not all references cited in the essay are included in the List of References. RB The balance of this page should be left blank. Please start or attach your assignment on the following page (which has been separated by a section break) Make sure your formatting matches the formatting of the mark sheet Introduction: The essay is focused on providing the information regarding the project called business process management or BPM system. The complete process of using the information system and information technology for supporting the business processes by developing some kind of technology that can operate in entire or segment of the organisation is called business process management system development (Jeston and Nelis 2014). The business process management system is the technology that is effective in enhancing the workflow of an organisation. The essay describes various aspects of implementing the business process management system within the Dutch social insurance organisation. The project had been carried out in two stages. The Prince2 project management methodology had been utilised for carrying out the project. The project is carried out in the financial industry. The number of stakeholders of the project are four thousand and six hundred in two phases total. The budget of the project was approximately 2 million dollar. The essay compares the techniques described in the case study with the information that has been gleaned from other sources. The link between the activities associated with user participation and outcome of the BPM project has been discussed in short. The Description of the Project: The main activity of the organisation is executing the employee insurances that is a semi-public job. Dutch Social Insurance Organization is an agency that drives independent policy and only reports to Social Affairs department that resides under Dutch Ministry. According to Waal and Batenburg (2014), the project was completed in two phases. The first activity was defining and designing the business process management system. The realisation and design of the second stage of the system were done followed by the implementation and realisation of the first stage of the system. The second stage of the implementation was done at the second stage of the project which included the utilisation of the updates of the business process management system. Business Process Management structure was provided, essentially planned for streamlining the centre imposing processes associated with the administration controlled rules within the instances partition and developed the environment for implementation to the extent that consistency with tenets and methodology that are essential to an authentic form. BPM structure included of Business Process Managed programming, three distinct business precise interfaces and applications to external databases. The BPM application was arranged and obtained regarding the needs of the suggestions. The service specific programs could be considered as in-house programs from one of the five inimitable open suggestions. In addition, these programs were similarly created manually in terms of the new situation (Waal and Batenburg 2014). Comparison with the Other Projects: Topic Sentence: Requirement gathering phase is also important as the project definition phase. Recommended Best Practice: According to Kerzner (2013), a successful project must be done by concentrating on the requirement gathering the process. The BPM system in the Dutch Social Insurance Organization is done through concentrating on the definition phase. It implies that the selected functionalities have been incorporated into the system successfully, but the possibility of occurring issues because of missing any requirement (functional and non-functional) is high. The most effective way of carrying out a project is by defining it at first and then doing the planning phase, followed by initiation phase. In this way, the project manager can cover all the aspects of the projects (Turner 2016). Comparison to the Literature: Instead of the fact that the projects are done by recording all the movement and resource allocation, the projects are always prone to face challenges. Often the challenges become so severe that the project may lose its true potential. By dividing the project into two sections, the project manager got the opportunity of eliminating the challenges that are inevitable to appear. However, this took so much time in just implementing the system. Walker(2015) suggested that the use of the initiation and planning stages may require more time before the implementation phase but in whole the project members will have a great idea regarding every aspect of the project. Conclusion and Recommendation: Here within the study, the three importance of the planning has been provided. First, proper planning is very effective in gathering all the information required for implementing the project. Second, within the planning phase, the pattern of progressing the project are well defined(Turner 2016). It assists in guiding the project. Third, planning will bound the project decisions so that any decision may not affect the other factors of the project is a way that the project becomes a failure. Topic Sentence: Managing the stakeholder is an effective way to make the project successful. Recommended Best Practice: The stakeholder management must be concerned with the three activities such as making sure that the stakeholders are engaged in each phase of the project, fulfilling the need of the stakeholder and address the solution for the forecasted future problems. The input of the stakeholder management must include Communications Management Plan, Stakeholder Management Plan, Organizational Process Assets and Change-log. The correspondences administration arrange a documentation of stakeholder’s requirements for correspondence necessities (Brucker, Macharis and Verbeke 2013). Comparison to the Literature: The stakeholder engagement in the BPM system implementation project is quite sound. The project required more participants in the second stage than it had in the first stage. In addition to that, the involvement of the stakeholders in the project went up from six hundred to four thousand (Waal and Batenburg 2014). According to Weiss(2016),Each stakeholder needs data for a particular reason, and therefore, the configurations, level of detail, substance and dialect may require some modification from stakeholder to stakeholder. The greater part of this should be mulled over as sources of info while Managing Stakeholder Engagement (Yang and Shen 2014). The output will be notifying the stakeholder regarding the project progress. Making use of the reports that saves the activities of the project. Not only engaging but also managing the stakeholders is very crucial. Waligo, Clarke and Hawkins (2014) stated the stakeholder management into five steps. The first one describes identifying, recognising and acknowledging stakeholders. In this segment, along with defining the requirements of the project, the stakeholders are recognised and solicited. The stakeholders must be able to influence the project and gather importance. Force of a stakeholder regarding impacting heading of the project and results (Meding et al. 2013). A stakeholder delineates a visual portrayal of the different stakeholders (individual and gatherings), their level of intrigue and their significance to the project. It is for the individual utilisation of the project administrator and the administration group (Freeman and Moutchnik2013). It is utilised to recognise the level of bolster at present being gotten by stakeholders and to guide activities to keep up or increment that support. The second activity is analysing contribution, support and commitment. An adequate stakeholder management system is needed to be involved in successfully overseeing stakeholders. The management system should recognise and store the method to deal with taking to provide support and reduce undesirable consequences of stakeholders for the period of the project’s lifespan(Waligo, Clarke and Hawkins 2014). The three crucial choices for the enquiry are duty, assurance and reinforce that is utilised within the stakeholder outline utilised widely for guiding stakeholder management. Developing the action plan is the third part of the stakeholder management activity (Freeman and Moutchnik2013). A stakeholder examination is utilised by business pioneers and project supervisors to distinguish the key influencers associated with a particular program or project then investigate their condition of concentration, the degree of secrecy and the consequence they add to it (Yang and Shen 2014). This learning assists the program for interfacing within the fine stroute with stakeholders, exclusively in positioning supreme master active communication. The ID of any hindrances to the complete stakeholders 'assurance and accountability is the preliminary transfer concerning personalising any implementations that might assisting evacuating these difficulties. Therefore, it is a proper preparation for recognising any likely interruptions amongst stakeholder investigation with the objective that stakeholders can be contemplated when managing (Freeman and Moutchnik2013). The fourth activity is converting the plan into action. Stakeholder activity plan is gleaned from the stakeholder investigation. The management transfers stakeholders within supplementary ashore situations of bearing by pushing the managed tasks devotedly (Meding et al. 2013). It can integrate communication with stakeholders and maintain them informed on substances that are possibly going to endure some consequence with them, obtaining information from stakeholders that will be relevant regarding the project and handling the requirements of stakeholders. The final job is to keeping track of the outcomes (Waligo, Clarke and Hawkins 2014). The reason for this progression is for occasionally re-surveying the situation of each stakeholder for figuring out the Furthermore activities are necessary for keeping up stakeholder responsibility and sustenance to the project(Johansen, Andresen and Ekambaram 2014). Conclusion and Recommendation: The stakeholders is a crucial part of the project management strategy. Without the support of the stakeholders it is possible to make a project successful. The project manager must be able to handle the requirements of the stakeholder while controlling the project activities. Gaining full support of the stakeholders is the responsibility of the project manager even if the project faces some issues. Topic Sentence: Project management phases define the project effectiveness. Recommended best Practice: In order to make the most of the Prince2 methodology, the methodology must be constructed using seven interconnected phases. In the first phase, starting up the project, the organisation, in this case, Dutch Public Insurance Organization should be examined to make sure that it could support the project. Then the project is directed by the project board. Comparison to the Literature: The BPM implementation in the Dutch Social Insurance Organization was carried out using the Prince2 project management methodology. The project progress was divided into four sections such as initiation, definition & design, realisation and implementation (Waal and Batenburg 2014). Through the initiation phase, project manager set the preparation for the meaning of the project. In the definition and configuration stage two activities were arranged, Business Design and Architecture and Technique. Karaman and Kurt(2015) derived that The project board evaluates the project on the basis of the justification and liabilities. The Business Design extend made utilisation of an authoritative outline approach which concentrated on nine viewpoints that mutually portrayed the current and fancied circumstance (Saadet al. 2014). In the principal occasion, the streams worked freely, in light of cycles of client sessions. The Architecture and Technique project was additionally composed of three streams and concentrated on the demonstrating and format of the BPM framework, the meaning of the database and its coupling to outer frameworks. Amid the client sessions, the deliverables were characterised incrementally to give criticism and approval to the following session. An investigation of and recommendations emerging from the project were examined in the workshops (Tomanek and Juricek 2015). Here, the usefulness, applications and the nature of the execution were surveyed. After three sessions, the streams were united. Then the project is initiated. The project manager divides the project activities into smallest and relevant jobs within the initiation phase. Managing the product delivery is not mandatory for each project. This phase is included into the project by examining the outputs of the project. In terms of keeping the project activities within a specific predefined boundary, the project manager must define some parameter regarding each project action. This whole process is done by managing the project boundary. At last, the project is closed, and the developed system is incorporated within the organisation environment (Karaman and Kurt 2015). Conclusion and Recommendation: The project could have been completed with more accuracy and properly if the earlier mentioned activities were done. By dividing the project activities into adequate smallest possible parts, the project manger can clearly define the activities. This will allow the team to understand the scope of the work easily. Conclusion: Within this essay, the in-depth analysis of the BPM system project along with the comparison of its segments has been presented. The business process management system must be adequate for supporting the business goals of the organisation. The functionality of the system is linked with the core processes of the organisation, and thus it must maintain non-functional requirements like accuracy and availability all the time. A project can be carried out in a various way. The nature of the project and expectations from the system takes a huge part in the project methodology selection activity. However, some of the activities like, requirement gathering, testing, documentation must be included no matter what Information System Project it is. The Prince 2 is a hard project management methodology to adopt within the projects. This made the BPM system implementation project more complex. As the concerned project was huge in size, the project manager got away by applying the concept of Prince 2 methodology. The above study successfully included that user participation activities are tightly associated with the business process management system outcomes. The stakeholders are one of the strongest parts of a project. The participation of the stakeholders is essential for carrying out the project successfully.   Reference List: De Brucker, K., Macharis, C. and Verbeke, A., 2013. Multi-criteria analysis and the resolution of sustainable development dilemmas: A stakeholder management approach. European journal of operational research, 224(1), pp.122-131. Dorigo, L. and Marcon, G., 2014. A Caring Interpretation of Stakeholder Management for the Social Enterprise: Evidence from a Regional Survey of Micro Social Co-Operatives in the Italian Welfare Mix. Freeman, E. and Moutchnik, A., 2013. Stakeholder management and CSR: questions and answers. uwf UmweltWirtschaftsForum, 21(1-2), pp.5-9. Jeston, J. and Nelis, J., 2014. Business process management. Routledge. Johansen, A., Eik-Andresen, P. and Ekambaram, A., 2014. Stakeholder benefit assessment–Project success through management of stakeholders. Procedia-Social and Behavioral Sciences, 119, pp.581-590. Karaman, E. and Kurt, M., 2015. Comparison of project management methodologies: prince 2 versus PMBOK for it projects. International Journal of Applied Science and Engineering Research, 4(4), pp.572-579. Kerzner, H., 2013. Project management: a systems approach to planning, scheduling, and controlling. John Wiley & Sons. ME de Waal, B. and Batenburg, R., 2014. The process and structure of user participation: a BPM system implementation case study. Business Process Management Journal, 20(1), pp.107-128. Saad, S., Ibrahim, A., Asma, O., Khan, M.S. and Akhter, J., 2014. PRINCE2 MEthodology: AN INNovAtIvE WAy foR IMPRovINg PERfoRMANCE of MAlAysIAN AutoMotIvE INdustRy. The Journal of Technology Management and Technopreneurship (JTMT), 1(1). Tomanek, M. and Juricek, J., 2015. Project risk management model based on PRINCE2 and SCRUM frameworks. arXiv preprint arXiv:1502.03595. Turner, R., 2016. Gower handbook of project management. Routledge. Von Meding, J., McAllister, K., Oyedele, L. and Kelly, K., 2013. A framework for stakeholder management and corporate culture. Built Environment Project and Asset Management, 3(1), pp.24-41. Waligo, V.M., Clarke, J. and Hawkins, R., 2014. The ‘leadership–stakeholder involvement capacity’nexus in stakeholder management. Journal of Business Research, 67(7), pp.1342-1352. Walker, A., 2015. Project management in construction. John Wiley & Sons. Weiss, J.W., 2016. Business Ethics: A Stakeholder & Issues Management Approach, 2014. Cyrus Chronicle Journal, 1(1), pp.66-69. Yang, R.J. and Shen, G.Q., 2014. Framework for stakeholder management in construction projects. Journal of Management in Engineering, 31(4), p.04014064. Ziemba, E. and Kolasa, I., 2015. Risk factors framework for information systems projects in public organizations-insight from Poland. In Computer Science and Information Systems (FedCSIS), 2015 Federated Conference on (pp. 1575-1583). IEEE.