Adopt a formal but flexible project life cycle #16
Labels
Input wanted
Issue needs more discussion, clarity or specificity to be completed.
suggestion
Have an idea for how OpenOakland could work better?
Description
Historically, OpenOakland has had various processes and standards for intaking and executing project work. Over time, those processes have become less formalized and more opaque to volunteers and leadership. Without a clear point of view on the project life cycle, an "anything goes" approach has taken root. The result is a lack of efficiency, oversight, accountability and, on occasion, harm to the community.
The goal
Define the project life cycle, including major phases and milestones, and required and recommended activities. This structure needs to balance flexibility and autonomy for volunteer teams with accountability to the public, and need to be accompanied by supportive resources that make the work both manageable and fun. We have an opportunity to help Oaklanders understand and define what equitable tech can look like in our city.
Reference material
The text was updated successfully, but these errors were encountered: