CITZ-IMB-Playbook

CITZ-IMB Modern Application Playbook

Introduction

OCIO-ES-IMB is the Ministry of Citizen’s Services Information Management Branch, its mandate includes:

• Engaging with Ministry Business Units to support their IM/IT project initiatives
• Providing IM/IT Application Management Services including support and operational maintenance for over 80 applications on behalf of CITZ Ministry Business Units
• Providing STRA and PIA services for the Ministry
• Providing Infrastructure Management Services for Ministry clients
• Operating the IMB Support Desk
• Reporting to the Ministry CIO (MCIO)

To support IMBs overall strategic IM/IT initiatives a Modern Application Playbook is required that will aid in Ministry Business Units in their new application development journeys. To support the playbook a 12-Factor compliant Capstone2020 Progressive Web Application is being developed to demonstrate the Modern Application Playbook.

Problem Statement

The OCIO-ES-IMB does not have a consistent playbook to aid in the development of Modern Applications by Ministry business units.

Hypothesis

If we have a modern application playbook our stakeholders, partners and vendors will have a set of tested, repeatable patterns that will guide their journeys in the development of modern applications from product ideation through to the sustainment lifecycle to aid in consistent and efficient use of limited resourcses that make use of current best practices.

Goal

The goal of the Capstone2020 project team is to create actionable guidance for Ministry Business Units developing Modern Applications.

Objectives include:

• Provide the reader with a collection of references to tested methodologies, tools and best practices.
• Guide modern application development
• Demonstrate creation of a system that supports the BC Governments Digital Framework.
• Provide "plays" that describe valuable patterns that project teams should consider as part of their digital product management lifecycle.

The Plays:

1. Ideate solutions that meet the needs of business units
2. Successfully navigate the Ministry project intake process
3. Building your Team
4. Ready, Refine, Sprint
5. Transition to Operations
6. Continuous Product Improvement
7. Sustainment Lifecycle

Project Status

BETA

Development

GitHub | Jekyll | Ruby

We are actively adding new features and enhancements.

Read about our design theme here.

Read our development guide here.

Contributing Guideline:

Contributions are welcome, but please review this document before making any change

• Best Practices:

  • Be careful when using/passing/storing credentials
  • Maintain quality

• Pull Requests:

  • We use the Forking process in our development. Click Here for more details and best practices
  • Please, add brief description of what's been added/fixed, what issue was addressed
  • Reviewers either set the status to 'Approve' or 'Request Changes'
  • Once approved, submitter Squash and Merge (not just Merge) code (kicks off Github Actions)
  • Submitter ensures all Github Actions completes successfully

• Git Commit Messages style-guide:

  • Use the present tense ("Add feature" not "Added feature")
  • Use the imperative mood ("Move cursor to..." not "Moves cursor to...")
  • Limit the first line to 72 characters or less

License

Copyright 2020 Province of British Columbia

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

   http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

Lifecycle

The project is in a reliable state and major changes are unlikely to happen.