Please enable JavaScript.

Coggle requires JavaScript to display documents.

BDP Release Retro (People (Negative (Knowledge Share (Not understanding…

- - - - Developers are not familiar with the code,
        and make little effort to gain the required
        level of understanding
    - - There is little opportunity to push-back on changes earmarked for a release
    - - Not all developers follow the existing coding patterns
      - Developers perform very limited changes, does not leave codebase in a better space than found
    - - There seems to be a lack of urgency around the timely delivery of items in order to start testing
    - - There are limited resources to perform testing
      - The level of knowledge is limited, impeding the efficiency of testing
      - There is a not enough regression testing
    - - There is only one resource responsible for this
      - This is not a shared responsibility
    - - Not understanding the architecture of BDP
      - Not understanding the Process Flows in BDP
      - Not listening to (following) advice from other developers
      - Not participating in / attending knowledge share
  - - - There are developers who take real pride in their own work
    - - There is a number of individuals who are always stepping up and assisting with release issues
- - - - Allocate specific teams to work on scope for a particular release
    - - Branching builds as a journey
      - Merging Strategy
      - Responsible person/team with context
    - - Not clear which machines have
        which Release (UAT and SIT)
      - Deploying one release to another LAN
        to troubleshoot without clear communication
    - - The relevant schedule for the
        releases need to be more visible
    - - There is only one resource (with Prod access)
        who manages this
  - - - There is value in the sessions
        we have hosted thus far