Wk 3 Discussion – Analyzing The Quality User Story

Post a total of 3 substantive responses over 2 separate days for full participation. This includes your initial post and 2 replies to other students.

Due Thursday

Respond to the following in a minimum of 175 words:

Save your time - order a paper!

Get your paper written from scratch within the tight deadline. Our service is a reliable solution to all your troubles. Place an order on any task and we will take care of it. You won’t have to worry about the quality and deadlines

Order Paper Now

Depending on the type of project and the SDLC applied, system requirements may be developed differently. For example, many current projects use the Agile SDLC and build requirements based on user-story format. A user story is essentially a use case that describes how a specific user would interact with a system. An example of a user story tied to a customer using an ATM might be, “As a customer of the bank, I need to be able to access my account from an ATM to understand balances across all of my accounts.”

What are the attributes that comprise a quality user story, and why are these attributes necessary? Consider the result of poorly-written user stories. Provide an example of what you would consider to be a quality user story. This example can be from experience, from a company you know of, or one that you create.

Due Monday

Reply to at least two of your classmates. Be constructive and professional in your responses.