There are as many types of business analyst personalities as there are organizations and projects. The million-dollar questions is, how can a manager match an analyst’s unique skills to the projects that can really benefit from them, helping to ensure a project’s success? How can a manager build stronger, perhaps more suitable skills in his analysts?
Abraham Maslow once said “If the only tool you have is a hammer, you tend to see every problem as a nail.” This article provides the project manager (PM) / business analyst (BA) a framework for categorizing business problems as a baseline for selecting a solution development life cycle (SDLC).
“The overall purpose of Business Analysis is to build a bridge between business and IT”. This is a good enough definition for a position as hard to define as Business Analysis.
Can the same business rule be enforced differently in different contexts? The answer – an important one for re-use of business rules – is yes. This article explains. It also outlines what business analysts need to know to specify contexts of enforcement for a business rule effectively.
A software tool for The Decision Model supports the entire life cycle of Decision Management. This includes the authoring, analysis, testing and deployment of entire decision models. Whether managed by the business – as some people consider ideal – or managed by IT or business analysts on behalf of the business – as others consider necessary – business decisions need not only a repository for storing decision models, but a range of functions to manage them effectively.
Taking a long lens approach to looking at 2011 is an apt metaphor that should serve as a reminder to BAs of the perspective they need to take to in terms of both their professional development and their role in the organization. There’s no better time to take stock and strategize on how to best prepare for the opportunities and the challenges you’ll experience ahead.
brought to you by enabling practitioners & organizations to achieve their goals using: