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

Add possible template for WG Scrum of Scrums #1424

Merged
merged 23 commits into from
Feb 2, 2024

Conversation

Kay-Zee
Copy link
Member

@Kay-Zee Kay-Zee commented Jan 30, 2024

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

  • General description of completed items
  • List of Closed issues

This sprint

  • General description of sprint goal
  • List of issues to be worked on

On Hold

  • List of issues on hold

Active Epics

  • Main epics that are being tackled, and currently active for this working group

Additionally, there are four general sections, being

  • Wins
  • Mainnet Uptime
  • FLIPs Tracker
  • Key Release Dates

---

### **User Experience** Greg
Objective:
Copy link
Member

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?

Copy link
Member Author

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.

Copy link
Member

@AlexHentschel AlexHentschel left a 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 😅

@AlexHentschel
Copy link
Member

general sections

  • FLIPs Tracker
  • Key Release Dates

We could move these to the top. Specifically Upcoming Key Release Dates would fit into the "Overview" section at the top and should also be at the top of mind for people looking at the doc.

Co-authored-by: Alexander Hentschel <alex.hentschel@axiomzen.co>
Co-authored-by: j pimmel <frankly.watson@gmail.com>
@j1010001
Copy link
Member

j1010001 commented Feb 2, 2024

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

@Kay-Zee Kay-Zee merged commit 3442b72 into master Feb 2, 2024
1 check passed
@Kay-Zee Kay-Zee deleted the kan/sprint-kickoff-template branch February 2, 2024 17:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants