Sprintly Spaceshot Design Briefs
Status | Draft In review Accepted Rejected |
---|---|
Proposer(s) | @Tommy Neidlein |
Date Submitted for Review | 10/12/2022 |
Date of Implementation |
|
Description of Proposal
https://purdue-space-program.atlassian.net/l/cp/RNWF5s11 is a newsletter for general members and organizational memory purposes that outlines the major accomplishments of each sprint from each primary team, in addition to any blockers that are preventing tasks from being completed (especially if those blockers are related to another primary team). Each primary team should strive for no more than a paragraph every sprint cycle. It serves as a good way for general members to stay up to date on the big picture elements of the project, without needing to spend an hour going through Jira boards. It will be posted at the end of each 2 week sprint in the general slack channel.
Pros and Cons of Implementing the Proposal
Pros | Cons |
---|---|
Increased communication of project progress | More work for systems reps or leads (up to them who does it) |
More accountability for teams, enables a gut check where teams can see where they should be at |
|
Longer organizational memory about when major design decisions were made, and why they happened |
|
Purpose of Proposal
Currently, a lot of new and general members feel detached from the big picture aspects of the project. In order to increase retention (and preserve documentation on technical decisions), more of an effort needs to be made to connect the people doing the bulk of the work to the rest of the team. It also reduces the team’s dependence on meetings where leads need to talk about what they are working on. This way, the time a lead would spend talking about big team updates can be spent getting work done and pushing the project forward.
Plan for Action
Leads need to decide that this is something important, and will have to either delegate the job to their systems rep or set aside the time each week to do it. It will be tested for a month then reassessed.