Read the case below -- Develop a non-profit management application. Then write ten user stories based for the case below. Upload the user stories in a Word document to this location. Case Requirements: You are a new employee at a non-profit called Mx. Their mission is to help children get a better education by sponsoring workshops and lectures across the country. Their events are growing at a rapid pace and it's been challenging to keep track of all the logistics. In addition, their donors are very generous and have been willing to give more. However, it's been challenging to keep track of all the donations. Your manager is asking you to come up with a solution to keep track of all the information and automate/improve the processes. Desired features: Donors portal where they can log in and see all of their donations and how their money is being spent Employee portal where they can log in and do the following: Track the donors, their donations and update any relevant information Track the events they do and the benefits those events provide Track the cost of the events and the donors funding for those events Attendees can register for upcoming events hosted by Mx Everyone wants to know everything on their phone so they can access it on the go Send automatic thank you emails to donors every time they donate Sent automatic invitations to individuals to upcoming events Add a calendar for all the events scheduled . Introduction In this section of the module, you will learn how to correctly write user stories. User stories provide short descriptions of the functionality for an application from the perspective of the person who wants and will use that functionality. The format of user stories is: As a I want so that Examples of user stories are: 1. As an administrator, I want to be able to manage my data so that I can make changes at any time. 2. As a teacher, I want to be able to see the number of trainees attending a training event at any time so that I know what resources I need. 3. As an HR Manager, I want to view a candidate's status so that I can manage their application process throughout the recruiting phases. Knowledge Auser story is a requirements tool used in the agile software development methodology. While the story is simple it will spark conversations so that the developer can understand the reason for the story and the system behavior that will be needed to successfully fulfill the story. The three parts of the user story are the who, what and why of the system requirement. The "who" is the role. Most applications will have categories of users. They can write the story, or it can be written for them. The "what" is the feature that is being asked for in the story. It can be the activity that they want to be able to do on the system (like check their spelling) or an activity that they must do (enter their password). The "why" is the reason that the user wants the feature. This provides the system developers the context for the user story and will help guide them on how to implement the functionality. Key Points to Remember User stories are written from the viewpoint of the system user. As a , I want , So that can achieve some goal/benefit/value> User Story is narrated from the user's perspective regarding what he or she wants to have rather than what the system can do for him