Business analysis is an indispensable function in all business organizations, performed at myriad forms and scales. Maintaining high quality of business analysis consistently is a challenge to many organizations. Inconsistent business analysis output quality results in undesirable project outcomes, poor decisions, operational disjoints and missed opportunities. This article uses an actual case to discuss how low quality business analysis impacts an organization and what improvement initiatives the organization implemented to address the problems.
Given the right circumstances, even good people can go astray as our psychology push us down the slippery slope of questionable behavior. A little bit of knowledge about the forces that drive us to cheat can go a long way helping avoid bad behavior. Here are some common landmines to become aware of so you can make sure to defuse them as you embark in a new BA project
The context diagram and the use case diagram are two useful techniques for representing scope. This article describes two other methods for documenting scope: feature levels and system events.
I’ve been a Business Analyst for about 15 years now starting as a graduate back in the day. And while I do not consider that to be close to a career’s worth of experience I have certainly seen significant changes in the way business analysis is performed and the tools that are used thanks to the evolution of technology.
Every software team talks about project scope and team members often complain about unending scope creep. Unfortunately, the software industry lacks uniform definitions of these terms, and the requirements literature is short on clear guidance regarding how to even represent scope. I confront scope head-on in this series of three articles...
brought to you by enabling practitioners & organizations to achieve their goals using: