Model: A better development process - Udi Dahan
June 29th, 2022
(src: Course: ADSD - Fallacies of Distributed Computing)
role: Business Analist
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/e05147b8-55cb-42bb-b61a-3c74ed248980/8c2a06986a515721fb56cdc34861ab4c/11460613-distributed-system-design-slides.jpg)
role: Architect
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/8973aef9-ef6c-490d-8b11-e9c617f02adb/2f27f3836e44d6142c781d28636a10bb/11460613-distributed-system-design-slides.jpg)
role: Project Manager
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/9b2d5804-6500-4fea-8f84-639be932ec40/fe337bea1937415f3b09b94bd83202ba/11460613-distributed-system-design-slides.jpg)
Estimates
Given a
- well-formed team (worked together)
- with required skills (has done such things before)
- of size S
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/844ee895-576e-46c8-b020-ead30311b3d4/d41980a4175ad79b3722d38a4082563f/11460613-distributed-system-design-slides.jpg)
I like how estimates formulated this way, drive Proof-of-Concepts with the sole focus of getting better estimates.
This then lowers risk & variability by shifting that to the beginning of the project.
Kinda the same principle as Technique: Walking Skeleton for incremental development where you put the path-to-prod at the beginning of a project, because it's often the most variable thing.
This post was referenced in: