ثلاثة أفكار أن يعتبر عندما يطبّق رشيقة مع يوزّع تطوير أفرقة
أعدت الهيكل ال [سفتور نجنيرينغ] يتلقّى يكون بإدخال رشيقة برمجيّة تطوير مفاهيم. قد حضّ رشيقة تحسين عظيمة في ال [ليف-سكل] من برمجيّة مشروع. عندما يطبّق رشيقة مع بعيد عن الشّاطئ أو يوزّع تطوير فريق, هناك فرصة أن يخاطب ثلاثة مظاهر من المشروع. نحن سنغطّي هذا ثلاثة مواد [أس ولّ س] يزوّد بعض خلفيّة على رشيقة.
هناك عدّة تطوير تكتيكات يقدّم برشيقة. ركّز على كثير تكتيكات محاولة أن يقلّل [أند/ور] عرضت خطر في يطوّر برمجيّة في مبلغة قصيرة وقت. تكرار التطوير البرمجيّة في واحدة [أونيت وف تيم], وهذا يمكن دمت [فروم] واحدة [تو] أربعة أسابيع. هو يتضمّن تخطيط, [رقويرمنت نلسس], تصميم, [كدينغ], ويختبر. يحتاج برمجيّة يطوّر أثناء تكرار لا يكون وظيفيّة بكفاية أن يكون أطلقت كمنتوج في السوق, غير أنّ الهدف أن يتلقّى يعمل برمجيّة, دون بقة, في النهاية من كلّ تكرار. [ر-فلوتس] الفريق المشروع أولويات في النهاية من كلّ تكرار.
تقليديّة [أوتسورس] ضخخت تحديات وتحديات جديدة خلقت عندما برمجيّة تطوير أخذت بعيدا عن الشّاطئ. هذا تحديات جديدة في الدّرجة الأولى في فروق ثقافيّة, يضمّ مع الاتّصال صعوبة واجبة إلى الفرق في وقت و [لنغج كمبرهنسون]. Most importantly, the biggest challenges remain in communicating, transfer of business logic understanding, demand in co-operation in poorly defined projects, unknown and imprecise requirements and lack of customer involvement, differences between customer and vendor, geographical distance, and many more. To be successful with offshore software development, these hurdles need to be overcome by both the onshore and offshore teams.
In plan-driven and Agile as well, face to face communication is stressed to improve communication and understanding of the project. This type of face to face time takes place during each iteration, where plan-driven project is concerned and this took place essentially at the beginning of the project. When face to face time is not possible with the offshore provider, it is beneficial to have each developer answer 3 daily questions: what you did yesterday? what you plan to do today? describe any roadblocks or obstacles in completing the iteration stories? Each developer should answer these question and not simply the offshore project manager. Perhaps the offshore project manager can help in translating the answers to these questions.
In case of Agile, face to face meetings are held at all time, usually in the form of daily Scrums, pair programming, iteration retrospectives and iteration planning. In distributed development teams, many times the onshore managers travel offshore to hold meetings with the offshore team, or in other circumstances, managers from offshore travel onshore for meetings. One important influence depends on the offshore person visiting the onshore team to absorb the project details and develop/foster relationships. He should take this know-how from the onsite team in a way that he is knowledgeable enough to answer many questions raised by his offshore team. In addition, he should be also capable of relating to his team members about the decisions that were taken in his meetings with the onsite team. Depending upon the complexity of the project, a member of the onsite team, with good knowledge in business logic is often sent to work offshore.
In implementing Agile projects, a series of processes are utilized. The development process is not just a single approach. In implementing software offshore development, there are some principles that are followed, which have been termed as Agile Manifesto. These are as follows -
➢ Customer satisfaction is achieved by rapid and continuous delivery of useful software.
➢ Quick delivery of working software within weeks rather than months.
➢ The principle measure of development progress is derived from the working software.
➢ Any changes in the software may be incorporated later.
➢ Necessity in having face to face communication for better understanding.
➢ Maintain close relationships between the business people and the developers.
➢ Motivation and trust on the individuals make the project implementation successful.
➢ Apply continuous attention to the project design, and try to attain technical excellence.
➢ Adapt fast to changing circumstances.
It was found that the iterative framework brought benefits to Agile software development vendors. By this approach, the customers could make payments after each iteration. By paying this way, the customer does not lose or be in a risk to pay the for the whole lot after the completion of the project. This brought in commitment from the customer to provide the vendor with better business and motivates the vendor to consider each iteration important. The method of continuous feedback and communication helps in the offshore development process, but the approach of short iterations has proved to be especially successful.
Another aspect of Agile development is the importance of testing in each iteration. Each iteration should produce automated tests that can be used during each iteration and future iterations as well. The benefits of automated testing is better covered in different articles. However, in the context of this article, it is important for your offshore vendors to deliver automated tests with each iteration. When considering new vendors, ask about their testing strategies. It is better to go with a vendor who believes in automated testing, rather than trying to convince a vendor the benefits of automated testing.
So, in sum, when implementing Agile in distributed development teams, there are opportunities to address three aspects of the project: communication, payment/deliverables and automated testing.
[أوتسورس] برمجيّة
![[أوتسورس] برمجيّة](/images/tallglobe.gif)










