This diagram illustrates our catalog of agile practices, collected from the most popular agile methods. This diagram reinforces the fact that it is not recommended to consider exclusively the implementation of one agile method. What is important are the agile practices behind the methods and the synergy among practices. Thus, the recommendation is to apply all practices you can and in its major intensity. Below is the list of practices that correspond to the numbers shown in the figure. Click on the image to download a slide in which you can see the names of the practices focusing your mouse on a point (a practice) in the same image.
This image shows a possible grouping of practices in order to assess its application in certain specific areas of improvement. The practice #1 appears out of the grouping because it is meybe the more fundamental al general practice. Click on the image to download a slide in which you can see the names of the practices focusing your mouse on a point (a practice) in the same image.

Catalog of Agile Practices

translation missing: translation missing:
PRA1 To promote simplicity in all aspects. Providing the simplest solution that is satisfactory for the client. Lean, XP
PRA2 To address and deliver finished work incrementally. Kanban, XP, Scrum
PRA3 To make frequent deliveries of completed work units. Kanban, XP, Scrum
PRA4 To conduct planning meetings frequently. XP, Scrum
PRA5 To limit the work planned for a period based on estimations and team capacity. XP, Scrum
PRA6 To organize work in iterations, grouping work units which will be delivered together. XP, Scrum
PRA7 To avoid investing effort in work that is not committed and/or is not close to delivery. Lean
PRA8 To organize team’s work with focus on generating a good flow of finished work. Kanban
PRA9 To continuously manage work so that it is always properly prioritized. Scrum
PRA10 To limit Work in Progress (WIP), that is, the quantity of work units which are in some activity of the process Kanban
PRA11 To create small teams and try to mantain its members XP, Scrum
PRA12 To delimit the work context of teams ---
PRA13 To track continuously (with a frequency of days, not weeks) Kanban, XP, Scrum
PRA14 To conduct a short daily meeting with all team members XP, Scrum
PRA15 To visualize all work not finished which is in charged to the team Kanban
PRA16 To manage all the assigned work in an integrated way, at the level of each member or the whole team. ---
PRA17 To strengthen the communication between the client and the team. Client must be highly available for the team, if it is possible, in-situ. XP, Scrum
PRA18 To have only one person who properly represents all the client part, who take decisions about work priorities and explains the work to the team. XP, Scrum
PRA19 To conduct review meetings each time new work is released Scrum
PRA20 To promote self-organizing teams. The team should take decisions about how to get the result expected by the client. Scrum
PRA21 To have a boss with a facilitator and lider profile instead of authoritarian and controler. XP, Scrum
PRA22 To bring together all team members in the same place XP, Scrum
PRA23 To have a work place which gives advantage to collaboration among team members. XP
PRA24 To establish and communicate to the team the vision of the product or service, and reinforce it frequently. XP
PRA25 To get that the team, through its members, has all necesary skills to do the work. Scrum
PRA26 To get that team members can be in charge of different activities, hopefully of any of them, eventhough there could exists some specialists. Scrum
PRA27 To focus the work on the satisfaction of acceptance tests which have been agreed with the client. XP
PRA28 To document, but only what is strictly necessary. The effort invested in documentation should be profitable regarding the advantage that documentation provides. Lean
PRA29 To establish guidelines for adequately managing the rework. Lean
PRA30 To have a leader/consultant in process improvement available for the team. XP, Scrum
PRA31 To apply recommended standards for the technical work. XP
PRA32 To conduct retrospective meetings in order to evaluate the the process and support the continuous process improvement. Scrum
PRA33 To agree and define what is meant by work completed, for each activity performed on a work unit as well as for the releases delivered to the client. Scrum
PRA34 To get that some work or activities (in some work units) be performed jointly by two or more members. XP
PRA35 Do not abuse of overtime, negotiate at the right time to avoid it. XP
PRA36 To reduce interruptions or context changes affecting the work of team members. Lean
PRA37 To establish a discipline of productive meetings. ---
PRA38 To automate testing to ensure that the product maintains the desired behavior while some changes are made. XP
PRA39 To postpone until the last moment the assignment of responsible of some activity. ---
PRA40 To continuously integrate the work finished in the new version of the product. XP
PRA41 To promote that team members know all parts of the product or service which they are in charge. XP
PRA42 To continuously improve the internal organization of the product for facilitating its maintenance. XP