Versions Compared

Key

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

...

We need to decide how to distribute the cost accounting work.

Discussion items

ItemNotes
Resources

Jira Legacy
serverSystem JIRA
jqlQueryfilter=10170
serverId50130123-f232-3df4-bccb-c16e7d83cd3e


Questions
  • Who on the team is best suited to this work?
  • Is the work ticked the right work based on Mercury MVP decisions?
What Joe learned
  • Finish short leash deploy
    •  
    • Not in scope for Mercury:
      • Jira Legacy
        serverSystem JIRA
        columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        maximumIssues20
        jqlQuerykey in (RHOL-137,RHOL-814,RHOL-815,RHOL-816)
        serverId50130123-f232-3df4-bccb-c16e7d83cd3e
         
  • Adjust costs based on implementation of short leash deploy
Remove phlo-limit
  • Jira Legacy
    serverSystem JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId50130123-f232-3df4-bccb-c16e7d83cd3e
    keyRHOL-437
RHOL-17: define contract default minimums
  • Assure in the big deploy contracts are run at the minimum cost
  • Mitigate against contract flood
  • May not be need if covered by short-leash deploy
RHOL-132: 
  • Likely covered by RHOL-767
  • Closed during meeting
Resourcing
  • Ovidiu ~2 weeks out from being complete on F refactoring work
  • Priority for cost accounting work is completion of short-leash deploy, RHOL-775
    • Idea to have Joe further specify the open tickets for short-leash

Action items

  •  Joseph Denman start work to specify the open tickets in the short-leash epic
  •  Kelly Foster follow up with Kent and Arthur for the resourcing questions
  •  Ned Robinson and Deanna Duke start setting expectations for feature complete date based on needed cost-accounting work.