Reliable MIS100 Foundations of Information Systems Assignment Help From Trusted Professionals Experts

 

ASSESSMENT 2 BRIEF

Subject Code and Title

MIS100 – Foundations of Information Systems

Assessment

Solution Plan

Individual/Group

Group

Length

2500 words (+/- 10%)

Learning Outcomes

The Subject Learning Outcomes demonstrated by successful completion of the task below include:

b)  Analyse and synthesise organisational requirements and recommend a number of tested and verifiable solutions to address organisational needs.

c) Communicate a collaborative strategy which embodies the principles of agile methodology to address complex organisational needs by incorporating different information technologies.

Submission

Due by 11:55pm AEST Sunday end of Module 4.1 (Week 7).

Weighting

40%

Total Marks

100


Task Summary

This group assignment is an agile project focusing on the topic of Enterprise Resource Planning Systems, where the group will use agile techniques to produce a final report of 2500 words outlining a solution plan. In the process of developing the final report, each group will first prepare a team contract, prepare two scrum boards and a short presentation as part of their weekly learning activities in Module 1. Each of these learning activities will provide evidence of the agile process the team has followed to research, develop and deliver the final report.

Context

·         Agile project management is rapidly emerging as a commonly used project management methodology in contemporary IT departments. The main aim of this assessment is to develop an iterative and incremental approach to achieve better project outcomes.

·         Scrum is one of the agile project methodologies which aims to ensure that the team works together with regular ‘check-ins’.

·         Short time boxes – in this case weekly – are used to break the tasks that need to be completed into bite-sized components to ensure incremental delivery and to avoid a ‘crunch’ on resources at the final points of delivery.

·         This assessment is prescribed to achieve two things:

o    Simulate a mini-agile project to allow you to build knowledge of the process via experiential learning.

o    Allow you to explore the concepts associated with implementing an Enterprise Resource Planning Systems and offer solutions to a simulated organisation.

Task Instructions

Team Formation and Registration

·         Form teams of 3-4 members.

·         The deadline for team registration is 11:45pm AEST Friday end of Module 1.2 (Week 2).

·         To register your team, you are required to send your Learning Facilitator an email with “[MIS100] Team Registration” in the subject line. In the body of that email, please list the names and student ID numbers of all the members of your team.

·         You are required to send the registration email to your facilitator before the registration deadline.

·         After the registration deadline, those students who are not in a team will be allocated to a team by the Learning Facilitator. 

Case Scenario

·         Please read the attached MIS100_Assessment 2_Case Scenario.

Team Contract 

·         Please read the attached MIS100_Assessment 2_Team Contract.

·         Each team is required to complete their team contract as part of the learning activity for

Module 2.1 (Week 3) Scrum Boards

·         Each group is required to complete scrum boards as part of learning activities for Module

2.2 (Week 4) and Module 3.1 (Week 5).

·         You will receive feedback from your Learning Facilitator for each of these scrum board learning activities. It is expected that your group take this feedback into consideration when writing the final report. 

Presentation

·         Each group is required to conduct a presentation consisting of 5 slides during Module 3.1 (Week 6) as part of the weekly learning activities.

·         The five slides of the group presentation should include:

1.      Title page

2.      Introduction

3.      Background

4.      Recommendations

5.      Conclusion


·         You will receive feedback from your Learning Facilitator for the Presentation learning activity. It is expected that your group take this feedback into consideration when writing the final report.

Final Group Report

Please write a 2500 words group report following the structure outlined below:

Title page

Should include the subject code and subject name, assignment title, all student’s names and student numbers in the group and the Learning Facilitator’s name.

Executive summary: While this report is brief – it will require an Executive Summary, which does not form part of the overall word count.

Introduction (300-350 words): will also serve as your statement of purpose for the report. This means that you will tell the reader what you are going to cover in your report. You will need to inform the reader of:

a.      Your area of research and its context

b.      The key concepts you will be addressing

c.       What the reader can expect to find in the body of the report

Body of the report (1800 – 2000 words): will need to respond to the specific requirements of the case scenario. The areas you will be required to cover are:

a.      What are the major objectives of an ERP system and how are they similar or different to a Functional Area Information System?

b.      What are they benefits and limitations of ERP systems?

c.       What are the core modules of an ERP systems and what would the extended modules be? Which module would you recommend first for implementation and why?

d.      What are the different available implementation models that the business can consider for their ERP implementation and the benefits and drawbacks of these different implementation models? Which would you recommend?

e.      Which functional departments are likely to be impacted in the business as they transition to a world where ERP supports cross-functional and cross-departmental processes? 

The conclusion (300-350 words): will summarise any findings or recommendations that the report puts forward regarding the concepts covered in the reports.

Appendices

Please include the following documents in the appendices:

Team contract

Content of scrum board 1 Content of scrum board 2

Presentation script (2 pages max) along with the PowerPoint Slides 

Report Format and Layout

a.      The report should use font Arial or Calibri 11 point, should be line spaced at 1.5 for ease of reading and page numbers on the bottom of each page.

b.      If diagrams or tables are used, due attention should be given to pagination to avoid loss of meaning and continuity by unnecessarily splitting information over two pages. Diagrams must carry the appropriate captioning.

Referencing

There are requirements for referencing this report using APA referencing style. Please see more information on referencing here 

a.      It is expected that you reference any lecture notes used and five additional academic sources in the relevant subject area based on readings and further research.

b.      You are strongly advised to read the rubric, which is an evaluation guide with criteria for grading the assignment. This rubric will give you a clear picture of what a successful report looks like.

Submission Instructions

Please submit ONE MSWord document (.doc or .docx) via the Assessment 2 section found in the main navigation menu of the subject’s Blackboard site. The Learning Facilitator will provide feedback via the Grade Centre in the LMS portal. Feedback can be viewed in My Grades.

Academic Integrity Declaration

We declare that except where we have referenced, the work we are submitting for this assessment task is our own work. We have read and are aware of Torrens University Australia Academic Integrity Policy and Procedure viewable online at

We are aware that we need to keep a copy of all submitted material and their drafts, and we will do so accordingly.

Assessment Rubric - Report

 

Assessment Attributes

Fail

(Yet to achieve minimum standard)

0-49%

Pass (Functional) 50-64%

Credit (Proficient) 65-74%

Distinction (Advanced) 75-84%

High Distinction (Exceptional) 85-100%

REPORT - Visual appeal and presentation of content

 

Title page

 

Font, spacing and format are in accordance with the requirements of the assessment brief

 

Appropriate use of paragraphs, sentence construction, spelling and grammar

 

Adheres to the word count requirement

 

15%

·         No title page is included.

 

·         Incorrect font and size is used with poor line spacing and large gaps in pagination or tables or diagrams run over onto the next page unnecessarily.

 

·         Report is written as a block of text with no breaks in between ideas. Separate ideas cannot be clearly discerned.

 

·         Many errors in spelling or grammar obscure meaning of what student has written.

 

·         Does not adhere to the word count requirement of 2500

·         Title page is included but is missing most information.

 

·         Either incorrect font and size is used or poor line spacing and large gaps in pagination.

 

·         Paragraphs are used but large blocks of text with long sentences make it difficult to understand the ideas being conveyed.

 

·         Spelling or grammar has errors but meaning remains clear.

 

·         Does not adheres to the word count requirement of 2500 words (+/- 20%).

·         Title page is included but is missing key information.

 

·         Some errors in font use and line spacing. Some pagination problems.

 

·         One idea or concept per paragraph. Some paragraphs could be more succinctly written.

 

·         Minor spelling or grammar errors.

 

·         Adheres to the word count requirement of 2500 words (+/- 10%)

·         Title page is included with most required information.

 

·         Minor errors in font, spacing and format.

 

·         One idea or concept per paragraph with 3-4 well constructed sentences per paragraph.

 

·         No errors in spelling or grammar.

 

·         Adheres to the word count requirement of 2500 words (+/- 10%).

·         Title page is included with all required information.

 

·         Font, spacing and format are in accordance with the requirements of the assignment brief.

 

·         Expert use of paragraphs with 3-4 well constructed sentences per paragraph which follow logically from each other.

 

·         No errors in spelling or grammar.

 

·         Adheres to the word count requirement of 2500 words (+/- 5%).

 
 

 

words (greater than

+/- 20%).

 

 

 

 

 

REPORT –

Knowledge and understanding of Enterprise Resource Planning Systems

 

Objectives

 

Benefits and limitations

 

Functional areas of impact in the business

 

20%

 

Demonstrates a partially developed understanding of Enterprise Resource Planning Systems by describing incomplete elements of the objectives, benefits and limitations, and functional areas of impact to the business of ERP systems.

 

Demonstrates a functional knowledge of Enterprise Resource Planning Systems by describing:

·         The objectives

·         Benefits and limitations

·         Functional areas of impact of

ERP systems

 

Demonstrates proficient knowledge of Enterprise Resource Planning Systems by describing

·         The objectives

·         Benefits and limitations

·         Functional areas of impact of

ERP systems

 

Some additional examples are referenced based on additional research.

 

Demonstrates advanced knowledge of Enterprise Resource Planning Systems by

·         The objectives

·         Benefits and limitations

·         Functional areas of impact of

ERP systems

 

Additional examples are used that are relevant to the business as described in the case scenario

 

Demonstrates exceptional knowledge of Enterprise Resource Planning Systems by

·         The objectives

·         Benefits and limitations

·         Functional areas of impact of

ERP systems

 

Highly relevant examples have been identified via further research, which demonstrate the development and in-depth understanding of the case scenario.

 

REPORT –

Analysis and application with synthesis of new knowledge

 

Core and extended modules

 

Implementation models

 

20%

 

Limited synthesis and analysis.

 

Limited recommendations based upon analysis.

 

Demonstrated analysis and synthesis of new knowledge with application.

 

Shows the ability to interpret relevant information and literature from more than one source.

 

Well-developed analysis and synthesis with application of recommendations linked to analysis/synthesis.

 

Thoroughly developed and creative analysis and synthesis with application of pretested models and / or independently developed models and justified recommendations linked to analysis/synthesis.

 

Highly sophisticated and creative analysis, synthesis of new with existing knowledge.

 

Recommendations are clearly justified based on the analysis and synthesis of the knowledge of Enterprise Resource Planning Systems and the

cases.

 

 

 

 

 

 

REPORT –

Use of academic and discipline conventions

 

Formal tone

 

Meets the assignment brief regarding introduction, body and conclusion.

 

No use of first party perspective

 

 

Appropriate use of credible resources; correct citation of key resources using APA style of referencing

 

15%

·         Poorly written with informal tone, using first person pronouns (I, my, we, me, us) and does not adhere to the assessment brief of the requirements for a short business report.

 

·         No introduction attempted.

 

·         Conclusion not attempted.

 

·         Demonstrates inconsistent and inadequate use of good quality, credible and relevant resources to support and develop ideas.

 

·         No use of in-text references, or no reference list at the close of the report. There are many mistakes in using the APA style.

·         Written according to academic genre as per the assessment brief. Minor errors in the use of first-person pronouns (I, my, we, me, us).

 

·         Introduction attempted but very generic does not clearly state the purpose of the report and what the reader should expect to find in the body of the report.

 

·         Conclusion attempted but does not include summation of key concepts discussed in the report and/or key conclusions or recommendations.

 

·         Demonstrates consistent use of credible and relevant research sources to support and develop ideas, but these are not always explicit or well developed.

 

·         Little use of in-text referencing, or

inadequate references

·         Written according to academic genre as per the assessment brief.

 

·         Demonstrates consistent use of credible and relevant research sources to support and develop ideas.

 

·         Sound use of the introduction but does not clearly state either the purpose of the report or what the reader should expect to find in the body of the report.

 

·         Sound use of the conclusion and succeeds in either the summation of key concepts discussed, or key conclusions or recommendations, but not both.

 

·         Good use of in-text referencing and appropriate number of references used and

listed in the reference

·         Well-written and adheres to the academic genre as per the assessment brief.

 

·         Consistently demonstrates expert use of good quality, credible and relevant research sources to support and develop appropriate arguments and statements. Shows evidence of reading beyond the key reading.

 

·         Good use of the introduction which clearly states the purpose of the report and what the reader should expect to find in the body of the report.

 

·         Good use of the conclusion and succeeds in summation of key concepts discussed and key conclusions or recommendations.

·         Expertly written and adheres to the academic genre as per the assessment brief.

 

·         Demonstrates expert use of high-quality credible and relevant research sources to support and develop arguments and position statements. Shows extensive evidence of reading beyond the key reading.

 

·         Excellent use of the introduction, which secures the attention of the reader, clearly states the purpose of the report and what the reader should expect to find in the body of the report.

 

·         Excellent use of the conclusion, which succeeds in confident summation of key concepts and conclusions and gives

the reader a clear

 

 

consulted and added to references at the close of the report. There are some mistakes in using APA style.

list. There are only minor errors in using the APA style.

·         Very good use of in- text referencing. All in- text references match with references listed in the reference list. There are no mistakes in using the APA style.

sense of next steps required.

 

·         Excellent and meticulous use of in- text referencing with all in-text references matching with references listed in the reference list. There are no mistakes in using the APA style.

TEAM CONTRACT

 

 

10%

·         No team contract submitted

·         Team contract submitted but missing some or all elements in the contract regarding: ground rules, team goals, project plan, team roles, meeting schedule, decision- making process and team expectations

·         Team contract submitted but ground rules, team goals, project plan, team roles, meeting schedule, decision- making process and team expectations are completed in a perfunctory manner simply to complete the task.

·         Team contract submitted ground rules, team goals, project plan, team roles, meeting schedule, decision- making process and team expectations are completed but could offer greater depth of insight into what is required for the group to succeed.

·         Team contract submitted and well- developed to set expectations for a high-functioning and successful team project.

SCRUM 1

 

Content of Scrum Board, presentation and teamwork

·         Scrum Board is not presented, team is unprepared.

·         Scrum board is completed; however, insufficient consideration has been given to items on the scrum board.

·         Scrum board is complete and there is evidence that the team have applied effort, but further work needs to be done to improve technique

·         Scrum board is complete and shows that the team have a good grasp on what items are waiting in their backlog and are making headway in

·         Scrum board is complete and reflects that the team is progressing well with their project with all team members actively engaged in

collaborative activity.

 

 

 

 

 

5%

 

·         Stilted, awkward and/or oversimplified delivery.

 

·         Limited use of engaging presentation techniques. (e.g. posture; eye contact; gestures; volume, pitch and pace of voice)

 

·         All of team not in attendance

 

·         Correct, but often stilted or awkward delivery.

 

·         Sometimes uses engaging presentation techniques (e.g. posture; eye contact; gestures; volume, pitch and pace of voice)

 

·         Team in attendance but lack of team preparation and collaboration is clear.

 

·         Correct, but occasionally stilted or awkward delivery.

 

·         Uses engaging presentation techniques (e.g. posture; eye contact; gestures; volume, pitch and pace of voice)

 

·         Team all present soundly but there is evidence of a lack of team insight into other team members’ areas.

getting items completed.

·         Clear and confident delivery.

 

·         Confidently and consistently uses a range of engaging presentation techniques (e.g. posture; eye contact, expression; gestures; volume, pitch and pace of voice; stance; movement)

 

·         Team presents soundly and there is evidence of collaboration and continuity.

 

·         Clear, confident and persuasive delivery.

 

·         Dynamic, integrated and professional use of a wide range of engaging presentation techniques (e.g. posture; eye contact, expression; gestures; volume, pitch and pace of voice; stance; movement)

 

·         Team demonstrates an excellent level of collaboration and awareness of their role in the team delivery plan.

SCRUM 2

 

Content of Scrum Board, presentation and teamwork

 

 

 

 

 

 

 

 

5%

·         Scrum Board is not presented, team is unprepared.

 

·         Stilted, awkward and/or oversimplified delivery.

 

·         Limited use of engaging presentation techniques. (e.g. posture; eye contact;

gestures; volume,

·         Scrum board is completed; however, insufficient consideration has been given to items on the scrum board.

 

·         Correct, but often stilted or awkward delivery.

 

·         Sometimes uses engaging presentation techniques (e.g. posture; eye contact; gestures;

·         Scrum board is complete and there is evidence that the team have applied effort, but further work needs to be done to improve technique.

 

·         Correct, but occasionally stilted or awkward delivery.

 

·         Uses engaging presentation

·         Scrum board is complete and shows that the team have a good grasp on what items are waiting in their backlog and are making headway in getting items completed.

 

·         Clear and confident delivery.

·         Scrum board is complete and reflects that the team is progressing well with their project with all team members actively engaged in collaborative activity.

 

·         Clear, confident and persuasive delivery.

 

·         Dynamic, integrated and professional use of

 

pitch and pace of voice)

 

·         All of team not in attendance

volume, pitch and pace of voice)

 

·         Team in attendance but lack of team preparation and collaboration is clear.

techniques (e.g. posture; eye contact; gestures; volume, pitch and pace of voice)

 

·         Team all present soundly but there is evidence of a lack of team insight into other team members’ areas.

·         Confidently and consistently uses a range of engaging presentation techniques (e.g. posture; eye contact, expression; gestures; volume, pitch and pace of voice; stance; movement)

 

·         Team presents soundly and there is evidence of collaboration and continuity.

a wide range of engaging presentation techniques (e.g. posture; eye contact, expression; gestures; volume, pitch and pace of voice; stance; movement)

 

·         Team demonstrates an excellent level of collaboration and awareness of their role in the team delivery plan.

PRESENTATION

 

Effective Communication (Presentation/Oral/ Slides)

 

 

 

 

 

 

 

 

 

10%

·         Difficult to understand for audience, no logical/clear structure, poor flow of ideas, argument lacks supporting evidence.

 

·         Limited use of engaging presentation techniques. (e.g. posture; eye contact; gestures; volume, pitch and pace of voice)

·         Presentation is sometimes difficult to follow. Information, arguments and evidence are presented in a way that is not always clear and logical.

 

·         Sometimes uses engaging presentation techniques (e.g. posture; eye contact; gestures; volume, pitch and pace of voice)

 

·         Employs basic, but generally accurate presentation aids as

directed. Several aspects

·         Presentation is easy to follow. Information, arguments and evidence are well presented, mostly clear flow of ideas and arguments.

 

·         Uses engaging presentation techniques (e.g. posture; eye contact; gestures; volume, pitch and pace of voice)

 

·         Employs clear and somewhat engaging presentation aids as

directed. A few aspects

·         Engages audience interest. Information, arguments and evidence are very well presented; the presentation is logical, clear and well- supported by evidence.

 

·         Confidently and consistently uses a range of engaging presentation techniques (e.g. posture; eye contact, expression; gestures; volume, pitch and pace of voice; stance;

movement)

·         Engages and sustains audience interest. Expertly presented; the presentation is logical, persuasive, and well- supported by evidence, demonstrating a clear flow of ideas and arguments.

 

·         Dynamic, integrated and professional use of a wide range of engaging presentation techniques (e.g. posture; eye contact, expression; gestures; volume, pitch and pace

 

·         Presentation aids are not employed or developed as directed.

require further refinement (e.g. amount of information, styling, editing, etc.).

require further refinement (e.g. amount of information, styling, editing, etc.).

 

·         Employs succinct, styled and engaging presentation aids that incorporate a range of elements (graphics, multi-media, text, charts, etc.).

of voice; stance; movement)

 

·         Employs succinct, creative and engaging presentation aids that effectively integrate a wide range of elements (graphics, multi-media, text, charts, etc.).

 

The following Subject Learning Outcomes are addressed in this assessment

SLO b)

Analyse and synthesise organisational requirements and recommend a number of tested and verifiable solutions to address

organisational needs.

SLO c)

Communicate a collaborative strategy which embodies the principles of agile methodology to address complex organisational

needs by incorporating different information technologies.

Preserve your Top Grade with Online Assignment Help Service 24/7 Know More