LCO Wrapup Management Decisions
Mar 5

Present

• Matt
• John
• Susanne
• Bill
  
  

Notes

• Initial classification system needs to allow for classification perspectives of developers ("but it's not done") and management ("i don't care, we can take the hit")
• Distinction between work remaining
  • for LCO
  • to reach LCA
• Just because work was expected to be needed doesn't mean that it still is
• Any task that is articulated as remaining should be characterized in terms of its contribution to next phase
• "Task" terminology
  • WBS
  • Architectural
  • Jira (John almost always talks about these)
• Matt is looking for numeric report of tasks in each category
  
  

CEI
36 tasks total

• 27 fixed/complete
• 2 duplicates
• 1 dropped wo impact
• 1 dropped may impact (#6)
• 3 work remains (35, 37, 38)
• 4 lco prep rather than actual technical work
  • 2 reporting
  • 2 prep for lco
    
    

Recommendation: Complete

COI
28 tasks total

• 21 fixed/complete
• 1 dropped wo impact
• 2 dropped may impact
• 4? work remains 
  
  

Recommendation: Complete with one lien task, other tasks recharacterized as LCA tasks

DM
98 tasks total

• ~40 prototypes tasks included
  • 13 prototype tasks incomplete
  • all remaining prototype tasks fixed/complete
• "real" tasks
  • 4 dropped wo impact
  • 4 dropped may impact
  • no work remains
    
    

Recommendation: Complete; may recharacterize dropped w/ impact as LCA tasks

SA
23 tasks total

• 15 fixed/complete
• 1 duplicate
• 0 dropped wo impact
• 0 dropped may impact
• 7 work remains 
  
  

most work remains is actually instrument agents

Recommendation (provisional): Complete w/liens

Use Jira as annotational conversation

[John taking notes on specific tasks in Jira]

Subsystem level recommendation:

• Recommendation
• Recommendation pending resolution outstanding issues
• No recommendation - need further discussion