Comments by "ForgottenKnight1" (@ForgottenKnight1) on "Where Agile Gets It Wrong" video.

  1. 18:15 - A succsessful merge is just that. It does not validate that the final result satisfies business needs. Nor does trunk development or pair programming. What validates a solution are the tests run against that codebase, no matter what the branching/merging strategies are. Are the tests covering all business cases ? Are the tests failing ? If yes, you go and have a look because you broke something. Maybe the break is intentional (requirements changed) or not.
    3
  2. Changes should not happen just for the sake of change. First, see if there is a need to change.
    3
  3. Here's a nugget of reality for you: you need both those situation for efficient and effective software development
    1
  4. In such an environment merges are done by backlog priority. Is my item more important for the business than yours ? Then, even if I finish after you, if youre code is not merged, I get to merge first because of that priority. In short, you apply a merging strategy based on the priority of the business.
    1
  5.  @deanschulze3129  Unfortunately ? That sounds like you like micromanagement.
    1