Design-Driven User Story for Agile Development.
The business analysis skillset is very important to me. I have learned over the 15 years of doing use cases, user stories, requirement documents and other documentations, that efficient documentation and velocity not always come easy.
In a recent project assigned to me I was challenged to take a massive group of requirements in an Epic, elaborate, analyze and make it ready for development in one sprint time. 🤔 Challenge Accepted!!!
Some important facts about the Epic:
- Mockups were ready and approved;
- All requirements were also reviewed by Stakeholders;
- The Epic purpose is a new feature to our SaaS Care Solution submitted by legal, so up most priority for this quarter-end time.
Straight to Solution Design Elaboration:
Our goal was to understand and analyze the requirements while designing the solution architecture. The design focused on mapping the business-process with requirements, complemented by the UX mockups and integration dependencies.
Big job, but defiantly not impossible for this amazing group of people.
Business Model –> Use Case Model –> UX Mock-Ups –> Solution Architecture

My Notes:
The most important artifact of this project: Solution-Design-Model. At the grooming meeting I presented the model to the scrum team. After a 30 minutes of intense Q&A the team decided to use the model as development artifact (user-story). The model was broken using the UX Flow, and that’s how that work was divided inside the scrum.
While development was being done, QA team and DevOps received the same model and notes from the scrum-team as artifact. They also liked the design-model 🧐.
Mission accom
Great team.


