Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 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

  • 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

...

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

...