EA/BPM COE II: Practices, People & Tools Implementation
EA/BPM COE II: Practices, People & Tools Implementation
3-6 month implementation services: Start enabling your programs/projects and Information Technology department to realize the day-to-day & long-term benefits of Enterprise Architecture and Business Process Management. This includes the the right mix of advisory and side-by-side engagement to enable the EA/BPM COE services: staffing/training, tool selection/implementation, and definition/tailoring of practices, methods and frameworks.
Staff selection/hiring/training — based on existing guidance or service design guidelines from “EA/BPM COE I Policy” advisory or other policy guidance, the ideal staffing mix is updated/confirmed (e.g., full-time, interns, contractors, offshore). Job descriptions are updated/confirmed, and teams are assembled and organized for maximum flexibility to support Line-Of-Business product/service development versus centralized to meet cost/efficiency/compliance goals. Optionally includes college campus partnership and recruitment advisory service.
Tool selection/implementation/customization — based on existing guidance or service design guidelines from “EA/BPM COE I Policy” advisory or other policy guidance, an appropriate EA/BPM platform is selected. BPM capabilities and requirements are updated/confirmed, and tooling scope is expanded as needed to accomodate additional requirements (e.g., integration with existing program/project management tools, inclusion of capabilities such as Application/Technology Portfolio Management, or integration with GRC platforms such as RSA Archer). Cloud/on-premise tools are selected, implemented and/or customized as needed.
Practices, Methods and Frameworks: based on existing guidance or service design guidelines from “EA/BPM COE I Policy” advisory or other policy guidance, detailed COBIT-5 derived practices are tailored to enable staff to deliver EA/BPM services using the customized toolset. This includes integration or enhancement of the existing Software Development Lifecycle (SDLC) / Continuous Delivery Pipeline (CDP) to include EA/BPM artifacts, helping to improve flow and quality (e.g., “shifting left” by improving behavior-driven development to utilize up-to-date processes and risk/compliance information, and standard technology components). TOGAF-derived frameworks are updated as re-usable meta patterns in the tool, which form the basis for design of standard technology components.
