# Way of self organization in decentralized development cycles
### What's the goal if this?
- Come up with a name
- Come up with a "manifesto"
- Define waht 10/10 success means
### Problems to solve
- Sill product development causing missed opportunities for similar or complimentary efforts to collaborate and share knowledge and learning
- Searchability - how do I know what efforts are in progress so I can contribute and/or learn
### Initial Manifesto notes
- Sharing Knowledge
- "It's more a Philosophy"
- It's about the people
- It's up to you if you want to contribute or join
### Process and Behaviours
- Need a timebox
- Serves as a start and end point of a plan (not the project).
- Celebrate learnings and wins at the end
- Ceremonies (on a cadence)
- Inspect and Adapt
- How to improve the process
- Research and Engineering Sync
- Coordinate upcoming R&D and add it to the backlog
- Celebrate Learnings
- Showcase what you have learned and share wins
- Delegated Project Master Sync
- Teams working on similiar, dependent or complementary can collaborate and share knowledge
- You don't want "projects" - They have a start and an end which is not desireable
- Parity practices project/dev anarchy
- Devs decide what to work on. If no ones works on something, it "dies"
- Roughly 45 devs
- Becoming more open is important
- Beauty and also strength of the space is that anyone can start an initiative
- Actually things are open, it's just sometimes hard to know where to look?
- For non-dev, technical docs are really hard to decypher. That's the biggest gap right now, and it has been around for years.
- It's not only about hte process, but also really about behaviors
- Communications is no. 1, process is no. 2
- Teams should still be enabled to self-organize
- Iteration is important. Any kind of decisions or aproachs is just an hypothesis that needs to be evaluated
- How do you get new people to join?
- They have another mindset
- They wait for or want to get permission to join and take part
- There are no users yet. So how do you validate?
- Async communciation si important, documentation, recordings since everyone is distributed globally or at least people should be enabled to participate globally
### What would a 10/10 be?
- Best practices guide / workbook for decentralized organisations
- Inludes scrum, kanban, agile, lean, XP
- Come up with a manifesto
- Guide sounds more definitive. Are we able to really achieve this? Is it even desirable? Manifesto is more philosophical.
- Communicate often. Even just to state things.
- What should that manifesto include?
- Enable "outsiders"/anyone to join - searchability, learn from each other
- (Some more things I wasn't able to catch during discussion)
- Decentralized Kanaban
- One area to show progress of development across all projects building for a better Ethereum. Creates an easy search source for anyone looking to contribute. Organic growth of roadmap. Can include multiple threads of work.
- Nested Kanban - starting top down. As you click an item, it drills down to another kanban board with it's own artifact type of a more decomposed effort of work.