Source Control History


Description:

Source control does not forget. We rely on this so we can revert to previous versions, but we can also use it to track frequently changing areas of the codebase.

Scores:


Ease of Use
Maintainability
Value for Money
Impact

Pros:

  • Readily available
  • Focuses effort
  • Used as required

Cons:

  • Can spark debate amongst engineers
  • Difficult to make sense of sometimes

Changes:

  • Change value for money to 4 stars (LLKD 2017)
  • Change Impact to 4 stars (LLKD 2017)

Comments

Post a Comment

Popular posts from this blog

What's all this about?

When someone says 'feedback', what's the first thing you think of? It's the retrospective, right? Similar to a magic trick, this is due to preconditioning that makes this a predictable answer. It may be our 'go to' feedback mechanism - but it is not the only one. It might not even be the best one, depending on your goal. We want to inspire you to look a little differently at your team and organisation. You work in a sea of feedback, some obvious - some not. Many teams consider only a small fraction of the available feedback to improve their behaviours. This website compliments a workshop which provides a simple process that allows an organisation to explore alternative and often ignored sources of feedback and decide how they might use and manage the information they uncover. The session is agile agnostic; it is not specific to any particular method. The inspiration for this was actually Top Trumps, a popular card game from our youth. For each type of fe
Read more