Product Team Profile

您的浏览器中未启用 JavaScript，因此无法打开此文件。请启用 JavaScript，然后重新加载。

The questions below are designed to guide a conversation about a specific application development project, in order to highlight risk based on the critical success factors for delivery. Alignment does not guarantee success but significantly reduces the risk of failure.

Please do not provide any third party or personal information in your responses as this information may be stored on servers located outside of Canada. Participation in the use of Google Forms is voluntary.

Ministry name

Team Name

Application/Project

Please enter a unique name for your application or project - you'll use the same name on each form for this project

Product Owner email address

Business Outcomes

What is the business objective of the project? Can the ministry team specify 1 to 4 outcomes that the project will achieve? Each outcome to be stated as: increase, decrease or sustain something that is responsive to the verified need of one or more specific target groups. To protect your own privacy and the privacy of third parties, please do not include any personal information about yourself or others in these fields.

Application Purpose

What is the application or information system your are building? Who are the users? What will it do to enable the achievement of the desired outcome(s)?

Cloud Services Required

What are the key public cloud services required? (eg: Virtual Machines, containers, serverless ..)

GitHub repositories

Please provide links to all GitHub repos you'll be using to manage your code, high level documentation and diagrams:

Target Production Date

When do you need the application to be live in production?

年

月

日

Current requirements for pathfinding in public cloud - please check all that apply

We have ADM sponsorship for this initiative

We have a strong rationale for using public cloud services for this initiative

We are OK with working in an environment under flux

We have an executive endorsed continuity plan for this application

We have approval for estimated operational funding for cloud resources

Our MISO is engaged and STRA is underway

Our MPO is engaged and will ensure that the PIA for the business program covers this initiative

Product Owner Profile

A consultant or executive with limited contact with the team

A government resource who has other responsibilities

A dedicated government resource

清除所选内容

Product Owner Experience

How many years of experience as a Product Owner?

Dedicated team

How many other applications/products is the team supporting?

Cross-functional roles

Does the team have cross functional roles defined that cover: Scrum Master, UX Researcher, UX Designer, Developer (Solution Architect, Back end, Mid-tier, Front end), DevOps Specialist/ SRE?

3 or more roles filled external to team (people on some other team) OR 3 or more roles assigned to a single team member

At least 6 roles covered and clearly assigned to named team members AND no more than 2 roles filled by external to team resources AND no more than 2 roles assigned to a single team member.

All 8 roles covered and clearly assigned to named dedicated team members AND no more than 2 roles assigned to a single team member.

清除所选内容

Community participation

Is the Team connected to the greater BC Government Communities of Practice?

The team operates in a silo, custom builds solutions from scratch or from Google searches

The team sends a team member to attend regular Community of Practice, participates in BC Gov online communities, asking questions and involving in discussions around their technical and agile approaches.

The team innovates and shares back to the community via presentations at Community of Practice events and Lunch & Learns. The team maintains one or more community usable products over which they take a Stewardship role.

清除所选内容

Build and deployment process

Is the build and deployment process automated?

Some automation but manual intervention needed.

Automation including test and security.

Full automation including test and security

清除所选内容

Resource provisioning

Is public cloud resource provisioning scripted?

No, all manual through the cloud provider console.

Majority infrastructure provisioning as code, some cloud console access needed.

Full infrastructure provisioning as code and versioned with the application.

清除所选内容

Application lifecycle (part 1)

Is the full lifecycle of the application in scope?

No. Only concerned about development and deployment.

Some attention to logging, resilience, monitoring, security, updates and patches has been planned/implemented but many processes are manual.

Full lifecycle is automated including logging, resilience, monitoring, security, updates and patches

清除所选内容

Application lifecycle (part 2)

Will the team be doing continuous small releases

No. Likely a few large releases and hand over to a maintenance team.

Planning releases every few weeks and same team will maintain the application.

Yes. We'll do continuous small releases and the same team will maintain and continuously improve the application.

清除所选内容

Application architecture

Is the application Cloud Native?

No. Monolithic architecture or requiring VMs and stateful infrastructure (services).

Container deployment, some API’s. Majority stateless services, some stateful services.

API’s, Container and or serverless run time, stateless services.

清除所选内容

Common tools and resources

Does the pipeline, app components and run time environment use common BC Government tools and resources?

No. Bespoke, proprietary of uses tool/ components not adopted by the BC DevOps community

Some alignment with exceptions that are well understood and justified.

The full stack is well understood and aligned with the BCDevOps common practices.

清除所选内容

Source code management

Is the code Open?

No, either proprietary or unknown, needs handoff to be usable.

Some closed source portions until launch/ go live - then open, requires reading of documentation to use.

Open Sourced. Bonus for residing in github.com/bcgov. Code is ready for anyone from the public to pull down and go.

清除所选内容

Use of open frameworks

Is the code using open frameworks the BC DevOps community is familiar with?

No; either niche/ esoteric, proprietary or legacy/ unsupported.

Open frameworks with downward trends in popularity.

Open frameworks with upward trends in popularity.

清除所选内容

Code maintenance

Is the code maintainable?

No, it is not reviewed, consistent, or simple at a glance. It can only handle minimal proof of concept workloads.

Manual reviews as part of the process, application can handle initial workloads only.

Full automation of linting, static code analysis, API testing, application performance monitoring and productive pattern analysis are in place. Code design can accommodate future growth.

清除所选内容

提交

清除表单内容

切勿通过 Google 表单提交密码。

此内容不是由 Google 所创建，Google 不对其作任何担保。举报滥用行为 - 服务条款 - 隐私权政策

表单