There’s an old fable about six blind men who encountered an elephant for the first time. Although they couldn’t see it, they wanted to learn what an elephant was like. Each of them touched a different part of the elephant.
The Agile Extension to the BABOK® describes “business analysis areas of knowledge, their associated activities and tasks, and the skills necessary to be effective in their execution within the framework of agile software development”. Below are 3 misconceptions that, in my opinion, the current draft of the Agile Extension is helping perpetuate.
Your meeting is underway and while you’re attentively listening to the business SME explain the detailed process for transferring a policy from one agency to another, you find yourself feverishly jotting down notes as the nuggets of information being thrown out are too juicy not to capture. Then it hits you: you have no idea what the business SME is talking about!
Today’s letter is “C” – for Class Diagrams. Business Analysts use Class Diagrams to help them discover ‘structural’ business rules and to document them in a visual form that is readily understood by developers. What is a structural rule?
Agile development is an approach that evolves requirements and software through iterative deliverables. One of its principles is to deliver working software frequently, often through a series of two to three week iterations. The Decision Model (TDM) is a model for the full and rigorous specification of logic.
brought to you by enabling practitioners & organizations to achieve their goals using: