514
edits
Changes
GC Enterprise Architecture/Playbook (view source)
Revision as of 09:27, 14 January 2020
, 09:27, 14 January 2020no edit summary
As the provider of service to Canadians, it is important for the GC to understand the stakeholders well. The stakeholders in this case may be their users, their partners (if any), their suppliers (if any), their program or project manager, their implementor, etc. Once a department identify all its stakeholders, it needs to map them into their roles and responsibilities as well as identify their requirements. From there, department will need to figure out how to make it easier for the stakeholder to use the business service, which means department needs to really drill down on the user interface design of their service. This is what digital is all about, to make it easy for the users to consume the GC service.
As the provider of service to Canadians, it is important for the GC to understand the stakeholders well. The stakeholders in this case may be their users, their partners (if any), their suppliers (if any), their program or project manager, their implementor, etc. Once a department identify all its stakeholders, it needs to map them into their roles and responsibilities as well as identify their requirements. From there, department will need to figure out how to make it easier for the stakeholder to use the business service, which means department needs to really drill down on the user interface design of their service. This is what digital is all about, to make it easy for the users to consume the GC service.
While configuring the service, departments should also take into account the policy requirements, including accessibilities, gender based+ analysis and official languages.
Once the stakeholders are identified, the roles and responsibilities are mapped, and the stakeholder needs are identified and translated into business service, the department can then model a complete quality end-to-end business service that provides the best digital experience to its users while also maximize its effectiveness and optimize efficiencies.<br><br>
* <b><I>Clearly identify internal and external stakeholders and their needs for each business service including user centric design </b></I>
To understand the 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 the department provides), employees (if the service also applicable to the departmental employees, or if the employees is the one implementing the service), or others. Partners can be other departments or organizations that consume the departmental service, provide data to the department, or those who are building the system/program with the department. Suppliers can be the SaaS companies who provide the department with service, vendors, SSC, etc. <br><br>
There are various sites where department can visit to understand and use stakeholder analysis and stakeholder mapping. The following are examples of sites that department can use to obtain further on stakeholder analysis or mapping:
There are various sites where department can visit to understand and use stakeholder analysis and stakeholder mapping. The following are examples of sites that department can use to obtain further on stakeholder analysis or mapping:
<!-- TABLE ENDS --> |}
<!-- TABLE ENDS --> |}
<!-- COLUMN ENDS: -->
<!-- COLUMN ENDS: -->
<br><br>
* <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>
* <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>