MIS604 Requirements Engineering | My Assignment Tutor

MIS604_Assessment_3_Brief_Agile Requirements Analysis & Management Report_Module Due6.1 Page 1 of 5Task SummaryThis final assessment requires you to respond to the case study used in Assessment 1 and 2 so that you candevelop insights into the different facets of Requirements Analysis. In this assessment you are required toproduce 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’ is clear to allstakeholders.8. A paragraph detailing the similarities and differences between traditional predictive requirementsanalysis 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 analysis andrequirements 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 iterativein nature. This has necessitated the development of new and differentiated requirements analysis andmanagement skills, techniques, and capabilities. This assessment aims to assist you in developing well-roundedskills as a Business Analyst who uses a spectrum tools and techniques. In doing so, you can draw irrespectiveof the approach your future employer may take to software development. ASSESSMENT 3 BRIEFSubject Code and TitleMIS604 Requirements EngineeringAssessmentAgile Requirements Analysis & Management ReportIndividual/GroupIndividualLength2000 words (+/- 10%)Learning OutcomesThe Subject Learning Outcomes demonstrated by successful completion ofthe task below include:b) Demonstrate methods for eliciting, analysing, documenting, andmaintaining requirements in an organisational context.c) Synthesise key principles of requirements management andcommunicate to stakeholders in order to solve problems.d) Evaluate organisational requirements to maximise effectivenessand promote sustainable business practices.SubmissionDue by 11:55pm AEST/AEDT Sunday end of Module 6.1Weighting35%Total Marks100 marks MIS604_Assessment_3_Brief_Agile Requirements Analysis & Management Report_Module Due6.1 Page 2 of 5Task Instructions1. Please read attached MIS604_Assessment_Case Study.2. Write a 2000 words Agile Requirements Analysis & Management Report as a response to the casestudy provided.3. Review your subject notes to establish the relevant area of investigation that applies to the case. Reread 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 will structureyour 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 the report –this means that you will tell the reader what you are going to cover in your report. You will need toinform 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 Epics and 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 and management.The conclusion (100-150 words) will summarise any findings or recommendations that the reportputs 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 readingand page numbers on the bottom of each page. If diagrams or tables are used, due attention shouldbe given to pagination to avoid loss of meaning and continuity by unnecessarily splitting informationover 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 theassignment. This will give you a clear picture of what a successful report looks like.ReferencingThere are requirements for referencing this report using APA referencing style and it is expected that studentsreference any lecture notes used and five additional sources in the relevant subject area based on readingsand further research.is essential that you use appropriate APA style for citing and referencing research. Please see moreinformation on referencing here http://library.laureate.net.au/research_skills/referencingMIS604_Assessment_3_Brief_Agile Requirements Analysis & Management Report_Module Due6.1 Page 3 of 5Submission InstructionsSubmit Assessment 3 via the Assessment link in the main navigation menu in MIS604 RequirementEngineering. The Learning Facilitator will provide feedback via the Grade Centre in the LMS portal. Feedbackcan be viewed in My Grades.Academic Integrity DeclarationI declare that except where I have referenced, the work I am submitting for this assessment task is my ownwork. I have read and am aware of Torrens University Australia Academic Integrity Policy and Procedureviewable online at http://www.torrens.edu.au/policies-and-formsI 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 5Assessment Rubric Assessment AttributesFail(Yet to achieve minimumstandard)0-49%Pass(Functional)50-64%Credit(Proficient)65-74%Distinction(Advanced)75-84%High Distinction(Exceptional)85-100%Visual appeal andpresentation of contentTitle pageFont, spacing andformat are inaccordance assignmentrequirements.Appropriate use ofparagraphs, sentenceconstruction, spellingand grammar.Adheres to the wordcount requirement15%No title page is included.Incorrect font and size isused with poor linespacing. Report is writtenas a block of text with nobreaks in between ideas.Separate ideas cannot beclearly discerned. Manyerrors in spelling orgrammar obscuremeaning of what studenthas written. Does notadhere to the word countrequirement.Title page is included but ismissing most information.Either incorrect font and sizeis used or poor line spacing.Paragraphs are used but largeblocks of text with longsentences make it difficult tounderstand the ideas beingconveyed. Spelling orgrammar has errors butmeaning remains clear. Doesnot adheres to the wordcount requirement.Title page is included but ismissing key information.Some errors in font use andline spacing. One idea orconcept per paragraph.Some paragraphs could bemore succinctly written.Minor spelling or grammarerrors. Adheres to the wordcount requirement.Title page is included withmost required information.Minor errors in font,spacing and format. Oneidea or concept perparagraph with 3-4 wellconstructed sentences perparagraph. No errors inspelling or grammar.Adheres to the word countrequirement.Title page is included withall required information.Font, spacing and formatare in accordance theassignment brief. Expertuse of paragraphs with 3-4well constructed sentencesper paragraph which followlogically from each other.No errors in spelling orgrammar. Adheres to theword count requirement.Knowledge andunderstandingProduct Roadmap andthe Product BacklogEpics, User stories, storydecomposition andstory elaboration.Story mapping andMinimum ViableProductLack of understanding ofthe required concepts andknowledge.Key components of theassignment are notaddressed.Lack of application, andanalysis of information toprovide clearrecommendations.Limited understanding ofrequired concepts andknowledge.Some of the key componentsof the assignment are notaddressed.Limited application andanalysis to provide clearrecommendations.Adequate knowledge orunderstanding of therequired concepts. Areasonable capacity toexplain and apply relevantkey concepts.Supports opinion andinformation substantiatedby evidence from researchto providerecommendations.Thorough understanding ofthe key concepts.Discriminates betweenassertion of opinion andinformation substantiatedby robust evidence fromthe research/coursematerials and extendedreading.Well demonstrated capacityto apply and analyseHighly developedunderstanding of the fieldor discipline/s.Systematically and criticallydiscriminates betweenassertion of opinion andinformation substantiatedby robust evidence fromthe research/course MIS604_Assessment_3_Brief_Agile Requirements Analysis & Management Report_Module Due6.1 Page 5 of 5 Comparison betweenAgile and traditionalrequirements analysisand management60%relevant information toprovide clearrecommendations.materials and extendedreading.Recommendations areclearly justified based onthe application and analysisof information.Use of academic anddiscipline conventionsFormal toneIntroduction, body andconclusion.No use of first partyperspectiveAppropriate use ofcredible resources,Correct citation of keyresources using APAstyle of referencing, intext as well as formodels, diagrams,tables or tools.25%Poorly written withinformal tone, using firstperson pronouns. Doesnot adhere to theassignment brief of therequirements for a shortbusiness report. Nointroduction attempted.Conclusion notattempted. Inconsistentand inadequate use ofgood quality, credible andrelevant resources tosupport and developideas. No use of in-textreferences, or noreference list at the closeof the report. Manymistakes in using the APAstyle.Written according toacademic genre. Minorerrors in the use of firstperson pronouns.Introduction attempted butvery generic does not clearlystate the purpose of thereport. Conclusion attemptedbut does not includesummation of key conceptsdiscussed in the reportand/or key conclusions orrecommendations.Consistent use of credibleand relevant researchsources to support anddevelop ideas, but these arenot always explicit or welldeveloped. Little use of intext referencing, orinadequate referencesconsulted and added toreferences at the close of thereport. Some mistakes inusing APA style.Written according toacademic genre. Consistentuse of credible and relevantresearch sources to supportand develop ideas.Sound use of theintroduction but does notclearly state either thepurpose of the report orwhat the reader shouldexpect to find in the bodyof the report. Sound use ofthe conclusion andsucceeds in either thesummation of key conceptsdiscussed, or keyconclusions orrecommendations, but notboth. Good use of in-textreferencing andappropriate number ofreferences used and listedin the reference list. Thereare only minor errors inusing the APA style.Well-written and adheres tothe academic genre. Expertuse of good quality,credible and relevantresearch sources to supportand develop appropriatearguments and statements.Shows evidence of readingbeyond the key reading.Good use of theintroduction which clearlystates the purpose of thereport and what the readershould expect to find in thebody of the report. Gooduse of the conclusion andsucceeds in summation ofkey concepts discussed andkey conclusions orrecommendations.Very good use of in-textreferencing. No mistakesin using the APA style.Expertly written. Adheresto the academic genre.Expert use of high-qualitycredible and relevantresearch sources to supportand develop arguments.Extensive evidence ofreading beyond the keyreading. Excellent use ofthe introduction. Securesthe attention of the reader,clearly states the purposeand what the reader shouldexpect to find in the bodyof the report. Excellent useof the conclusion. Succeedsin confident summation ofkey concepts andconclusions. Gives thereader a clear sense of nextsteps required. Excellentand meticulous use of intext referencing withreferences listed in thereference list. No mistakesin using the APA style.

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

Leave a Reply

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