Reference no: EM133034431 , Length: word count:2000
MIS604 Requirements Engineering - Laureate International Universities
Assessment - Agile Requirements Analysis and Management Report
Learning Outcome 1: Demonstrate methods for eliciting, analysing, documenting, and maintaining requirements in an organisational context.
Learning Outcome 2: Synthesise key principles of requirements management and communicate to stakeholders in order to solve problems.
Learning Outcome 3: Evaluate organisational requirements to maximise effectiveness and promote sustainable business practices.
Task Summary
This final assessment requires you to respond to the given case study used in Assessment 1 and 2, so that you can develop insights into the different facets of Requirements Analysis in agile. In this assessment you are required to produce an individual report of 2000 words (+/-10%) detailing the following:
1. A Product Roadmap for the project
2. Product Backlog of coarse granularity including Epics and User stories
3. Personas who typifies the future system end user
4. Decomposition of Epics into User stories for first release
5. Minimum Viable Product (MVP) definition for first release
6. Story Mapping for MVP - ordering User stories according to priority and sophistication
7. Story elaboration of User stories for MVP to ensure that the User story is clear, along with the acceptance criteria for the elaborated stories to ensure the ‘definition of done'.
8. A paragraph detailing the similarities and differences between ‘traditional predictive' 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 Business 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 Business 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.
Task Instructions
1. Please read the 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.
4. Perform additional research and investigation and select five additional sources in the field of agile requirement specification, analysis, and management to add depth to your explanation of method selection.
5. Plan how you will structure your ideas for your report and write a report plan before you start writing.
6. The report DOES NOT require an executive summary or abstract.
7. Structure of the Report
- A professional custom title page with the subject code and subject name, assignment title,
student's name, student number and lecturer's name
- Table of contents
- 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:
o Overview of the problem you've been asked to research
o The key concepts you will be addressing,
o 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 two specific areas reflecting the given case study:
o A Product Roadmap, which includes releases and timelines of the project
o Product Backlog of coarse granularity including Epics and User stories. Use the following format to create the product backlog.
o Two (02) Personas who typifies the future system end users or major stakeholders
o Decomposition of two (02) Epics into User stories for first release
o Minimum Viable Product (MVP) definition for first release
o Story Mapping for MVP - ordering User stories according to priority and sophistication
o Story elaboration of five (05) User stories for MVP to ensure that the User story is clear, along with the acceptance criteria for the elaborated stories to ensure the ‘definition of done'.
o A paragraph detailing the similarities and differences between ‘traditional predictive' 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.
- Reference list
- Appendix (if required)
Attachment:- Requirements Engineering.rar