BA Mindset Principle #8: Take Responsibility for Shared Understanding of Business Requirements

What is the most important outcome of business analysis activities? Is it detailed and intricate process maps? Comprehensive business requirements documents? Groomed user stories? A requirements sign-off obtained within schedule? All of the above are important. But there is something else…

BA Mindset Principle #7: Simplify Until Nothing Can Be Removed

Complexity is cited as one of the main reasons a project or a business change can fail: The overall architecture is too complex.Business rules are bulky, tedious and sub-optimal.Processes are overgrown with fluff and unnecessary steps created for political and…

BA Mindset Principle #6: Uncover Gaps – Do Not Cover Them Up

It does not matter what you call them – “gotchas”, “ah-ha moments”, “gaps” or “cans of worms”.  A discovery of something completely unexpected or totally opposite to the assumptions and beliefs of the stakeholders is not so rare. For example:…

BA Mindset Principle #5: Analysis Before Synthesis; Information Before Requirements

Many years ago, I took some business analysis training courses to receive an Advanced Certificate in Business Analysis (this was before IIBA). The very first mandatory course was called “How to gather and document business requirements”. The course provided a good background…