Reflect on the following in a minimum of 500 words each. Complete your reflections by responding to all prompts.

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. 

Reflect on the above and identify two to four steps or activities a project team can take that will influence user adoption.

• Explain how these steps or activities will influence      user adoption.

Requirements Testing

As a project manager or senior systems developer, you are most likely aware that when developing new systems, teams tend to focus on understanding the requirements of the system at the start of the project. Until requirements are known, it is hard to understand design and development components. Beyond this, testing is an essential part of any systems project, no matter what SDLC is applied.

Reflect on the following:

• When do you think a project team should plan for      testing? Why?
• Who do you think is the best resource(s) to conduct      testing activities? Why?

Technology Trends

​​​​​​​As an IT leader, you are aware that technology advances rapidly in the current market and can become dated and obsolete quickly. Organizations must keep pace with the evolution of technology to compete and sustain a market advantage.

Reflect on the following:

• What are some emerging technology trends that have      influenced your personal choice of an SDLC, either in your experience or      in something you have read?
• Discuss the trend and the influence and effect it had      on you. Were there any issues?
• Would you recommend the same SDLC if you had to do it      again?