-
Notifications
You must be signed in to change notification settings - Fork 158
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
Add possible template for WG Scrum of Scrums #1424
Conversation
--- | ||
|
||
### **User Experience** Greg | ||
Objective: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will this change from Sprint to sprint? How does it differ from sprint goal?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I meant this to be a place to be constantly reminded of the cycle objective. Let me update that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 Thanks for putting this together. Looks great.
Added a few minor suggestions for improving the content structure in the doc. For example, currently Incidents
is a sub-section of Team Wins
😅
agendas/2024/sprint-kickoff/YYYY-MM-DD-Flow-Sprint-Kickoff-Template.md
Outdated
Show resolved
Hide resolved
We could move these to the top. Specifically |
Co-authored-by: Alexander Hentschel <alex.hentschel@axiomzen.co>
Co-authored-by: Alexander Hentschel <alex.hentschel@axiomzen.co>
agendas/2024/sprint-kickoff/YYYY-MM-DD-Flow-Sprint-Kickoff-Template.md
Outdated
Show resolved
Hide resolved
agendas/2024/sprint-kickoff/YYYY-MM-DD-Flow-Sprint-Kickoff-Template.md
Outdated
Show resolved
Hide resolved
agendas/2024/sprint-kickoff/YYYY-MM-DD-Flow-Sprint-Kickoff-Template.md
Outdated
Show resolved
Hide resolved
agendas/2024/sprint-kickoff/YYYY-MM-DD-Flow-Sprint-Kickoff-Template.md
Outdated
Show resolved
Hide resolved
agendas/2024/sprint-kickoff/YYYY-MM-DD-Flow-Sprint-Kickoff-Template.md
Outdated
Show resolved
Hide resolved
agendas/2024/sprint-kickoff/YYYY-MM-DD-Flow-Sprint-Kickoff-Template.md
Outdated
Show resolved
Hide resolved
agendas/2024/sprint-kickoff/YYYY-MM-DD-Flow-Sprint-Kickoff-Template.md
Outdated
Show resolved
Hide resolved
agendas/2024/sprint-kickoff/YYYY-MM-DD-Flow-Sprint-Kickoff-Template.md
Outdated
Show resolved
Hide resolved
agendas/2024/sprint-kickoff/YYYY-MM-DD-Flow-Sprint-Kickoff-Template.md
Outdated
Show resolved
Hide resolved
Co-authored-by: j pimmel <frankly.watson@gmail.com>
FYI all, I took this file and created a copy for 2nd Feb here: https://github.com/onflow/flow/blob/master/agendas/2024/sprint-kickoff/2024-02-02-Flow-Sprint-Kickoff.md |
In the interest of bringing more clarity of what's happening across the team on Flow, we are aiming to consolidate the sprint kick-off across all working groups on Flow. This will help represent all engineering work being tackled by the the core Flow Foundation engineers, and provide clarity both across WGs and with external on-lookers.
The idea is that each WG has their own section, with the following format:
Objective:
Done last sprint
This sprint
On Hold
Active Epics
Additionally, there are four general sections, being