bcgov / bcgov/cas-reporting

Post-MVP: Potential Opportunity: Small Aggregate list of facilities in the system

Open
#327 2 comments 0 reactions 0 assignees View on GitHub
attn: PO Service Design UX Research
Dominant language
No language data
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

#### Goal of Ticket
[Post-MVP]
User testing is needed to understand whether LFOs would appreciate having the ability to list all the facilities that are part of their Small Aggregate (L_c) in BCIERS. Would that be helpful for managing and reporting on the small aggregate? Or do they prefer to track these facilities and their emission in their own system?

#### Describe the task

Prepare questions for LFO users to learn more about this process and their needs.

#### Acceptance Criteria

- [ ] first
- [ ] second
- [ ] third

#### Additional context

Add any other context about the task here.

#### Definition of Ready:

Note: If any of the points are not applicable: delete or mark N/A

- [ ] Topic is clearly Defined.
- [ ] Task Description is Clear.
- [ ] People to speak to are identified (if applicable).
- [ ] Acceptance Criteria is Clear.
- [ ] Ticket Title is Clear.
- [ ] Ticket is reasonably Split up/sized.
- [ ] Value/Pain is Clear.
- [ ] Relevant Team Members are assigned.
- [ ] Ticket Estimated.

#### Definition of Done.

Note: If any of the points are not applicable: delete or mark N/A

- [ ] Rough User Stories Proposed.
- [ ] Follow-up Tickets created (if necessary).
- [ ] Findings are documented (if necessary).
- [ ] Reference docs/spreadsheets identified and indexed.
- [ ] Value Proposition Canvas (if required)

Contributor guide

No contributing guide indexed for this repository

Research direction

No files, tests, or entry points are identified. Start by defining the questions for LFO users about listing Small Aggregate facilities and tracking emissions, then document the findings, propose rough user stories, and create follow-up tickets if needed.

Written by the indexing model from the issue text.

Assessment

Domain
design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.