5 tricks to know before you outsource your drupal project
0 likes769 views
Take time to thoroughly document project requirements to avoid misunderstandings. Encourage offshore developers to ask questions to gain a clear understanding of the project. Define communication methods and frequency, such as weekly calls, to ensure the project stays on track. Conduct regular reviews of deliverables and provide feedback to minimize mistakes. Require daily status reports from developers on tasks completed, time spent, and any clarifications needed to maintain transparency.
![Tip 5: Task Status
You must have clear transparency of what your team is doing and where they are heading up.
Ask your Developer to provide you daily status in following format:-
This email will be submitted daily in morning and evening:
Subject- Today's Goal - Date
If I could do only 3 tasks, what would they be?
1. Task 1 - [Expected Hours - 2 hours] [Actual hours - ]
2. Task 2 - [Expected Hours - 2 hours] [Actual hours - ]
3. Task 3 - [Expected Hours - 2 hours] [Actual hours - ]
Keep the tasks action oriented and short.
Additional Tasks underwent-
1. Task 1 - [Expected Hours - 2 hours] [Actual hours - ]
2. Task 2 - [Expected Hours - 2 hours] [Actual hours - ]
Is there anything you need from your Lead today or tomorrow?
1. I need clarification on _____. XX mins meeting today would be great.
2. I need clarification on _____. XX mins meeting tomorrow would be great.
This email format has proven to be very beneficial in maximizing resource management. It also ensures that your
project is constantly accelerating!](https://image.slidesharecdn.com/5trickstoknowbeforeyououtsourceyourdrupalproject-130528011659-phpapp01/85/5-tricks-to-know-before-you-outsource-your-drupal-project-4-320.jpg)
5 tricks to know before you outsource your drupal project
- 1. 5 Tricks to know before you outsource your Drupal Project
- 2. Tip1: Take time to Document Your Project When dealing with an off-shore team, a poorly documented project or no documentation directly hampers the efficiency of the team. Consider this example: You: Hey, I need an orange ball Developer: Ok Don’t be furious if your developer ends up giving an orange football instead of an orange ball. This happens often when all requirements are exchanged over email/call. Now, how it would be if you had documented your requirement. I need an orange ball which should have following characteristics: Round Orange Hollow Radius – 5cm Now, you’ll always get a perfect orange ball as you have required. So take time to document your requirement. It’s worth the effort!
- 3. Tip2: Encourage your offshore team to raise doubts Never lose patience or feel irritated when your developer asks too many questions. Instead encourage them to raise doubts because that ends up giving a better insight of the project to your developer. Always remember that – you understand your project well because you have it in your mind but to your developer it is just the set of instructions or requirement that you provide. So you must gain the fluidity to pour in the project from your mind into your developers. With each answer to their question you are achieving this. Tip 3: Define Communication Frequency and Medium With an offshore team you cannot enjoy the freedom of shadowing them anytime. So, it is really important that you decide how frequently you want to meet – of course on a call. Decide a time that suits both of you considering the time-zone difference. Generally meeting your off-shore team once/twice in a week is enough to ensure that your project is on time. Set the time and day and make sure that your off-shore team and you adhere to it. If required bring them on call more often, but make sure that to understand where your team is leading. Tip 4: Review – Feedback – Review Set up frequent deliverables and review the development so far; even if it is a rough prototype. Give your feedback and then review again that your feedback so far has been incorporated. This ensures maximum efficiency by your time thus, minimizing scope of mistakes.
- 4. Tip 5: Task Status You must have clear transparency of what your team is doing and where they are heading up. Ask your Developer to provide you daily status in following format:- This email will be submitted daily in morning and evening: Subject- Today's Goal - Date If I could do only 3 tasks, what would they be? 1. Task 1 - [Expected Hours - 2 hours] [Actual hours - ] 2. Task 2 - [Expected Hours - 2 hours] [Actual hours - ] 3. Task 3 - [Expected Hours - 2 hours] [Actual hours - ] Keep the tasks action oriented and short. Additional Tasks underwent- 1. Task 1 - [Expected Hours - 2 hours] [Actual hours - ] 2. Task 2 - [Expected Hours - 2 hours] [Actual hours - ] Is there anything you need from your Lead today or tomorrow? 1. I need clarification on _____. XX mins meeting today would be great. 2. I need clarification on _____. XX mins meeting tomorrow would be great. This email format has proven to be very beneficial in maximizing resource management. It also ensures that your project is constantly accelerating!