Reference no: EM133580404 , Length: word count:2000
Requirement Engineering
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 Instructions
Please read the given case study and make assumption wherever needed
Based on the given case study, you are required to write a 2000 (+/- 10%) words Agile Requirements Analysis & Management Report.
Review your subject notes to establish the relevant area of investigation that applies to the case. Re-read any relevant readings. Perform additional research and investigation to add depth to your understanding.
Plan how you will structure your ideas for your report and write a report plan before you start writing.
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:
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 two specific areas reflecting the given case study:
Product vision for the project
A Product Roadmap, which includes main product features over releases and timelines of the project
Product Backlog including Epics and User stories (minimum ten (10) entry). Following is an example format to create the product backlog:
Story Mapping for the project - ordering User stories according to priority and sophistication
Two (02) Personas who typifies the future system end users or major stakeholders
For the first release, identify the epics and user stories from the product backlog (identified in the previous question (c)).
Decomposition of two (02) Epics into number of User stories selected for the first release (identified in the previous question (f)).
Story elaboration and Acceptance Criteria of five (05) User stories for the first release to ensure that the User story is clear and the ‘definition of done'.
Describe, how the mindset and role of a Business Analyst (BA) need to be changed while
transitioning from ‘Waterfall' to ‘Agile' requirement engineering practice.
The conclusion (100-150 words) will summarise any findings or recommendations that the report puts forward regarding the concepts covered in the report.
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.
Diagrams and tables must carry the appropriate captioning (numbering, name, and source).
If diagrams or tables are used, please follow APA 7 guideline for the same.