Success requires a highly skilled team from program management and architecture to operations.

Key Success Factors

1

Build the Right Team

2

Organize for Success

3

Build Coalition with Business Partners

4

Maintain Flexibility

KSF 1.1: Relentlessly assess the capabilities of the organization and make the required changes

• defined to-be skill set and built the team in about a year through rigorous recruiting

KSF 1.2: “Know what you don’t

•

know” and partner for success

partnered with Accenture and BEA’s Product Engineering groups

Organizational discipline and focus drive coordination and the development of skills.

Key Success Factors

1

Build the Right Team

2

Organize for Success

3

Build Coalition with Business Partners

4

Maintain Flexibility

KSF 2.1 Structure optimal development program

• Centralized program mgmt, architecture & planning, Infrastructure services, release management, etc.

•

KSF 2.2 Define your standards

Standardized delivery model (1 release equates to 12 people x 4 months), and built or integrated delivery IP (methods, configurations, etc.) across entire application lifecycle

The program structure was designed to align with the business units and provide focus on each program level function.

Program Structure Enterprise Infrastructure Services Marketing Business Liaison Sales Business Liaison Services Business Liaison G&A Business Liaison Dev2Dev PartnerNet eOrders eLicense Knowledge Express eSupport CIB/Support Renewals Program Management Office (Project planning and Reporting) Enterprise Roadmap, IT Strategy, and Budgeting Enterprise Architecture (Project and Future Planning) Enterprise Infrastructure Services (Development and Maintenance) Release Management (QA, CM, RM, Sys Admin) ROI Calculation / Adoption & Training eEmployee

The program functions are a set of shared services/resources that support projects from development through maintenance.

MyBEA Program Functions Function Program Management Office Enterprise Roadmap, IT Strategy/Planning and Budgeting Enterprise Architecture Enterprise Infrastructure Services (EIS)

• •

Description and Business Benefit

Overall management, planning and coordination of all projects, activities, and resources and Presentations.

. Communications (internal and external), Methodology Standards, Management Status Reports Drive the integrated and consolidated roadmap for all application development. Associate the program timeline to our quarterly budgeting processes.

• • Supports each of the technical business development teams with architecture/design. Group also provides support to the EIS team and is the primary liaison with product engineering groups for product feedback and architecture planning.

Development of the common portal, integration and application services. Providing services such as registration, login, profiles, exception handling, etc.

Release Management (Test, CM, DBA, Sys Admin)

• Testing, configuration, change management and integration of application code prior to release in the development, QA, and staging environments.

ROI Calculation / Adoption & Training

• Calculate ROI based on actual project costs and realized value of the business capability. Facilitate an adoption and learning program to maximize the potential of the new capability.

Our architecture helps us to provide a more responsive our delivery model for all projects: we typically use teams of 12 people for 4 months (12 by 4). 12x4 Delivery Model and Benefits Four month release cycle

•

Reduce risk equates to higher Release 1 Release 2 likelihood of project success

•

More effective teams and more 12 people team size

Project Mgr.

Technical Architect Release Mgt.

accountable team members

•

Synchronization with budgeting cycle allows for

Functional and Testing Lead(s) Developers (Web tier and EJB)

changing priorities

•

More Celebration Dinners!

Achieving a single corporate-wide vision is challenging for any organization.

Key Success Factors

1

Build the Right Team

2

Organize for Success

3 4

Build Coalition with Business Partners Maintain Flexibility

•

KSF 3.1 Secure executive sponsorship

CIO led alignment to vision with executive leadership team and other key senior executives • Early quick Wins (very visible) • • • •

KSF 3.2 Demonstrate value to business

Showed results often (quarterly releases) Evangelized each success Used standard ROI discipline Supported our business in new ways - sales support, feedback to Engineering

Business needs and technology evolve rapidly: do not cast your plans and designs in concrete.

Key Success Factors

1

Build the Right Team

2

Organize for Success

3 4

Build Coalition with Business Partners Maintain Flexibility

KSF 4.1 Do not design to far ahead of

•

business need or product capability

Created governance process with business partners to define future based on planned business needs • •

KSF 4.2 Keep Infrastructure Services light and modular

(“infrastructure as an enabler, not an anchor”) Designed thin, relatively “product version independent” services – leveraged industry standards Abstracted design components to ensure re usability