MIS604_Assessment_3_Brief_Agile Requirements Analysis & Management Report_Module Due6.1 Page 2 of...

Question

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 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 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 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 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.

Ankit · Accepted Answer

Agile Requirements Analysis & Management Report 
                                             INTRODUCTION
In this report it is all about agile requirement analysis and its management report. it is simple guidelines in software development Which is interaction between client and developer as their customer feedback their collaboration their working task and feedback.
When we are doing requirement analysis it is all about what the customer wants in their application soon they are mentioning it as story points so any developer and tester can understand what is the requirement all about. In the story points it's mentioned that what are the time required to complete the particular story end how much time it will take to complete and what is the status of the different story points which is seen by the team, scrum Masters as well as the product owner
In the body you will the different story point and about the product backlog of the application.
                                        BODY OF THE PROJECT
This application is all about to ensure that organisations can call on students, in short notice, to fulfil their short-term vacancies/ needs for specific skills. So we are planning to develop a web and mobile application for this. This application should allow organisations that require short term assistance to register for the service online to source students with the appropriate skills. The company will be funded by a pro rata commission charged per hours worked by each student.
The lack of requirements lifecycle in a project can lead to major loopholes in the project. There can be risks of scope creep in the project as the requirements coverage may not be proper and the scope of the project may not be defined properly as an outcome. The lack of coverage, inability to incorporate the requirements, and the overall gap in managing requirements lifecycle can have negative impacts on the project objectives and successful outcomes.  The main actors involved in this system ate students and Employees. Students are the main actor of this application, where they can have permit to login and create their profile based on their skills and the location where they can work. They can contact to find out more about job. Similarly, Employees of Student Gigz Ptv Ltd can hire students and sign all contracts and agreements. Likewise, they can rate and review student’s profile as well as they can recommend to students with specific experiences. Additionally, they can send job alters and contact to students via message broadcast regarding students’ availability. 
                                                Business Requirement 
The main purpose of this report is to develop insights on two specific areas – requirements documentation and requirements lifecycle management. So, the body of this report will illustrate requirement analysis, documentation and importance of requirements lifecycle management, process, and traceability matrix to manage the requirements. they can rate and review student’s profile as well as they can recommend to students with specific experiences. Additionally, they can send job alters and contact to students via message broadcast regarding students’ availability. The application of Student Gigz company must include following functional requirements .It is recommended that the requirements lifecycle management is carried out using effective tools and mechanisms. For example, the use of surveys, interviews, and observations shall be used as the techniques to collect the information so that proper identification of the requirements is possible. Similarly, analytical tools shall be used to analyse the requirements and the status.   It is also recommended that due to increase in hackers around the world, the authentication steps should be considered very carefully as it may lead to big loss in terms of financially and identification.
The system should show information’s on how students can login and interact with the web application. Example- Email login, Password options.

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...

Answer To: MIS604_Assessment_3_Brief_Agile Requirements Analysis & Management Report_Module Due6.1 Page 2 of...

Answer To This Question Is Available To Download

Related Questions & Answers

Submit New Assignment