Changes

Jump to navigation Jump to search
no edit summary
Line 6: Line 6:  
<h2> INTRODUCTION - How to use the Playbook</h2><br>
 
<h2> INTRODUCTION - How to use the Playbook</h2><br>
   −
This EA Playbook is intended to help Enterprise Architects build their departmental Enterprise Architecture.  
+
This EA Playbook is intended to help Enterprise Architects build/manage their departmental Enterprise Architecture.  
 
The book is organized into chapters as per the B-I-A-T-S+P architecture layers called Plays. We recommend that users:
 
The book is organized into chapters as per the B-I-A-T-S+P architecture layers called Plays. We recommend that users:
   Line 24: Line 24:  
A Business Architecture is where an organization identifies the various services that it suppose to provide externally, as well as the various functions it owns or needs to own internally to support the external service. In terms of GC Enterprise Business Architecture, this is where the Government of Canada identifies the various departments, the services they provide to Canadians and the functions they owns. <br><br>
 
A Business Architecture is where an organization identifies the various services that it suppose to provide externally, as well as the various functions it owns or needs to own internally to support the external service. In terms of GC Enterprise Business Architecture, this is where the Government of Canada identifies the various departments, the services they provide to Canadians and the functions they owns. <br><br>
   −
<b>Fulfill the Government of Canada stakeholder's needs</b>
+
<b><u>Fulfill the Government of Canada stakeholder's needs</b></u>
* Clearly identify internal and external stakeholders and their needs for each business service including user centric design
  −
* Include  policy requirement applying to specific stakeholder groups, such as  accessibilities, gender based+ analysis, and official languages in the creation of the service
  −
* Model end-to-end business service delivery to provide quality, maximize effectiveness and optimize efficiencies across all channels (e.g lean process)
      +
As provider of service to Canadians, departments need to understand their stakeholders well. The stakeholders include their users, their partners (if any), their suppliers (if any), their program or project manager, their implementor, etc. Once you identify all your stakeholders, you need to identify their requirements and figure out how to make it easier for them to use your service, which means you need to really drill down your user interface design. This is what digital is all about, to make it easy for your users to consume your service.
   −
<b>Architect to be Outcome Driven and Strategically Aligned to the Department and to the Government of Canada</b>
+
While configuring your service, you should also take into account the policy requirements
 +
 
 +
* <b><I>Clearly identify internal and external stakeholders and their needs for each business service including user centric design </b></I>
 +
To understand your stakeholder, it is recommended for program & project manager to conduct stakeholder analysis and create stakeholder mapping for each service being delivered. Users in this case can be Canadians (in terms of service your department provides), employees (if the service also applicable to your employees, or if your employees is the one implementing the service), or others. Partners can mean other departments or organizations that consume your service or provide data to you, or those who are building the system or building the program with you. Suppliers can be the SaaS companies who provide you with service, vendors, SSC, etc.
 +
 
 +
* <b><I>Include policy requirement applying to specific stakeholder groups, such as accessibilities, gender based+ analysis, and official languages in the creation of the service </b></I>
 +
 
 +
In identifying your stakeholder, ensure you are being inclusive, include other stakeholder groups.
 +
 
 +
* <b><I>Model end-to-end business service delivery to provide quality, maximize effectiveness and optimize efficiencies across all channels (e.g lean process)</b></I>
 +
 
 +
 
 +
<b><u>Architect to be Outcome Driven and Strategically Aligned to the Department and to the Government of Canada</b></u>
 
* Identify which departmental/GC business services, outcomes and strategies will be addressed  
 
* Identify which departmental/GC business services, outcomes and strategies will be addressed  
 
* Establish metrics for identified business outcomes throughout the lifecycle of an investment
 
* Establish metrics for identified business outcomes throughout the lifecycle of an investment
Line 36: Line 46:       −
<b> Promote Horizontal Enablement of the Enterprise</b>
+
<b><u> Promote Horizontal Enablement of the Enterprise</b></u>
 
* Identify opportunities to horizontally enabled business services and provide cohesive experience to stakeholders
 
* Identify opportunities to horizontally enabled business services and provide cohesive experience to stakeholders
 
* Reuse common business capabilities and processes from across government and private sector
 
* Reuse common business capabilities and processes from across government and private sector
514

edits

Navigation menu

GCwiki