IN THIS ISSUE
Featured articles showcased in this issue:
> When in Rome: The Role of a Good, Global Business Analyst
> What the Heck Is Enterprise Analysis - Part 1
> Activity Diagram – Usage and Benefits
> Documenting SOA
> Webinar: BA Best Practices: Reporting Requirements, Design, Creation and Distribution
> Webinar: Optimizing Requirements Discovery
> Webinar: Jazz Up Your Collaborative Lifecycle Management
Also in this issue:
> More Business Analyst Humor
> Even more Resources for Business Analysts
> New Interview Questions
When in Rome: The Role of a Good, Global Business Analyst
by Glenn R. Brûlé, Executive Director, ESI International
Yes, the world is flat, and the reality of today’s global economy is that business analysts (BA) from all corners of the earth often work with one another. But they don’t always understand how business efficiency is impacted by the comprehension of their inherent differences. There are fundamental philosophical and behavioral differences between professionals across the world that impact business success.
What the Heck Is Enterprise Analysis - Part 1
by Robin Goldsmith, Go Pro Management, Inc.
For many business analysts (BAs), the IIBA Business Analysis Body of Knowledge (BABOK®) Knowledge Area that is the least familiar is Enterprise Analysis (EA). In some ways, this may be a mixed blessing. On the one hand, the BABOK® (v2) EA area describes important topics and techniques that BAs should be conversant with: defining business needs, solutions, business cases, and project initiation. On the other hand, I have issues with the ways BABOK® v2 treats these topics.
Activity Diagram – Usage and Benefits
by Brad Botz, Business Analyst
As part of the Unified Modeling Language, Activity diagrams are often utilized for many software projects. However, a few questions about Activity diagrams linger in the minds of many Business Analysts, such as: Who is really using them? What kind of projects are they being used on? Why are people not using them? How are people using them? Are they providing any benefit?
by John Moe, Head of Business Integration, Tori Global
For projects that may well be delivered by Service Oriented Architecture (possibly using Service Oriented Analysis), I would suggest that you may need to consider different or additional ways of documenting your requirements and specifications. The reason for this is that the way you shape your requirements needs to encompass both the holistic nature of SOA, as well as the new terminology and delivery mechanisms.
BA Best Practices: Reporting Requirements, Design, Creation and Distribution
Wednesday, November 10, 2010 Register Now
Optimizing Requirements Discovery
Tuesday, November 2, 2010 Register Now
Jazz Up Your Collaborative Lifecycle Management
Tuesday, October 19, 2010 Register Now
MORE FROM ModernAnalyst.com
More Articles of Interest & Featured Posts
> Three Types of Design Effort
> Intermediate Business Analyst Certification Brings Hope for the Junior Business Analyst
> The single most important failure with requirements
Relevant Interview Questions
> What is Gap Analysis?
> What is a Communication Diagram?
> What is a database view and why should the business analyst understand it?
Informative Blog Posts & Resources
> Enter the Business Engineer
> Why Should We Hire You?
> Risk Management - Opinions on best practice
> Business Process Analysis (BPA) for the Masses -- Is It Real?