|ASSESSMENT 2 BRIEF|
|Subject Code and Title||MIS100 – Foundations of Information Systems|
|Length||2500 words (+/- 10%)|
|Learning Outcomes||The Subject Learning Outcomes demonstrated by successful completion of the task below include:|
- Analyse and synthesise organisational requirements and recommend a number of tested and verifiable solutions to address organisational needs.
- Communicate a collaborative strategy which embodies the principles of agile methodology to address complex organisational needs by incorporating different information technologies.
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.
- 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:
- Simulate a mini-agile project to allow you to build knowledge of the process via experiential learning.
- Allow you to explore the concepts associated with implementing an Enterprise Resource Planning Systems and offer solutions to a simulated organisation.
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.
- Please read the attached MIS100_Assessment 2_Case Scenario.
- 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.
- 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:
- Title page
- 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:
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:
- Your area of research and its context
- The key concepts you will be addressing
- 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:
- What are the major objectives of an ERP system and how are they similar or different to a Functional Area Information System?
- What are they benefits and limitations of ERP systems?
- 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?
- 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?
- 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 report.
Please include the following documents in the appendices:
Content of scrum board 1 Content of scrum board 2
Presentation script (2 pages max) along with the PowerPoint Slides
Report Format and Layout
- 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.
- 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.