Developers

we = remotedevelopment team, you=a developer

Onboarding

Initial contact from linked in, link to our website, email or other sources.

You get to the website and fill in a form

  • Personal details (name, age, nationality, company/sole trader)
  • Payment details (paypal, stripe, bank account number)
  • Skills and experience matrix
  • CV upload (PDF for direct presentation)
  • Rate expectations (low/high) for a Sprint (2 week delivery period)

We look at the form and ascertain it is not spam, and setup skype interviews with viable prospective developers.

We need to know if you are capable of remote work, your skills set: what your expectations are

Availability calendar

Organisation

We are looking to build small teams with excellent skills in 

  1. Laravel/VueJS full stack
  2. Later: GOlang, Dart, MEAN stack?
  3. Design and Graphic preparation
  4. Front end (Vanilla JS, VueJS, Less, CSS)
  5. Social Networking, CMS sites, Adwords and Analytics

Our infrastructure

  • Linux cloud servers
    • Web server (assets, code)
    • Repository
    • Database server
  • git
  • Jenkins
  • Travis CI

We use an external service for email and document sharing (Gmail, Google Drive)

We use cms.remotedevelopment.co.uk to publish documents

Communication is via Slack, supported by email

Our infrastructure is

  1. Linux Cloud server
  2. NGINX
  3. git
  4. mysql
  5. Jenkins
  6. Travis CI
  7. Grunt/Gult/Mix build tools
  8. Linting tools

Client infrastructure uses our infrastructure but we may move them onto:

  1. AWS 
  2. Postgres/MongoDB, other databases 

We are transparent with clients: they can use us or they can “move on” (meaning their security info is given to them, we do not own their data, we build and access their infrastructure)

Teams are from 1 to 6 developers (Lead, Backenders, Frontenders, Designer) but most projects will have 1 or 2 developers

Contracts

Remotedevelopment signs a contract with a client to deliver a project. The client is not given a quote or a specification, but goals are established and broken down into deliverables using Trello.

Let’s say it is a dashboard with lots of components requiring a infrastructure and sign in from users. We can put this together using Laravel in a few hours, and then keep extending it using migrations. We estimate this to be a project for 2 developers and 1 designer (for the first stage). We map it to 10 sprints, 2 of which involves the designer and one developer, 8 of which involves 2 developers.

Sprint 1 and 2 Lead + Design

Sprint 2 – 10 Lead + Developer

Lead Developer is a full stack developer, and the other developer usually would be Frontend or Full Stack. Due to the use of migrations in Laravel, this is quite feasible.

The client understands, due to the Agile process, that they can change or adapt ideas according to market research or priorities and that at the end of each Sprint there is normally a Deliverable which is invoiced.

To start, a client makes a downpayment for one sprint (2 developers) – each developer has declared their rate and the Team Leader can ask for developers to join the project. The developer is contracted for a number of Sprints.

The Contract describes a project with an end goal, but at the end of a Sprint the work is presented on a Staging server for the client to review. The Client has either started an account (monthly payments) in which case the next sprint can be started, or the client is on a cash basis, in which case the next sprint is started when the client has paid for the completed sprint. This is a basic mechanism, it is also possible to vary it but the basic unit is always a Sprint.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.