Initial roadmap

Our product roadmap is a summary of the vision and direction for the forms design and submission products

Prior to the common components formation - the showcase team within NR developed and launched the original Common Hosted Forms service, leveraging the opensource product Form.io. NR team are a valuable partner for our team.

Past work completed and released is found in their GitHub repositories:

CHEFS: https://github.com/bcgov/common-hosted-form-service/wiki/Product-Roadmap

CHES: https://github.com/bcgov/common-hosted-email-service/wiki/Product-Roadmap

CDOGS: https://github.com/bcgov/common-document-generation-service/wiki/Product-Roadmap

COMS:  https://github.com/bcgov/common-object-management-service/wiki/Product-Roadmap and COMS - Timelines

The high level epics the forminators are focused on and have recently completed are:

• Team Formation and Management:

  • Workshops and coaching the team on Agile and Scrum best practices

  • Utilizing Agile platforms and best practices including JIRA and Confluence as information radiators and work organization

  • Facilitating Agile maturity through leveraging different Agile framework including Kanban, Scrumban, and SCRUM frameworks

  • Self-organizing Scrum teams with dedicated Product Owner and Scrum Master and Developers

• Organization and management

  • New Jira kanban instance created to manage workload assignments

    • Forminators - Agile Board - Jira (atlassian.net)

  • New public instance of Confluence created to enable on line collaboration and FAQ/guiderail/pattern documentation. Includes stub pages for related Common Components teams

    • Forms Design + Submission - Forminators team landscape - Common Components Program - Confluence (atlassian.net)

• User feedback & iterative feature improvement stories/user improvements

  • User improvements: First Pull Requests merged to prod CHEFS

  • PR and branching collaboration with Showcase as gatekeepers

• Technical debt focus:

  • Branching strategy Investigations: tooling capabilities to future proof/readiness for any pivot from NR team in future

  • standardizing components: PoC/research

  • Stability of the platform

  • Scalability: Handling high usage

  • Performance

  • Ease of development

  • documenting limitations of opensource/forms.io

  • User documentation: Component description and help functionality (OOTB first, custom second)

• DevOps - tooling and methodologies. Pipeline, PRs and CI/CD frameworks, documented branch protection policies and procedures

• github actions flow (CI/CD decouple from jenkins approach)

• UX design

  • Govt of BC standardization

  • Pivots (Standardized design)

  • UX prototypes to speed up research on UX

  • Research

  • User personals and Journeys

  • Document roles & user flow on confluence

• Platform: library and back end

• Building collaborative partnerships

• Customer Inception: Health MVP pre work

Open

These themes and epics are regularly deconstructed into features and stories, and are managed via our kanban board within Jira here:

Forminators - Agile Board - Jira (atlassian.net)