I am posting this question again, please provide appropriate answer, I'll put data in power point, please provide appropriate answers of all the questions asked in this assignment. Thanks.

Assignment 3: Application of Agile Business Analysis (30%)

Purpose

The purpose of this assignment is to demonstrate your ability to apply, evaluate and resolve all principles learned in this course related to an agile approach.

How to Proceed

1. Read through Part A of the case study provided below keeping in mind the concepts learned throughout the entirety of the course.
2. Develop a PowerPoint presentation to share with your team that includes the following (Note there will be no requirement to present this assignment verbally):
   1. Perform stakeholder analysis and plot stakeholders on a graph.
   2. Develop a user persona for one of the stakeholders of the case.
   3. The Epic for the scenario.
   4. The user stories pulled from the crafted Epic.
   5. The prioritization of user stories accompanied by a description of how you determined which prioritization technique to use.
   6. The user acceptance criteria for 2 user stories.
   7. A Kanban iteration or Scrum sprint to manage requirements that highlights which requirements will be included in the first cycle (assuming a maximum of 2 can be included at a time).
   8. A description of what Done looks like for the Authentication feature.
   9. An explanation of how you are being agile principles vs. doing agile in your responses above.
   10. Documentation of the assumptions made of the case that led you to certain decisions for sections A to I.
3. Read through Part B of the case study provided below and add a final slide to your PowerPoint presentation that includes the following:
   1. Lessons Learned from Part B and;
   2. Identify what kind of reports you would recommend the team use and why.
4. Submit your Assignment 3 Report through the dropbox in UM Learn.

The Case Study Part A

The medical device company has a regulatory requirement to implement enhanced authentication to all its software. The user must provide their login credentials to access the system and if the user forgets the credentials, there has to be a way to securely retrieve the information. The user does not want to have to authenticate themselves every time they access another part of the system when they are already logged into one part of the system. The technology is web-based and the entire process should not require the user to call technical support. By providing efficient logon mechanisms, doctors are able to access the system easily and with less effort leading to a more positive user experience.

The company must also adhere to the regulatory requirement that requires the technology to log the time, date and details of every user's access. Although the company conforms to this regulation, the policies were recently updated and the company has a 3 month grace period before the regulatory bodies enforce the new requirements. The new regulations require the company to log location and device in addition to the time, date and details of the user's account.

The developer on the agile team is excited about implementing a biometrics authentication feature to solve the stated policy requirements. Although, there is merit in the developer's suggestion, this implementation is complicated and lengthy and may not be completed within the stipulated regulatory timeframe. The team has not yet decided if they will implement the biometric idea. As the Agile Business Analyst, you need to perform stakeholder analysis, prioritization and decomposition of requirements into user stories and decide which of the stories will be included in iteration or sprint 1. You may decide to break the biometric feature into one or more user stories and only include this feature in your first sprint or iteration.

The users of this software include doctors, medical office assistants, and receptionists.

The doctors are not technically savvy and are introverted in nature. They believe in speed and get paid by the number of patients they meet. The age of a doctor ranges from 40-55 years and they are specialists with extensive experience. The doctors are excited about this change and are the sponsor for this initiative.

The medical office assistants are somewhat more technically savvy than the doctors. They perform administrative tasks for the doctor. For example, receiving and sending out medical samples for investigation. They are detail oriented and want to get things done right as opposed to quick. the average age of receptionists is 25-35. The medical office assistants are not looking forward to this change because it adds to their workload and can introduce errors in their existing workflow. Additionally, because they are so detail oriented they often take longer to accomplish a task and therefore they do not have time for training.

The receptionists are the front end staff responsible for attending to phone calls and patient check-ins who arrive at the clinic. The receptionists are extroverted in nature. Their average age group is 18-25 years. The receptionists are neutral on the implementation of the new features but have high influence on how this feature is designed. This is because they've been working in the field for many years and have earned the trust of the doctors.

The Case Study Part B

The medical device company went ahead and implemented both the features in the first iteration cycle. In their initial iteration, they did not track progress through reports. Additionally, the medical device company decided to implement the biometric authentication feature whose implementation took over 3.5 months. Due to the complexity of this feature, the medical device company was unable to meet the grace period provided by the regulatory board. The doctors are dissatisfied with the slowness of this company.