When to incorporate design thinking in scrum
For many developers, QA automation engineers, and site reliability engineers participating in agile development teams, the delivery work starts by defining user stories and committing to complete them in sprints. Sometimes, the user story calls for a “back-end” implementation, such as configuring a data integration, coding a microservice API, addressing technical debt, or improving application performance. These are still user stories because their implementations provide business value, but the product owner can specify the target user experience with technical criteria. When the feature or user story calls for a “front-end” implementation that impacts the usability and requires a design, agile teams must decide when and how to incorporate design thinking, wireframing, user experience, and design specifications into the requirements. To read this article in full, please click here