Comments by "TheEvertw" (@TheEvertw) on "Don’t Turn Your Development Process Into a NIGHTMARE" video.

  1. A heavy, review-intensive process gives a false sense of control to Management. But reviews are worth nothing when the team is building something that the end users are not satisfied with. As someone said (Dick Hamming), "it is better to solve the right problem the wrong way than the wrong problem the right way". That makes Continuous Delivery a far superior way of keeping the project on track than a heavy process. To illustrate, I recently witnessed a project that had a pretty heavy process, with lots of reviews. But the project needed a very costly re-design one year into it, because while it was required to support 1500 I/O points, it only managed to support one tenth of that. Testing on hardware proved the software to not be fit for purpose.
    2
  2. Dave Farley of @ContinuousDelivery has some interesting opinions on that. His idea is to never do pull requests, and just let anyone push their work into the main dev branch whenever they feel comfortable the task is complete. While initially shocked, I agree with his reasoning.
    1