I decided it was time to take a step back. Every time we started a conversation, stakeholders would be talking in a mix of customer terminology and database fields and everyone would be so confused that we didn’t get very far. ![]() The way the customers thought about the information was very different than how the system that had been created 10+ years earlier stored the information. While clarifying language and asking good questions can clear up many ambiguities, sometimes it’s simply not enough to talk through a problem or issue.įor example, on one project we were figuring out how to provide customer access to a collection of information previously restricted to internal users. Speed Up Requirements Discovery With A Clarifying Modelįirst and foremost, the time I turn to visual modeling is when stakeholders are failing to understand each other. Let’s take a look at some of the circumstances that slow the requirements process down and how visuals can create breakthroughs that help you get things done faster. But in reality, using the right visual modeling tools pays immediate dividends by making the requirements process faster. ![]() Many business analysts mistakenly believe that adding a visual model to a specification – or preparing one specifically for a requirements meeting – means significant extra work.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |