Agile practices - Crop Guide

Happening	Cutting recommendations
Large project team	The large projects into several small reconstruction projects. First try technology pilot project, and then execute the implementation of the project. Consider frequent releases fewer features to create a small project team. Consider the team cut to include only the key core members. Usually overstaffed hinder the process but will be helpful. Reduce the size of the team can reduce internal turbulence and costs. The large team into multiple small team, and use of project management synchronization and coordination. The use of agile and lean project management to organize large-scale projects. Consider large-scale agile or lean frame framework such as DA, SAFE or LeSS. Each team can provide some useful perspectives, and bear the risk and the implementation of process pressure / cost
Distributed teams	Many projects will include (some of) dispersed team members. Instant messaging, video conferencing and electronic version of the team will help to ensure smooth communication. If the team remains stable, build more efficient exchange of future remote-face meeting as soon as possible. Easier to build trust when face to face, to improve the quality of the dialogue. If the lack of facial expressions and body language communication in the remote participants during the conference, please consider recycling questions to confirm their participation and whether the acceptance of the decision. Also, consider using agile methodologies based on iterative. If team members area where the difference is large, avoid using an iterative manner throughout the project, but to encourage more private meetings more frequently (every two to three individuals)
Some safety-critical products may require additional documentation and compliance checks recommended by the current agile process	Agile methods can still be used in these environments, but also the need for other appropriate compliance review, and certification of the document required in the field. In this case, the document may need to be delivered along with the completed function. Only after the completion of the document function is completed. Consider using a hybrid approach (a variety of agile methods), according to more stringent requirements for the product environment, the benefit from agile brought in to improve collaboration and communication. Aviation system developers and pharmaceutical companies adopt Agile methods in combination with their other process, make full use of these advantages and retain the corresponding control.
Steady demand and implementation process	You are really need agile methods? If the demand uncertainty is low, slow change speed or execution risk is very small, may not need the entire Agile methods. Despite the increase in the level of transparency and collaboration on any project has a benefit, but some iterations agencies and review cycle may be superfluous. If the build / feedback cycle can not be found on a regular basis or optimization requirements, consider extending the duration of time to reduce the impact on the cost of the review. If the project changes during the design and development speed very fast, but delivered to customers is a deterministic, repeatable process, using a hybrid approach may be appropriate life cycle model makes more sense in every project phase
Team functions located within the functional organization silos	Agile is based on the concept of cross-functional teams. Consider allowing these employees to create cross-functional teams on their own, without resorting to management interventions, and to understand its consequences. If you can recognize functional areas by organizing and rewards reward system, consider the first change to change the system. Unless there is some impact on their pay, employees will act for the benefit of the product or team
Transparent will fear	Agile will create a culture of transparency: Employees will demonstrate and share their achievements during the entire development. Share this way intermediate deliverables, and openness to the success or failure and the current state of the attitude that is the reaction transparency. Transparent takes courage. By using a white board or the state, showing an exemplary guide and transparency in the decision-making process
Many team members lack the technical domain knowledge	Agile initiative will improve the team and play to their strengths, to make local decision-making related content, such as task scheduling order, and which approach in solving problems. If the majority of team members lack experience, consensus-based approach can be problematic and lead to rework. Therefore, for these teams, before acquiring the necessary skills, some extra help "distribution" and "guidance" aspect may be necessary. In other words, do not blindly adopt agile methods, guidance from authorized inexperienced team to try to solve all problems. Consider the ability to build centers to provide help and guidance to accumulate domain knowledge
Lack of management support	If the lack of management support, the team will encounter a conflict between the quick thinking modes and methods of thinking and methods of forecasting more. Find common ground and make improvements based on organizational needs, and then use experimental and review progress. Consider management education / training. Consider explained in terms of Lean Thinking Agility: short period, small-scale, frequent review, regression and slightly improved
Agile terminology and language not suitable for tissue culture	If not agile language on the modification of terms, so that employees understand and agree that these activities. DESCRIPTION specific meaning of each term. For example, if the organization believes the "game" is not a professional, do not use such terms like "game plan", but considering the use of such terms as "Plan Seminar"