Tailoring the specifications to address the unique needs and challenges of different organizations or use cases can enhance the relevance and practicality of the "identity" building block.
Description
Activity
Rachel LawsonJune 22, 2023 at 10:23 AM
the published use-cases are at . As has already indicted a route to add your contribution to them, I think this particular issue has reached a conclusion so I’m going to close the issue - thanks for raising it!
Ott SarvJune 15, 2023 at 7:58 AM
I don't think I've come across the specific use case definition (GOVSTACK internal definition) yet. , could you perhaps guide me to where it's outlined? After reviewing it, I'd be more than happy to provide my additional thoughts and feedback.
Jaume DUBOISJune 15, 2023 at 7:22 AM
Additionally, I see there a contradiction with whole of a government approach in which we should build an infrastructure to enable third parties to build solutions on top handling their use cases. As mentioned in yesterday’s PC, country engagement should help countries to build infrastructure pieces rather than building use cases. For example I see a strong buy in by Togo which includes GovStack specifications as part of it interoperable framework, but the Digital Governance team which is behind won’t actually build the solutions on top instead they will support 3rd party public or private services providers to build themselves the solutions. I’m building vertical use case with countries would lead to create siloed instead of infrastructures. I have highlighted that yesterday and will illustrate it again in the TC as I think we have here areas of improvement.
Jaume DUBOISJune 15, 2023 at 7:15 AM
use cases have to come from the field, country engagement is a good channel for that and building block working group are also as our members have experience of operational systems. Products committee is there to collect those needs through different channels, also make a due diligence on them on my humble opinion and prioritize them.
Ott SarvJune 14, 2023 at 6:13 PM
, your active efforts to diversify the application of building blocks through various use cases are encouraging. I believe that a parallel decomposition process will be beneficial in helping GOVSTACK achieve its goals and manage the increasing complexity.
Ticket:
This approach not only expands the use cases but also ensures that each building block retains its functionality, comprehensibility, maintainability, reusability, and simplicity.
Moreover, as the aim is to broaden the scope of the building blocks, it is crucial always to consider the specific context of each use case. Not every solution will fit every problem; the nuances of each organization or use case demand customized adaptations.
The same approach should be applied to the few larger building blocks (BBs).
Rest assured; I will reach out if I come across any potential use cases that could contribute to the GOVSTACK mission.
Details
Assignee
Rachel LawsonRachel LawsonReporter
Ott SarvOtt SarvPriority
Medium
Details
Details
Assignee
Rachel LawsonReporter
Ott SarvPriority
MediumChecklist
Open Checklist
Checklist
Open Checklist
Checklist
The specifications for the "identity" building block (IDBB) currently lack tailored approaches for diverse use cases. To increase relevance and practicality, a more customized approach could be adopted to address specific needs and challenges of various organizations.
Recommendations:
Use Case Inclusion - Actively seek input from organizations that plan to use the IDBB to identify and understand their unique needs. Use this feedback to create use case-specific specifications that address these unique scenarios.
Consolidation of Use Case Information - Consider integrating the use case-specific information from other GovStack documents directly into the IDBB specifications. This can create a more comprehensive and user-friendly resource, minimizing the need for users to cross-reference multiple documents.
Regular Review and Updates - Institute a process for regular reviews and updates of the IDBB specifications, with a focus on improving the inclusion and clarity of use case-specific specifications. This will ensure the IDBB remains relevant as organizational needs evolve and new use cases emerge.
Outreach and Collaboration - Engage in a proactive dialogue with the wider community of users and stakeholders to ensure that the IDBB evolves in alignment with real-world needs. This can include forums, webinars, or surveys to gather feedback and ideas.
Case Study Development - Create case studies showcasing successful implementations of the IDBB in various use case scenarios. These can provide practical insights and serve as guidance for organizations seeking to implement the IDBB in their unique contexts.
Jaume feedback: IDBB already include BB specific use case, cross BB use cases are defined in other GovStack documents.