When we look at information technology products, 70% of software projects fail due to poor requirements. The main reason for this is not because the requirements are poorly written, or even poorly communicated, but because within the scope of an IT project, requirements lose customer focus and lack a holistic frame of reference for BAs to drive and trace requirements from the true customer needs; and, more importantly, from the business’s vision, and forward-looking strategy. Alignment to organizational strategy, and to customer value, are most effectively achieved through Business Architecture.

Business Architecture defines “what we do” as an organization and “why we do it.” It provides a common view of what makes up the business, how it brings value to its customers, and how IT supports its goals. It is the way IT, and Architecture, align with the business strategies, business goals, and business priorities.

In this presentation, you will learn what Business Architecture means to a Business Analyst, and how it impacts, and drives, Stakeholder Requirements.

Learning Objectives:

• How Business Architecture can be used to facilitate decision making on strategy, priorities, and investments
• What is a Business Capability Model and how BAs can use it to align business requirements with the business
• How BAs can use Business Capabilities to understand what business processes, business stakeholders, and business information must be part of the project’s business requirements