Analyzing the Quality User Story
As a project manager, you are most likely aware that 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.”
Reflect on the following:
- 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.
Driving User Adoption of New and Changed System
As a senior systems analyst or project manager, you are most likely aware that implementing a new system, or modifying an existing one, can create organizational change. This change can impact how employees work, how information technology teams support the business, and even how customers interact with the organization. Ensuring users adopt new systems or changes to existing systems is critical, as implementing a system no one will use becomes a wasted investment. User adoption should be considered by the business stakeholders no later than during the design phase.