Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AEDP Sprint #2 - July 2 #18

Closed
9 tasks done
msbtterswrth opened this issue Jul 8, 2024 · 5 comments
Closed
9 tasks done

AEDP Sprint #2 - July 2 #18

msbtterswrth opened this issue Jul 8, 2024 · 5 comments
Assignees
Labels
Milestone

Comments

@msbtterswrth
Copy link
Collaborator

msbtterswrth commented Jul 8, 2024

Sprint Goal

Other Priorities

Completed Items from last sprint

@msbtterswrth msbtterswrth changed the title AE Sprint #2 AEDP Sprint #2 Jul 11, 2024
@msbtterswrth msbtterswrth changed the title AEDP Sprint #2 AEDP Sprint #2 - July 2 Jul 16, 2024
@msbtterswrth
Copy link
Collaborator Author

Becky, just shipping to you to signify sprint end, Should I go ahead and close or would you like to review first?

@beckyphung
Copy link
Collaborator

@msbtterswrth I'd like to review first before closing. Will do that now :)

@beckyphung
Copy link
Collaborator

This is good to close from my end. Two things:

  • Question: Could you send me a list of the recurring ceremonies? I'd like to see what else besides sprint planning I could attend, at least in the beginning as we we're working on developing our first patterns.
  • Comment: I know we discussed 'Service history' as a less prioritized pattern to work on. How do you/the team expect this pattern to be able to be generalized for wider-use outside of VA?

@msbtterswrth
Copy link
Collaborator Author

We have the following recurring ceremonies:

  • demo every second Wednesday at 4pm
  • retro every second Thursday at 12pm
  • sprint planning/refinement is currently one meeting (which may eventually split into two) every first Thursday at 2pm

Regarding the Service History pattern, we have had some discussions around whether service history should remain a pattern at all once prefill is completed, as we don't currently let Veterans edit this information on their profile because it comes directly from DoD. We will continue to explore this line of thought as this next sprint or two unfolds.

@beckyphung
Copy link
Collaborator

Thank you! I thought there were a lot more, so appreciate the quick list :). I'm fine with not going to retro for now, just going to demo/sprint planning. Just lmk if there are ever any actions you all need from me after retros.

Good to know with service history. Keep me updated!

@msbtterswrth msbtterswrth added this to the FY 2024 Q4 milestone Jul 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants