Written by Timothy Figueroa . Published in the article.
Many customer requirements are complex and involve complete end-to-end solutions. Adding complexity is often the need to integrate these solutions into existing systems. This article focuses on the value of using complex requirements and experience design tools to support BAs in achieving customer goals.
The BA’s approach to withdrawals is critical for the BA to demonstrate understanding of requirements, work quickly, and reach consensus.
A BA approach should support continuous communication, rapid response, shared understanding, risk mitigation, and collaboration across distance and time. For complex requests where analysts write out detailed requirements upfront, it can actually lead to misunderstandings in communication, slowdowns, and limited collaboration. Most customers are business managers and the pre-generated detail approach overwhelms the customer and obscures their view of the end-to-end solution making the customer and her BA “can’t see the forest from the trees”. It can put you in a scenario.
The choice of approach typically determines how efficiently and effectively a BA meets customer needs. Most of the time it tells the customer, “You have listened to me,” “Show me what I asked for,” or “Demonstrate progress towards a solution or roadmap.” increase. ”. Her BABOK at IIBA defines knowledge domains containing strategies, guidelines, and techniques that provide a set of approaches for deriving knowledge.
One efficient technique is the use of prototypes. It is said that “seeing is believing”. Prototyping is a proven method of product design and goes a long way in providing an initial model of the final result.
Prototyping in this case emphasizes the use of experience design tools for web and mobile apps to support complex request elicitation activities. Complex requests are an indicator of prototype usage.
advertisement
The use of experience design tools is typically cloud-based to support collaboration and communication. These types of tools also support the big picture, allowing customers to experience what the solution might look like without spending time and money on development.
Users have no experience with databases, integrations, or technical details. These are affected, but the user experience is her UI, workflows, processes, features and functions. Prototypes promote common understanding by helping customers understand the UI, processes, workflows, and solution models that incorporate features and functionality.
There are several industry-leading experience design tools that support solution prototyping. This article does not go into detail about specific tools, but rather focuses on the value of using these tools to meet complex business demands. Experience design tools provide business analysts with the ability to document requirements in the form of customer-written prototypes. The value of an experience design tool is to support BA’s ability to create simulated solutions.
- Customers walk through, comment, suggest changes, discover unexpected things, use for demonstration purposes, etc…
- The technical team can also ask questions, make suggestions, prioritize work, plan technical details, and use additional documented requirements to reach common consensus. may describe a proposed solution.
- BAs can plan and create requirements from customer-approved prototypes without leaving out any details. Prototype assets (i.e. UI, processes, etc.) can be reused in documented requirements to provide required detail.
In conclusion, experience design tools can reduce misunderstandings, facilitate communication and collaboration, and support progress. Consider adding experience design tool skills to your BA toolbox. A picture is definitely worth a thousand words!
