Transformation Of Agile User Stories Into Executable Code In A Built Application
Balancing "What" and "How" in User Stories
This is important in certain contexts, especially when the solution involves complex business logic that the development team is not familiar with.
Even in complex domains, the goal should be to clarify the business problem and requirements without dicting the technical solution. This might involve outlining the business rules or data needed without specifying the code or algorithms to use.
Use techniques like "Three Amigos" meetings (involving business analysts, developers, and testers) to explore and refine user stories together, ensuring everyone understands both the problem and potential solutions.
Provide the detailed "how" in the form of acceptance criteria, supporting documents, or during backlog refinement sessions, rather than in the initial user story.
Tim HJ Rogers
Consult | CoCreate | Deliver
I support people and teams to grow, perform and succeed unlocking potential as a partner Consultant, Coach, Project and Change Manager
Together we can deliver projects and change, and improve the confidence, capacity, drive and desire of the people I work with.
ICF Trained Coach | MBA Management Consultant | PRINCE2 Project Manager, Agile Scrum Master | AMPG Change Practitioner | Mediation Practitioner | BeTheBusiness Mentor | 4 x GB Gold Medalist | First Aid for Mental Health | Certificate in Applied Therapeutic Skills
#people #process #performance #projects #programmes #pmo #change #processimprovement #projectmanagement #changemanagement #workshops #mediation #coach #icfcoach #mentor #facilitation #training #jersey #channelislands
Friday, 2 February 2024
Balancing "What" and "How" in User Stories
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment