Must have automation to deploy new changes to the cloud.

[scrumluvva]

As a Service Provider, I need to have automation to deploy new changes to the cloud So that I can achieve faster, practically error-free release cycles and a consistently satisfied customer.

Details and Assumptions

• [document what you know]

  Acceptance Criteria

  Given [some context]
  When [certain action is taken]
  Then [the outcome of action is observed]

[scrumluvva]

I'm on the fence with this one. Automation is a need, right? It's not something in the background that doesn't affect the customer...or is it? (See how I'm second guessing myself on this one?) Wouldn't that make it an enhancement? I went back and forth because of how I wrote the user story. I went ahead and made this technical debt because of how it was sampled in the training and moreso out of (perceived) assignment obligation for at least one in the Product Backlog to be labeled as such.

I authored some Details and Assumptions and Acceptance Criteria but did not include them because the assignment didn't call for it. Here it is though:

Details and Assumptions

• The happiest e-commerce customer is the one whose website runs smoothly.
• Automation helps to mitigate costly manual mistakes, which means it's more effective.

• Automation is more efficient than manual updates.

  Acceptance Criteria

  Given I can have said automation,
  When I utilize it to deploy new changes to the cloud,
  Then those changes will quickly update, resulting in 
  seamless system enhancements and a still highly satisfied customer.