Notes from "Continuous Learning" article

README.md

Exzerpt from the article "Continuous Learning"

by Joshua Kerievsky

https://www.industriallogic.com/wp-content/uploads/2005/09/ContinuousLearning.pdf

• Continuous learning is important to improve the process and keep up with new technologies.
• For example, the software can be simplified by using better libraries.
• Continous learning should result into a monetary return on investment.

Learning repository

• Write down lessons learned in a web based tool like a wiki.
• Needs to be easy to use.

Study groups

• A discussion of important technological subjects like posts in the learning repository, books and articles
• There should be no lecturer but it should be a group learning experience.
• Should happen regularly, e.g. one a month or once per iteration
• Just like refactoring, the habit should be kept even under the pressure of release dates.
• Attendance should be optional
• Read more: Pools of Insight: A Pattern Language for Study Groups

Iteration retrospectives

• Reflection on what went well, what was learned and what should be improved.
• The result should be concrete ideas about process improvements.
• Read more: Project Retrospectives: A Handbook for Team Reviews