Scaling up
adding human resources to a late software project makes it later
Brooks's law
Why?
- "ramp up" time
- Communication overheads
- Limited divisibility of tasks
Why?
- "ramp up" time
- Limited divisibility of tasks
- Communication overheads
Dependencies
There could be dependencies between stories
We could increase number of stories by doing stories from different contexts
Bounded context
It maybe looks like single thing...
Why?
- "ramp up" time
- Limited divisibility of tasks
- Communication overheads
Types of dependencies
- Code dependencies
- Infrastructure dependencies (frameworks, servers, deployment, etc)
- Requirements dependencies
Code dependencies
are explicit
(or could be)
note: there is limitations on who can work with code (technology stack) but this just increases "rump up" time
What we do to manage code and infrastructure dependencies
- Continuous Integration
- Monorepository
- Infrastructure as code
Requirements dependencies
are implicit
We don't know...
We only know what would be bad idea
