Best Practices for Defining Api Integration User Stories
Fleeting- External reference: https://blog.cloud-elements.com/best-practices-api-integration-user-stories
Best Practices for Defining API Integration User Stories.
the place to start is by writing out user stories that provide a clear picture of the experience you envision for your end-customers.
— https://blog.cloud-elements.com/best-practices-api-integration-user-stories
By developing user stories in the system persona, we can become too focused on the technical aspects of integration instead of the collaborative user experience we’re trying to establish
— https://blog.cloud-elements.com/best-practices-api-integration-user-stories
they guide the integration as a technical solution, but not as effectively as a business solution
— https://blog.cloud-elements.com/best-practices-api-integration-user-stories
A different way to write a user story is through a user persona. A great user persona is written from the point-of-view of an end-user
— https://blog.cloud-elements.com/best-practices-api-integration-user-stories
important to get as much use out of these personas as possible to ensure that your stories relate back to an experience model from the viewpoint of your end-users
— https://blog.cloud-elements.com/best-practices-api-integration-user-stories
If an integration task doesn’t involve users, write API user stories with a system persona so you can elaborate on the behind-the-scenes integration tasks that aren’t user-centric
— https://blog.cloud-elements.com/best-practices-api-integration-user-stories
Write User Stories Based on User Personas
— https://blog.cloud-elements.com/best-practices-api-integration-user-stories
As a (Persona), I want (Need), So That (Goal)
— https://blog.cloud-elements.com/best-practices-api-integration-user-stories
application-to-application persona (or system persona) to represent background system functions that do not require interaction from the end-user. The purpose of this system persona is to provide an additional level of detail and acceptance criteria beyond the user interaction scenario.
— https://blog.cloud-elements.com/best-practices-api-integration-user-stories
System-to-system user stories should be limited to providing a more detailed understanding of the behind-the-scenes interactions required between systems, but should not replace the user persona-driven stories.
— https://blog.cloud-elements.com/best-practices-api-integration-user-stories
write stories from your typical user personas and then elaborate with system personas to better visualize the end-to-end user experience.
— https://blog.cloud-elements.com/best-practices-api-integration-user-stories