CMGTCB/555: Systems Analysis and Development
2
Analyzing the Quality User Story
The first question one must ask themselves is what is a user story? A user story is used to expressed the desired functionalities of a product. The stories can be categorized in both high and low priority status which helps prioritize the user needs. A poorly written user story can cause confusion, and the effect of having confusion is time taken away from creating the project. Another attribute that could compromise a user story is poor communication. Miscommunicating about the project can cause the team to miss important requirements that could compromise the security of the project. Thus putting the entire project at risk for incomplete tasks, and a disconnect throughout the development team. Good User Story
A good user story will provide the user and development team with the required information to start and end the project. One could assume that a good user story is testable. Testing the project allows
the development team and users the ability to see their progression of the project, and the option to make improvements to meet the needs of the user. Miscommunicating when writing a user story can cause an entire project to be prolonged and loss of money. An example of a positive user story is: As a transportation manager, I want to be able to understand intermodals, so I can better assist my drivers. An example of a bad user story is: As a transportation manager, I want to go outside. The difference between the good and bad user story is that a good user story is more detailed, and a bad user story is too vague and lack the necessary details to complete the project. User adoption
User adoption is defined as the process the users through to determine if they will use the created product long term (Scout, 2023). A user adoption can be influenced by prioritizing the user experience and developing a plan to ensure that the product key features are not changed. One should
