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 #4 - July 30 #44

Closed
10 of 17 tasks
msbtterswrth opened this issue Jul 25, 2024 · 8 comments
Closed
10 of 17 tasks

AEDP Sprint #4 - July 30 #44

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

Comments

@msbtterswrth
Copy link
Collaborator

msbtterswrth commented Jul 25, 2024

Sprint Goal

Other Priorities

Team Capacity

  • Morgan OOO 7/29 - 8/2
  • Christine OOO 7/31, 8/9 (half day), 8/13
  • Belle OOO 8/9, 8/12
  • Adam OOO 8/9
  • Lynn OOO 8/9 (half day)

Completed Items from last sprint

@msbtterswrth msbtterswrth self-assigned this Jul 25, 2024
@msbtterswrth msbtterswrth added this to the FY 2024 Q4 milestone Jul 25, 2024
@msbtterswrth msbtterswrth changed the title Copy of AEDP Sprint #3 - July 16 AEDP Sprint #4 - July 30 Jul 25, 2024
@msbtterswrth
Copy link
Collaborator Author

msbtterswrth commented Aug 8, 2024

@beckyphung, after chatting with the team, based on risks with completing all prototypes before sprint end, replacing sprint goal of #41 with #46 and targeting #41 for completion 8/16.

@beckyphung
Copy link
Collaborator

Thanks @msbtterswrth. Two requests:

  • Can you add the titles of the tickets in this descriptions, so I don't have to click into each ticket to know what we're working on?
  • Can you make sure the team adds updates at least daily, so I understand what work is being done? It's not clear to me what's at risk of being completed this sprint vs. not completed based on the tickets because there aren't any updates in them

@ACParker89
Copy link

Thanks @msbtterswrth. Two requests:

  • Can you add the titles of the tickets in this descriptions, so I don't have to click into each ticket to know what we're working on?
  • Can you make sure the team adds updates at least daily, so I understand what work is being done? It's not clear to me what's at risk of being completed this sprint vs. not completed based on the tickets because there aren't any updates in them

Hi @beckyphung - was this after morning meeting? I want to make sure the team has clear expectations!

@beckyphung
Copy link
Collaborator

beckyphung commented Aug 12, 2024

@msbtterswrth @ACParker89 This was before this morning's meeting, so that's why this is confusing. For the second bullet, I'd revise it to be:

  • Make sure updates added to tickets enough to understand what the current status of work is, any relevant artifacts/documents, blockers we're working through, etc. Doesn't have to be daily.

@msbtterswrth
Copy link
Collaborator Author

thanks for the clarification @beckyphung <3

@msbtterswrth
Copy link
Collaborator Author

Sprint's officially closed and everything that's pushed has been moved to the next sprint, please review/close unless you have any additional questions @beckyphung :)

@beckyphung
Copy link
Collaborator

@msbtterswrth Thanks for letting me know. I added some questions to some of the open issues from this sprint that were moved to the next one. Can you answer those q's/do any follow-up tasks before I close this sprint?

@beckyphung
Copy link
Collaborator

@msbtterswrth I'm going to go ahead and close this sprint, since we're working through the questions I added in our current issues right now.

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

3 participants