Best Practices for Better Business Analysis
Today IIBA announced a new members-only publication called BP4BBA. I'm sharing because I'm the first author to be published - and pretty excited! Thanks to my reviewers for their advice, and Paul Stapleton (Technical Writer/Editor, IIBA).
IIBA doesn't have commenting on these articles yet, so please feel free to leave comments and questions here.
Welcome to the inaugural edition of Best Practices for Better Business Analysis™ - a new publication fro IIBA Members.
Best Practices for Better Business Analysis is a series of peer reviewed articles that provide you with tips, techniques, thoughts, and experience that will have a direct impact on your day-to-day practice of business analysis.
We hope you enjoy our January article:
Most requirements documents have a section dedicated to Constraints, Assumptions, and Dependencies (CADs). In theory, CADs play an important role in controlling organizational changes. In practice CADs are often used to shift blame when things go wrong. There is a practical way to address this: restructure all constraints, assumptions, and dependencies as risks or requirements.
- You can define common attributes among constraints, assumptions, dependencies, risks, and requirements.
- You can translate constraints, assumptions, and dependencies into risks or requirements.
- You can plan to represent this information in your organizational context.
- CADs cause change agents to inadvertently misrepresent and obscure important information.
- CADs can be translated into requirements or risks because they all share six attributes (events, impacts, probabilities, timeframes, stakeholders, and responses).
- Organizations rarely have capabilities in managing CADs, and often have capabilities in managing risks and requirements.
Paul Stapleton, Technical Writer/Editor, IIBA
Your opinions and ideas matter. What do you think?