This repository was archived by the owner on Oct 24, 2023. It is now read-only.
Repository navigation
Agile Delivery
- James: Got to a great place with a coherent protocol (3)
- Tudor: Team work last week (3)
- James: Critically important doc to take to VCs and backers. We look like we know kinda what we're talking about. (1)
- Gavin: Printing the WP and putting it on the wall (1)
- Gavin: Getting an early version up on the website
- Neal Shah: Published whitepaper! Great work!
- Cais: Waiting so long to get to the one week of intense collaboration (5)
- Tudor: More team collaboration would have helped (2)
- Cais: Thinking we were 99% complete when really we were 70% complete (2)
- James: Limited feedback from Mike. Not zero, but not what he could have done.
- Cais: Anticipating feedback from people that showed no interest beyond initial interest
- Neal Shah: Not enough team members!
- Tudor: We submitted versions that were too incoherent to friendly reviewers
- Neal Shah: Probably would have done with some rollup expertise for the tech implementation
- James: Knowing when to put the pen down.
- Cais: Coming up with protocol ideas in real-time without sufficient time to challenge (4)
- Cais: Merge hell (3)
- Gavin: Having to watch Teams almost near continuously to know what was happening (1)
- James: Regressions
- Gavin: Rushing late on a Friday
- Cais: Uncertainty around funding pollutes thinking
- Waiting so long to get to the one week of intense collaboration; * Spoke about doing a page turner but it was not happening.; * WRT whitepapers, is perfection the enemy of good. How Agile do we want to be?; * It helped to name ethresearch - defined our audience and the quality of the thinking required.
- ACTION: collaborate more readily, team step in when someone asks for help. Take requests for help seriously.
- How comfortable are we doing our coding in public? Is the code different to the whitepaper in way we publish it?; * Better to define the direction ; * Flesh out the big unknowns in private at the beginning; * Default to coding in public; * Don't want to reveal how early we are
- Coming up with protocol ideas in real-time without sufficient time to challenge; * In the last week, dealing with protocol problems. Pressure was on and not ample time to think about it.
- ACTION: areas which are less worked through, let it bake for a day or 2 and give team members the opportunity to respond
- Merge hell; * Only needed one PR to fix; * Declared ourselves done too quickly; * Good to see the monolith broken up; * Relative page inclusion caused issues
- ACTION: last minute changes should be owned by an individual.
- ACTION: whitepaper structure discussion should happen earlier in the sequence. Putting WP on the wall helped enormously. Replicate when it comes to the design.