Agile Principle:
Amplify Learning

Alternative name(s):

Project Learning
Rapid Improvement

Agile Manifesto


Amplify learning can be defined as a continuous learning process for refining a SDE (software development environment) Salo (2005). It is all about collecting knowledge and this will only happen when the team members will communicate and share ideas with each other in order to get good results. To improve the learning skills team members should have required communicative skills and as well as time management skills etc Thomas (2000). This will help in improving the business value and as well as improving the understandings of between different departments of the organization. Amplify learning process is a gradually learning process. It will also improve to highlight the problems for further development when there will be meetings with the product owner and customers and hence helps to satisfy the customers required needs.


Amplify learning encourages to share knowledge and information among team members. There will be more learning when the team is guided by a certain information. Amplify learning also includes what is to be addressed by expressing the concerned knowledge (Scrum Alliance, 2014). Hence there will be more face-to-face communication between the customers, testers and developers that provides more and more learning and also supports the distribution of information (ISTQB).

By regular distribution of knowledge and sharing ideas with other team members will counter the problems that usually arise. For e.g. if one of the important team member had to leave the work or had to go for some emergency he/she facing regarding health issues then definitely that shared information will help other team members to carry-on with the project without realizing his/her absence. In a nut shell Amplify learning is the agile roots for the Product Managers.

Links to other agile principles or practices:
Continuous Improvement
Continuous improvement is an integral principle of Scrum in this the Scrum Master Keeps an eye on how the things going and how the team members are managing work and what area needs improvement. Team members can also involve the Product owners to improve their work. There are also instructions in the Agile Manifesto like how to carry out the required developing software that can ultimately gives the best solution and every team members ends up in learning significant knowledge.

Communication is simply the act of sharing knowledge and ideas with other team members and face-to-face communication is considered as more efficient way of communication. Hence when there is a discussion involved between two team members then sharing of knowledge is there and hence team members will get a chance of leaning with each other.

Links to PMO knowledge areas (KAs):
User Involvement:
User involvement is all about participation and when the team members will involve then there will definitely be discussions and then team members will share knowledge and ideas with each other and it will help in learning.

Knowledge Management:
Knowledge Management is about spreading information within an organization. In this way it will help other team members to communicate with each other and share knowledge as well and sharing knowledge is also a part of Agile Manifesto values. Hence resulting in more and more learning which helps an organization to grow.

Problem Solving:
Problem Solving is about working together to figure out the best possible solution (Knippen & Green) and it may also involve the different problem solving stages. Agile Manifesto tells us that the team members that are working in the project and as well as the business involves should work daily collectively. Hence where there is problem solving there will definitely be learning involved.

Examples of use outside to IT domain:
If there will be a strong relationship between the students and the module leader then certainly there will be an exchange of information and this thing helps in learning more and more.

Nursing staff arrange meetings to share knowledge with each other and hence ends up in learning

Salo, O. (2005) Systematic Validation of Learning in Agile Software Development Environment. Available at: [Accessed: 12 June, 2014].

Thomas. (2000). A REVIEW OF RESEARCH ON PROJECT-BASED LEARNING. The Autodesk Foundation. 11 (2), 1-15.ONLINE available at : [Accessed 12 June 2014

Scrum Alliance (2014) Core Scrum — Values and roles. Available at: [Accessed: 11 June 2014]

ISTQB What is Agile model – advantages, disadvantages and when to use it? Available at: [Accessed: 11 June, 2014].

Knippen, JT, Green, TB, 1997. Problem Solving. Journal of Workplace Learning, Vol:9 Issue:3, PP: 98-99.

External links: