This final assessment requires you to respond to the case study used in Assessment 1 and 2 so that you can develop insights into the different facets of Requirements Analysis. In this assessment you are required to produce an individual report of 2000 words (+/-10%) detailing the following:

Brief_Agile Requirements Analysis & Management Report

MIS604_Assessment_3_Brief_Agile Requirements Analysis & Management Report_Module Due6.1 Page 1 of 5
Task Summary
This final assessment requires you to respond to the case study used in Assessment 1 and 2 so that you can develop insights into the different facets of Requirements Analysis. In this assessment you are required to produce an individual report of 2000 words (+/-10%) detailing the following:
1. A Product Roadmap and a Product Backlog of coarse granularity including Epics and user stories
2. A Persona who typifies the future system end user
3. Decomposition of an Epic in user stories for first release
4. Story Mapping – ordering user stories according priority and sophistication
5. Minimum Viable Product definition for first release
6. Story elaboration of the stories for MVP to ensure that the User Story is clear
7. Well considered acceptance criteria for the stories to ensure that ‘definition of done’ is clear to all stakeholders.
8. A paragraph detailing the similarities and differences between traditional predictive requirements analysis and management and Agile requirements analysis and management.
Please refer to the Task Instructions for details on how to complete this task.
Context
In the second assessment you would have developed capability in the areas of requirements analysis and requirements lifecycle management, which are well recognised Analysis skills and capabilities. However, Agile has become a recognised software development approach which is both adaptive and iterative in nature. This has necessitated the development of new and differentiated requirements analysis and management skills, techniques, and capabilities. This assessment aims to assist you in developing well-rounded skills as a Analyst who uses a spectrum tools and techniques. In doing so, you can draw irrespective of the approach your future employer may take to software development.
ASSESSMENT 3 BRIEF
Subject Code and Title
MIS604 Requirements Engineering
Assessment
Agile Requirements Analysis & Management Report
Individual/Group
Individual
Length
2000 words (+/- 10%)
Learning Outcomes
The Subject Learning Outcomes demonstrated by successful completion of the task below include:
b) Demonstrate methods for eliciting, analysing, documenting, and maintaining requirements in an organisational context.
c) Synthesise key principles of requirements management and communicate to stakeholders in order to solve problems.
d) Evaluate organisational requirements to maximise effectiveness and promote sustainable business practices.
Submission
Due by 11:55pm AEST/AEDT Sunday end of Module 6.1
Weighting
35%
Total Marks
100 marks
MIS604_Assessment_3_Brief_Agile Requirements Analysis & Management Report_Module Due6.1 Page 2 of 5
Task Instructions
1. Please read attached MIS604_Assessment_Case Study.
2. Write a 2000 words Agile Requirements Analysis & Management Report as a response to the case study provided.
3. Review your subject notes to establish the relevant area of investigation that applies to the case. Re-read any relevant readings for Module 1 and 2 for this subject.
4. Perform additional research and investigation and select five additional sources in the area of elicitation methods to add depth to your explanation of method selection. Plan how you will structure your ideas for your report and write a report plan before you start writing.
5. Please structure the report as follows:
The report does not require an executive summary or abstract.
A professional custom title page with the subject code and subject name, assignment title, student’s name, student number and lecturer’s name
An introduction (100-150 words) which 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:
• Overview of the problem you’ve been asked to research.
• The key concepts you will be addressing,
• What the reader can expect to find in the body of the report
The body of the report (1700-1800 words) will need to cover the following areas:
• A Product Roadmap and a Product Backlog of coarse granularity including Epics and user stories
• A Persona who typifies the future system end user
• Decomposition of an Epic in user stories for first release
• Story Mapping – ordering user stories according priority and sophistication
• Minimum Viable Product definition for first release
• Story elaboration of the stories for MVP to ensure that the User Story is clear
• Well considered acceptance criteria for the stories to ensure that ‘definition of done’ is clear to all stakeholders.
• A paragraph detailing the similarities and differences between traditional predictive requirements analysis and management and Agile requirements analysis and management.
The conclusion (100-150 words) will summarise any findings or recommendations that the report puts forward regarding the concepts covered in the report.
6. 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.
7. You are strongly advised to read the rubric which is an evaluation guide with criteria for grading the assignment. This will give you a clear picture of what a successful report looks like.
Referencing
There are requirements for referencing this report using APA referencing style and it is expected that students reference any lecture notes used and five additional sources in the relevant subject area based on readings and further research.
is essential that you use appropriate APA style for citing and referencing research. Please see more information on referencing here http://library.laureate.net.au/research_skills/referencing
MIS604_Assessment_3_Brief_Agile Requirements Analysis & Management Report_Module Due6.1 Page 3 of 5
Submission Instructions
Submit Assessment 3 via the Assessment link in the main navigation menu in MIS604 Requirement Engineering. The Learning Facilitator will provide feedback via the Grade Centre in the LMS portal. Feedback can be viewed in My Grades.
Academic Integrity Declaration
I declare that except where I have referenced, the work I am submitting for this assessment task is my own work. I have read and am aware of Torrens University Australia Academic Integrity Policy and Procedure viewable online at http://www.torrens.edu.au/policies-and-forms
I am aware that I need to keep a copy of all submitted material and their drafts, and I will do so accordingly.
MIS604_Assessment_3_Brief_Agile Requirements Analysis & Management Report_Module Due6.1 Page 4 of 5
Assessment Rubric
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%
Visual appeal and presentation of content
Title page
Font, spacing and format are in accordance assignment requirements.
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. 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.
Title page is included but is missing most information.
Either incorrect font and size is used or poor line spacing.
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.
Title page is included but is missing key information. Some errors in font use and line spacing. One idea or concept per paragraph. Some paragraphs could be more succinctly written.
Minor spelling or grammar errors. Adheres to the word count requirement.
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.
Title page is included with all required information.
Font, spacing and format are in accordance 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.
Knowledge and understanding
Product Roadmap and the Product Backlog
Epics, User stories, story decomposition and story elaboration.
Story mapping and Minimum Viable Product
Lack of understanding of the required concepts and knowledge.
Key components of the assignment are not addressed.
Lack of application, and analysis of information to provide clear recommendations.
Limited understanding of required concepts and knowledge.
Some of the key components of the assignment are not addressed.
Limited application and analysis to provide clear recommendations.
Adequate knowledge or understanding of the required concepts. A reasonable capacity to explain and apply relevant key concepts.
Supports opinion and information substantiated by evidence from research to provide recommendations.
Thorough understanding of the key concepts.
Discriminates between assertion of opinion and information substantiated by robust evidence from the research/course materials and extended reading.
Well demonstrated capacity to apply and analyse
Highly developed understanding of the field or discipline/s.
Systematically and critically discriminates between assertion of opinion and information substantiated by robust evidence from the research/course
MIS604_Assessment_3_Brief_Agile Requirements Analysis & Management Report_Module Due6.1 Page 5 of 5
Comparison between Agile and traditional requirements analysis and management
60%
relevant information to provide clear recommendations.
materials and extended reading.
Recommendations are clearly justified based on the application and analysis of information.
Use of academic and discipline conventions
Formal tone
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, in-text as well as for models, diagrams, tables or tools.
25%
Poorly written with informal tone, using first person pronouns. Does not adhere to the assignment brief of the requirements for a short business report. No introduction attempted. Conclusion not attempted. 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. Many mistakes in using the APA style.
Written according to academic genre. Minor errors in the use of first-person pronouns.
Introduction attempted but very generic does not clearly state the purpose of the report. Conclusion attempted but does not include summation of key concepts discussed in the report and/or key conclusions or recommendations. 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 consulted and added to references at the close of the report. Some mistakes in using APA style.
Written according to academic genre. 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 list. There are only minor errors in using the APA style.
Well-written and adheres to the academic genre. 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.
Very good use of in-text referencing. No mistakes in using the APA style.
Expertly written. Adheres to the academic genre. Expert use of high-quality credible and relevant research sources to support and develop arguments. Extensive evidence of reading beyond the key reading. Excellent use of the introduction. Secures the attention of the reader, clearly states the purpose and what the reader should expect to find in the body of the report. Excellent use of the conclusion. Succeeds in confident summation of key concepts and conclusions. Gives the reader a clear sense of next steps required. Excellent and meticulous use of in-text referencing with references listed in the reference list. No mistakes in using the APA style.