Agile Requirements Analysis | My Assignment Tutor

Agile Requirements Analysis & Management ReportTask SummaryThis final assessment requires you to respond to the case study used in Assessment 1 and 2 so thatyou candevelop insights into the different facets of Requirements Analysis. In this assessment youare 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 stories2. A Persona who typifies the future system end user3. Decomposition of an Epic in user stories for first release4. Story Mapping – ordering user stories according priority and sophistication5. Minimum Viable Product definition for first release6. Story elaboration of the stories for MVP to ensure that the User Story is clear7. Well considered acceptance criteria for the stories to ensure that ‘definition of done’ isclear to allstakeholders.8. A paragraph detailing the similarities and differences between traditional predictiverequirementsanalysis and management and Agile requirements analysis and management.Please refer to the Task Instructions for details on how to complete this task.ContextIn the second assessment you would have developed capability in the areas of requirements analysisand requirements lifecycle management, which are well recognised Business Analysis skills andcapabilities. However, Agile has become a recognised software development approach which is bothadaptive and iterative in nature. This has necessitated the development of new and differentiatedrequirements analysis and management skills, techniques, and capabilities. This assessment aims toassist you in developing well-rounded skills as a Business Analyst who uses a spectrum tools andtechniques. In doing so, you can draw irrespective of the approach your future employer may take tosoftware development.Task Instructions1. Please read attached Assessment_Case Study.2. Write a 2000 words Agile Requirements Analysis & Management Report as a response tothe casestudy provided.3. Review your subject notes to establish the relevant area of investigation that applies to thecase. 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 ofelicitation methods to add depth to your explanation of method selection. Plan how you willstructureyour 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’sname, student number and lecturer’s nameAn introduction (100-150 words) which will also serve as your statement of purpose for thereport –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 reportThe 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 Epicsand userstories 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 clearto all stakeholders. A paragraph detailing the similarities and differences between traditional predictiverequirements analysis and management and Agile requirements analysis andmanagement.The conclusion (100-150 words) will summarise any findings or recommendations that thereportputs 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 ofreading and page numbers on the bottom of each page. If diagrams or tables are used, dueattention should be given to pagination to avoid loss of meaning and continuity byunnecessarily splitting information over two pages. Diagrams must carry the appropriatecaptioning.Must do: –Visual appeal and presentation of contentTitle page Font, spacing and format are in accordance assignmentrequirements. Appropriate use of paragraphs, sentence construction, spelling and grammar. Adheres to thewordcount requirementKnowledge and understanding Product Roadmap and the Product Backlog Epics, User stories, storydecomposition and story elaboration. Story mapping and Minimum Viable Product, Comparison betweenAgile and traditional requirements analysisand managementUse of academic and discipline conventions Formal tone Introduction, body and conclusion. No use of firstparty perspective Appropriate use of credible resources, Correct citation of key resources using APA style ofreferencing, in-text as well as for models, diagrams, tables or tools.

QUALITY: 100% ORIGINAL PAPER – NO PLAGIARISM – CUSTOM PAPER

Leave a Reply

Your email address will not be published. Required fields are marked *