MIS604 Requirement Engineering Report 3 Sample
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.
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.
.png)
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)
Solution
Introduction:
ABC Pty Ltd is a reputable company in Adelaide Australia, well known for its service. The company is set to launch a program called "ServicePlease" in the next six months to cater to the needs of customers and supermarkets. It will launch both in the application and the website format, and its main purpose is to deliver the products. Customers need to register before availing of this facility. University Assignment Help, They will then be able to select from which supermarket they want to purchase the product, as well as provide customers with the convenience of delivery. This is going to prove to be very useful for consumers and supermarkets.
This report will highlight all the problems related to agile requirement analysis and management and its solutions based on the case study. The goal of this report is to develop efficiently as a business analyst using a spectrum of tools and techniques. This report will be based on a case study and will cover the relationship of the case study with agile analysis and management starting from the product roadmap. This report will also reflect product backlog, user persona and MVP information. The main purpose of presenting this report is to inform the readers about the various requirements of agile analysis. Subject notes will be reviewed to establish the relevant field of investigation applicable to the case study.
Product roadmap:
Based on the aforementioned case study, this report presents an appropriate product roadmap which is as follows. It is very important to draw a product roadmap for ServicePlease online grocery application, it is important for any online e-commerce app (Lombardo et al., 2017).
? First, a customer or buyer must include their email ID and personal information on the ServicePlease website or install the app.
? Then the person has to sign up from a valid mobile number and set up an online payment method using a debit card, credit card, PayPal for online transaction details.
? Then in this step, the customer has to search for the necessary items using a search bar which he or she wants to purchase.
? The next thing to do is to add the products to the cart and take the next step.
? Then the buyer has to set all the details of the online transaction and place the order.
? The service provider accepts the order and payment, they will enlist the help of the delivery boy to deliver the order.
? Proof of delivery must be provided by their driving license and vehicle registration certificate before delivery. If the registration is completed successfully, the provider will be eligible to deliver "ServicePlease" grocery products.
? Once the products listed in the store are packed, the delivery boy will be able to deliver them to the customer.
Figure 1: Product Roadmap
Source: Author
Product backlog: A product backlog refers to feedback from various sources, which includes app developers, business management as well as sales but most importantly, app users (Rødseth & Schjølberg, 2017). It should implement that response, prioritize it, manage it properly as well as work for the future of the product.
The team is working on the essential as well as valuable features to manage the app with the help of this product backlog, fixation of most important bugs, or solving other problems that are important for product development. Thus, backlogs are most effective in situations where it is impossible to answer all the questions or in a context where there is very little planning and a lot of importance.
ServicePlease application development often involves a team of talented professionals, who contribute to each other's goals as well as perform individual tasks efficiently. So, the product backlog lists the most important tasks during the application launch. Here the most important aspects are highlighted during the launch of the software and those tasks are performed first (McGreal & Jocham, 2018). This backlog provides an accurate idea of which aspects of the application need to be changed, in which cases there are defects and what features will be added or have been added.
.png)
Table 1: Product Backlog
Source: Author
User persona: The user personas of the app "ServicePlease" is being launched under the auspices of the company ABC Pty Ltd, helps designers as well as accompany usability testing sessions. An in-depth consideration of user behaviors as well as essential nuances makes it possible to define who a product is being made for and important aspects from a user-centric perspective (Humphrey, 2017). This will allow ABC Pty Ltd company product groups to prioritize product feature requests (features can be implemented or considered as most important on their ability to meet initial personality needs).
? Personas reflect the type of actual user, not the role of the different user. They not only reflect the internal role of a system but also much more (Ritter & Winterbottom, 2017).
? It reflects the current situation of the app.
? The user persona highlights all the targets, goals and plans that are related to the product or application.
? Every aspect of a personality description can be linked to real information through user personality (Szabo, 2017).
While it is easy to define a user attribute and introduce him or her as a persona when launching ABC Pty Ltd's product application, creating such a persona is critical enough to serve as a means of communication and effective design of the app. Based on this case study, customers and suppliers can be mentioned as the two main user personas.
Decomposition of epics: Assigning epics effort estimates is not a very safe job but rather risky. However, since uncertainty is high, ABC Pty Ltd usually requires a schedule and budget, so defining a continuous effort can work as the decomposition process develops. Keep in mind, estimates can never be completely accurate but still, this process can suggest a consistent measure. This model can be started by setting high estimation which decreases the value as the decomposition progresses.
There is no denying the need for Epic to launch applications like ServicePlease in a competitive market. It is characterized by various small user stories. Through these stories, ideas about the needs and useful aspects of the user can be formed (Aguanno & Schibi, 2019). One of the basic thoughts of these epics is that even if it is created during the product roadmap, it is not permanent but it breaks down during product backlog because then many new things have to be added.
Of course, first of all, what is the main purpose of the product or application that AbC Pty Ltd is going to launch, and to act accordingly. Epic user stories allow future users of this app to get ideas about the features and effectiveness of the software. It works primarily with groups, rather than individuals.
Epic and User Stories
.png)
Figure 2: Epic and User Stories
Source: Author
Minimum Viable Product (MVP): A product application with adequate features by a Minimum Viable Product (MVP) can verify the product at the beginning of the app development cycle at the same time to attract customers who initially accept it (Aghnia & Larso, 2018).
In the case of ServicePlease software, MVP can help the product development team get feedback from the users quickly so that the product can be repeated and improved (Nguyen-Duc et al., 2019). Since the agile method is built on user input based on app verification and repetition in the first release, the role of MVP in agile development is undeniable.
AbC Pty Ltd can develop as well as publish the MVP of ServicePlease because its product development team wants:
? To launch a product in the market as soon as possible.
? Before committing to a large budget for the full development of the product to test an idea with actual users.
? To form a clear idea of what resonates with the company's target market and what doesn't.
In addition to allowing AbC Pty Ltd to verify an idea for a product without creating a complete product, an MVP can reduce the time as well as resources that would otherwise be committed to creating a product that would not be successful.
Story mapping for MVP: The user story serves as positive feedback among the recipients in all the sections which can provide benefits to the app developers, app owners and application designers in case of app launch. With the help of user stories, the agile software development team is able to provide advanced development patterns. In this report, the researcher has covered all the issues related to the user story.
Research has shown that this concept of user value points to the advancement of various disciplines as well as plays an important role in design and implementation by prioritizing important decisions.
Who will use the application?
And who will benefit from using this application?
Based on these two questions, user stories show the potential for the growth of the app. In the case study of AbC Pty Ltd, anyone can use the ServicePlease application and purchase grocery items used in their daily life. By using this application, customers will be able to get the required items at home and the suppliers will benefit from it in many ways (Cui & Wu, 2017). In the case study, consideration should be given to running web and mobile applications as a criterion of acceptability. The main objective should be to meet the supply of products according to the needs of the customers who are running this application.
Figure 2: ServicePlease MVP Story Mapping
Source: Author
Traditional predictive and agile:
- Differences:
- Similarities:
1. The focus is on the business approach and the objectives of each growth in both traditional and agile processes (Wysocki, 2019).
2. The business perspective and the purpose of each growth are visible to both.
3. What is important for the needs of each business are explored and strategies are adopted accordingly.
4. Giving a solution to all the needs is not always important but in the case of traditional, the solution is not hindered. The same thing happens with agile.
Conclusion: This report presents all the information related to the product launch of AbC Pty Ltd. The most important aspects of launching a product are highlighted here. The report also discusses product roadmaps, the importance of MVPs ranging from user persona, similarities and differences between agile and traditional requirements. The most effective and possible aspects are described for the development of the app. Needless to say, the story of its users plays a very important role in launching any product. This report also provides information about that. Last but not least, the app should be launched considering all aspects of AbC Pty Ltd. so that the app works successfully and is not interrupted in any way.
Reference List:
Aghnia, M. C., & Larso, D. (2018). Developing new product using minimum viable product. Jurnal Aplikasi Manajemen, 16(2), 234–245. https://doi.org/10.21776/ub.jam.2018.016.02.06 https://jurnaljam.ub.ac.id/index.php/jam/article/download/1277/990
Aguanno, K., & Schibi, O. (2019). Agile business analysis: enabling continuous improvement of requirements, project scope, and agile project results. J. Ross Publishing. Retrieved November 19, 2021, https://ebookcentral-proquest-com.torrens.idm.oclc.org/lib/think/reader.action?docID=5762202
Cui, A. S., & Wu, F. (2017). The impact of customer involvement on new product development: contingent and substitutive effects. Journal of Product Innovation Management, 34(1), 60–80. https://web-p-ebscohost-com.torrens.idm.oclc.org/ehost/pdfviewer/pdfviewer?vid=1&sid=0007861d-ee8c-4d58-b9ed-4ae73887162b%40redis
Humphrey, A. (2017). User personas and social media profiles. Persona Studies, 3(2), 13–20. https://search-informit-org.torrens.idm.oclc.org/doi/epdf/10.3316/informit.955882816086719
Lombardo, C. T., McCarthy, B., Ryan, E., & Connors, M. (2017). Product roadmaps relaunched: how to set direction while embracing uncertainty (First). O'Reilly Media. Retrieved November 19, 2021, https://learning-oreilly-com.torrens.idm.oclc.org/library/view/product-roadmaps-relaunched/9781491971710/ch01.html#what_is_a_product_roadmapquestion_mark
McGreal, D., & Jocham, R. (2018). The professional product owner: leveraging scrum as a competitive advantage (Ser. The professional scrum series). Addison-Wesley. Retrieved November 19, 2021, https://learning-oreilly-com.torrens.idm.oclc.org/library/view/the-professional-product/9780134686639/ch01.xhtml#ch01_level1sec1
Nguyen-Duc, A., Khalid, K., Shahid Bajwa, S., & Lønnestad, T. (2019). Minimum viable products for internet of things applications: common pitfalls and practices. Future Internet, 11(2), 50–50. https://sci-hub.se/10.3390/fi11020050
Ritter, M., & Winterbottom, C. (2017). Ux for the web : build websites for user experience and usability. Packt Publishing. Retrieved November 19, 2021, https://web-a-ebscohost-com.torrens.idm.oclc.org/ehost/ebookviewer/ebook/bmxlYmtfXzE2MDc4NTJfX0FO0?sid=4bd672a9-8eec-488e-92d2-89719b1b0db8@sdc-v-sessmgr03&vid=0&format=EB&rid=1
Rødseth, H., & Schjølberg, P. (2017). Maintenance backlog for improving integrated planning. Journal Of Quality In Maintenance Engineering, 23(2), 195-225. https://www-emerald-com.torrens.idm.oclc.org/insight/content/doi/10.1108/JQME-01-2016-0002/full/pdf?title=maintenance-backlog-for-improving-integrated-planning
Szabo, P. W. (2017). User experience mapping : get closer to your users and create better products for them. Packt Publishing. Retrieved November 19, 2021, https://web-p-ebscohost-com.torrens.idm.oclc.org/ehost/ebookviewer/ebook/bmxlYmtfXzE1Mjc4MTBfX0FO0?sid=0b24af53-6b53-41e6-84b3-4cad421a4fc4@redis&vid=0&format=EB&rid=1
Tolbert, M. (2020). Hybrid project management: using agile with traditional pm methodologies to succeed on modern projects (Ser. Issn ser). Business Expert Press. Retrieved November 20, 2021, https://ebookcentral-proquest-com.torrens.idm.oclc.org/lib/think/reader.action?docID=6362838
Wysocki, R. K. (2019). Effective project management : traditional, agile, extreme (8th ed.). John Wiley & Sons, Incorporated. Retrieved November 20, 2021, https://ebookcentral-proquest-com.torrens.idm.oclc.org/lib/think/reader.action?docID=5747804
Would you like to schedule a callback?
Send us a message and we will get back to you
Highlights
Earn While You Learn With Us
Confidentiality Agreement
Money Back Guarantee
Live Expert Sessions
550+ Ph.D Experts
21 Step Quality Check
100% Quality
24*7 Live Help
On Time Delivery
Plagiarism-Free
81 Isla Avenue Glenroy, Mel, VIC, 3046 AU
