# IBC processes: how do we build things?

- We have gone from little process to pretty good processes built up over the last 3 years!
- planning call, mid iteration sync eng discussion (backlog, discussion on needs discussion issues), splitting teams workflows
- team members who can lead work and supporters
- shepherding os contributor work (external PRs)
- testing frameworks for releases (e2e, integration, compatability testing for multi release versions)
- process for internal audits, security audits, release process (alpha, beta, rc)

- Where to things hurt?
- adoption! both for product and engineering
- product<->workflow (feeds into adoption)
- channel upgrades (waterfall methodology more or less, spec/impl/spec/impl repeat)
- This influenced us to now do quicker cycles with POCs for technical validation of viability
- Examples: op-stack integration poc / the last two weeks of port router refactor (assess quickly, poc and determine outcomes)
- external org process disrupting engineering focus (ICF)