Versions Compared

Old Version 7

changes.mady.by.user Adam Stankiewicz

Saved on

compared with

New Version Current

changes.mady.by.user Adam Stankiewicz

Saved on

Key

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

...

Time

Item

Presenter

Notes

Adam Stankiewicz

[inform]

  • Had kickoff v2 with RaccoonGang last week Friday morning

  • They should be gearing up on getting familiar with the project code base throughout the week and posting ticket-specific questions for clarification on initial work throughout the week.

  • Scheduling weekly recurring sync meeting on Fridays, starting this week.



Adam Stankiewicz


[clarification] Is there a way to place a ticket in the desired column without needing to go through the full workflow?

Example:

PAR-312 is currently in “Needs Proposal” but want to move it to “In Engineering” (i.e., “Needs Engineer”) but can’t seem to move to “In Engineering” right away – can only move it to “Proposal In Progress”.

Workflow Issue / Resolution: Updated workflow to allow all “to-do” states to be transitioned to from any other state.

Is there a subset of Paragon tickets in the backlog that can be more easily surfaced to the Frontend Working Group?

  • Small pieces of work

  • New label that can be added to Paragon tickets (can be source of automation in the future)

  • Regular backlog grooming to figure out which subset of tickets makes sense.

  • PWG figures what could be picked up by FWG; FWG deals with prioritization and resourcing.

===

List of potential tickets:

Action items

  •  Adam Stankiewicz Create a new label for small pieces of Paragon work that’s ready to picked up by Frontend Working Group
  •  (Everyone) Think about which Paragon tickets might make sense to pick up by the Frontend Working Group (which tickets should get label to say it’s work to be picked up by Frontend Working Group).

...