Problem Breakdown

Problem: AR 5 needs to be investigated

Solution:

• Go through the spreadsheet and create tickets for each of the fields.
• Look through tickets and figure out what needs updating.
• Help update those tickets.

Problem: Inaccurate Tickets/Project View

Solutions:

• Person responsible for getting reports and updating PM tools
  • Not a Dev
  • Short standup meeting to get updates
    • Project based
  • Tools are up to user
• More projects.   
  • Projects should be used to indicate work grouping
  • That way, epics can be used to break down digestible portions of that work.
  • What makes a good "Project" group?  
    • Obviously, AR5 vs AR4
    • New Features?
    • Maintenance vs upgrades?

Problem: Inaccurate Sprints

Solutions:

• Correctly size sprints
  • One size doesn't fit all
• Per project sprints
• MVP for things at the end.
• Correctly sized tickets
  • What does this mean?
    • smaller
    • able to be tested

Problem: Inaccurate/incomplete requirements

Solutions:

• Better requirement meetings
  • Include developers
• process for having more requirement meetings as needed.

Problem: What is a good ticket?

Solutions:

• Size
  • Too broad? Too Narrow?
• Does it answer a question?
• Does it have a way to test it?
  • (Acceptance criteria)

Problem: How do you ticket unknowns?

Solutions:   

• Ticket the edges of the "fog"?
• Break down tickets until you have something that can be acted on.