Reference no: EM132838207 , Length: 2000 words

PREPARATION FOR THE ASSESSMENT

You are required to use the scenario to do the following:

a) Read through the CASE STUDY
b) Identify stakeholders and categorise them as primary, secondary, tertiary or facilitating
c) Build a power/interest matrix and decide how you will communicate with stakeholders during the project
d) Identify User Roles for the application and consolidate them
e) Choose 2 important user roles and create a persona for each one.
f) Create a low-fidelity prototype
g) Create a set of user stories using the user roles and low-fidelity prototype to help you. Check your user stories with INVEST
h) Create acceptance tests for 10 of your user stories
i) Estimate all of your stories using story points, prioritise them and identify the MVP
j) Create a release plan
k) Reflect on the strengths and weaknesses of the agile approach to requirements gathering and planning

Submit a 2,000-word REPORT with the following 4 sections.
1) Stakeholder analysis
a) Stakeholder identification
List stakeholder groups for the scenario, stratified into four categories: primary, secondary, tertiary, and facilitating.
About 100 words
b) Communication plan
Present a power/interest matrix for the stakeholder groups identified above.
Describe how you will communicate with the different stakeholder groups during the project.
About 200 words
c) Stakeholder discussion
Explain why it is important to identify and engage with a wide range of stakeholder during IT projects,
including a discussion about how IT projects need to deliver business value.
Justify the approach you have taken to stakeholder communication. About 250 words
2) User analysis
d) User roles Present a consolidated list of user roles (you can do this as a list or a diagram)
Briefly describe each of the user roles
About 150 words
e) Personas
Present two personas based on two of the user roles you think are the most important.
About 200 words
f) Low-fidelity prototype
Present a low-fidelity prototype to identify key features that each of the user roles might need.
About 200 words

3) User Stories
g) User stories
Present an initial set of user stories for the application listed in priority order.
For ONE of your user stories explain how it is independent, negotiable, valuable to customers or users,
estimable, small, and testable.
About 200 words
h) Acceptance tests
Present the acceptance tests for 10 or your user stories.
About 20 words
4) Planning
i) Estimate and plan
Present comparative story point estimates for your stories and an indicative release plan, including an
indication of the MVP.
About 200 words
j) Reflection
Discuss the strengths and weaknesses of the agile approach to requirements gathering and planning.
About 300 words
5) References
List the references that you have cited in the text. See the REFERENCE GUIDE (attached)

CASE STUDY - Lauretti's Leather Belts Web and Mobile Order Handling Service

Attachment:- Assignment.rar