This has to be one of the lightest posts on our blog so far! but the banner Nauman has created for a Drupal developers campaign we recently launched is simply too awesome (in my opinion) not to make it to the blog and be immortalized in the blogosphere!
there is a PHP developers campaign banner too (below) but my current flavor is definitely the Drupal developers banner up top! Awesome work Nomi. And yes I have shrunk the PHP banner so it does not distract from the awesomeness of the Drupal developers banner… yes I am Drupal biased! only a tiny bit.
more of the usual business like posts to follow… soonish.
Every team has its own preference of tools and the key is the ability of the in-sourced talent to be able to hit the ground running with the tools already in use for anything else will cause unnecessary disruption that negate the benefits of in-sourcing and embedding for a capacity boost. The cavalry should arrive and join the melee in true cavalry style!
Our engagement methodology is in that spirit, though we have our own tool kit that includes Redmine, Basecamp, Harvest, GIT, SVN, JIRA, Skype, G+ Hangouts, NetBeans and Visual Studio… but we also ensure our Drupal developers are familiar with and comfortable in the use of popular tools like Huddle, SharePoint, BugZilla, Mercurial and Eclipse.
And yes there will always be instances where the tools in use are unfamiliar to our teams, in which case our learning curve will pleasantly surprise you.
This ensures that our Drupal and Php developers can join and embed in your team from the get go, minimizing the on-boarding time significantly.
A Drupal capacity Boost: the approach
Back in the summer of 2011 a London based digital agency short on internal Drupal capacity and tired of the promises of recruitment agents approached us to explore how our on-demand Drupal capacity burst would work for them… with plenty of reservations of course.
We started off by taking their resource requirements and presented a number of our resource profiles to them from our Drupal developer resource pool and presented the process and cloud based tools we used by the teams to interact. The very next day their technical director conducted a number of interviews of our selected staff over Skype and was taken aback by the depth of their knowledge of Drupal and their communication skills.
The tipping point was when we demonstrated how using cloud based tools the Drupal developers would be managed entirely by the agency’s own project manager and would work with their existing team. And how simple it was to do so using tools like Basecamp, Jira, Git, Redmine etc. and communication over Skype and Google+ hangouts took care of the distance barrier. The agency was already using Git, Basecamp and Skype whilst working with contractors and members of the Drupal community… it was a no brainer.
Two members of our staff were selected to start the following week for a 1 month trial period. Our in-sourced Drupal developers hit the ground running and within the first week were put on time critical tasks, the following week the agency requested that three more Drupal developers be added to the mix and the agency has held on to the five for almost a year now. Our use of Google+ Hangouts has been an awesome hit!
Ok… you’re thinking that’s a nice story but where’s the meat!…. remember the editors orders! Short posts… so you’ll have to wait.. and the details will follow.
How is in-sourcing different from Outsourcing… and better?
Any credible outsourcing partner would tell you that a clear technical project specification is the groundwork of any successful outsourcing project.
However, if like the rest of us you live in the real world you already know customer stories are rarely static, end user needs and expectations are constantly evolving and adaptation is key to survival as is agility to success. In the traditional outsourcing world, this real world behavior can and does derail projects.
In-sourcing talent does away with the ‘box’ that outsourcing stuffs every project in.
You bring in our skilled resources into your team that you and your project managers/developers manage directly. You define and control the specifications to be as rigid or as fluid as your customer wants. You can make U-turns, change requirements on the fly, dictate the sprint duration and develop throwaway prototypes just as you do in the real world without paying the penalty of having to pay more to build applications that reflect the real world… a changing one.
In-sourcing is the evolution of outsourcing!