2020 Planning

Remote Development has been successfully providing one developer with remote work but on contract while making contact with other capable developers. It is however not yet operating, it is in development as an online project. Our other principal remote developer has written a developer onboarding and sprint management system in Laravel.

What is needed now are clients who buy into the idea and a signed remote development contract: but we have to write the contract, advertise and sell.

To take online remote development to the next level requires three steps are completed:

Preparation for Launch

1a. Client onboarding system updated. (DONE)

1b. Client onboarding tests and any necessary refinement for promoted release.

1c. Marketing user needs survey advertised to capture interest

1c. Create an advertising campaign for Linked-in based on research.

1d. Sign up a prospective client with a planned out project we wish to partner in.

2. Prepare agreements for clients and developers.

2a. Connect a payment system linked to the onboarding software and stripe payments.

2b. Investigate using blockchain style accountability audit trail.

3. Write front end component code for the Developer onboarding, and open the developer portal to sign up available skills and advertise for clients.

Funding may be required to onboard the first project for each team, thereafter it must self-fund. It is the team’s responsibility to own their client and project.

Remote Development is an idea, it is not an organisation. It is run as a project of Software Antelope Ltd (a UK registered company) but agreements for lead developers need to reflect their responsibility so they own their project. It may become an organisation with funding during 2020.

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.

Ideas for development

collectors list

a user-curated list of items with urls that can be scraped for current price

alerts set when prices change

ebay listings created with email confirmation when target prices are attained

users
items
lists
events
messages

a state machine that knows the disposition of each message, event, item cached in shared memory and flushed to disk with delta flags and minimisation

Funding the project

Remote Development is entering a round of funding. Here are some of our ideas and ideals to make this happen.

Purpose

Working in the tech development field and with artists provides a meaningful purpose to application development. There are three sides to this that matter: Technical progress, Artistic meaning, Environmental efficiency. Addressing each of these ideals can make the world a better place for our children to inherit. Progress is an accumulation of value. I aim to create value via technology, via creativity for an environment that improves conditions.

About me

Working in the tech development field and with artists provides a meaningful purpose and powerful combination. I have managed artists, producing events on the world stage, worked with major companies as a highly experienced developer and have tried to make a difference as a writer.

My computer software experience is extensive, yet I insist on keeping up to date with technology. I continue to explore latest full stack delivery methods.

Indiegogo

Application for crowdfunding in progress

Post to Linked In 25 October 2017

RemoteDevelopment.co.uk has launched its first ecommerce site co-production – a project for an artist who makes unique works for children – art4kids.gallery – see https://www.remotedevelopment.co.uk/cms/first-clients/ – implemented in WordPress with Woocommerce/Stripe hosted on an Nginx Cloud server. Just in time for unusual Xmas gift ideas, I was told.

Remote Development is a project I started on a train journey to a client site. The train was delayed. How much is this costing? Years of working in Agile teams and dealing with clients directly as well as contracting via agencies provided the motivation to provide a remote development vehicle. Remote Development is my contracting services delivered directly for clients more efficiently, for less expense. At this stage we are looking for seed clients to grow the business, as we slowly add qualified developers who are able to prove themselves.

Next I am looking for our first Full Stack Remote Development Project Client – if you want a project completed for less with Laravel/VueJS or Angular… remote contracting is proving less expensive than onsite contracting follow the links in the article and send us your enquiry.

===============================
article
===============================

Remote Development is professional contracting services delivered directly for clients more efficiently, for less expense. At this stage, we are looking for seed clients to grow the business, as we slowly add qualified developers who are able to prove themselves. Instead of funding a startup with huge upfront investment to build a huge company, I believe this can grow organically. Instead of creating a software company that owns products, RemoteDevelopment.co.uk can schedule and implement CMS/E-commerce sites swiftly, using an Agile framework, to successfully deliver and host user-created content.

Clients who want to take things further with online applications, or corporate clients who normally hire experienced developers on contract can employ our skills. Onsite contracting is subject to IR35 scrutiny, and in fairness to employees who are committed to a company, there has to be a difference or separation between

There is a natural conflict – clients want to know what a contractor will cost, a contractor asks what the budget is. Negotiation is the path to a compromise. Neither approach necessarily results in the best match of skills to product. The daily rate is simply a cost for time. A budget is an invitation to limit scope.

Agile software development suggests a better way to charge. Development clients can be given a proposal – mapping features against planned sprints. Each sprint is effectively a delivery stage in a continuous integration. Software must work, test-driven development helps! Each sprint can result in an invoice and payment can signal acceptance.

Remote Development is proving less expensive than onsite contracting if you want a web software project (with Laravel/VueJS or Angular) follow the links in the article and send us your enquiry.

====
new version
====

Remote Development is professional contracting services delivered directly for clients more efficiently, for less expense. At this stage, we are looking for seed clients to grow the business, as we slowly add qualified developers who are able to prove themselves. Instead of funding a startup with huge upfront investment to build a huge company, I believe this can grow organically.

Instead of creating a software company that owns products, RemoteDevelopment.co.uk can schedule and implement CMS/E-commerce sites swiftly, using an Agile framework, to successfully deliver and host user-created content. Instead of funding a startup with huge upfront investment to build a huge company, I believe this can grow organically.

Instead of creating a software company that owns products, RemoteDevelopment.co.uk can schedule and implement CMS/E-commerce sites swiftly, using an Agile framework, to successfully deliver and host user-created content.

Clients who want to take things further with online applications, or corporate clients who normally hire experienced developers on contract can employ our skills. Onsite contracting is subject to IR35 scrutiny, and in fairness to employees who are committed to a company, there has to be a difference or separation. Contractors are independent entities who must be prepared to operate independently setup with their own equipment and resources. Remote Development is a natural fit for contractors.

How do we charge for services? Daily rates have to cover costs for on-site work. There is a natural conflict – clients want to know what a contractor will cost, a contractor asks what the budget is. Negotiation is the path to a compromise. Neither approach necessarily results in the best match of skills to product. The daily rate is simply a cost for time. A budget is an invitation to limit scope.

Agile software development suggests a better way to charge. Development clients can be given a proposal – mapping features against planned sprints. Each sprint is effectively a delivery stage in a continuous integration. Software must work, test-driven development certainly helps! Each sprint can result in an invoice. Customers expect delivery of integrated features rather than the time spent on the journey.

Remote Development is proving less expensive than onsite contracting. More can be achieved. It is progress.

=====
final

Remote Development is professional contracting services delivered directly for clients more efficiently, for less expense. At this stage, we are looking for seed clients to grow the business, as we slowly add qualified developers who are able to prove themselves. Instead of funding a startup with huge upfront investment to build a huge company, I believe this can grow organically.

Instead of creating a software company that owns products, we can schedule and implement CMS/E-commerce sites swiftly, using an Agile framework, to successfully deliver and host user-created content. Instead of funding a startup with huge upfront investment to build a huge company, I believe this can grow organically.

Instead of creating a software company that owns products, Remote Development can schedule and implement CMS/E-commerce sites swiftly, using an Agile framework, to successfully deliver and host user-created content.

Clients who want to take things further with online applications, or corporate clients who normally hire experienced developers on contract can employ the skills of seasoned contractors. Onsite contracting is subject to IR35 scrutiny, and in fairness to employees who are committed to a company, there has to be a difference or separation. Contractors are independent entities who must be prepared to operate independently setup with their own corporate entity, equipment, and resources. Remote Development is a natural fit for contractors.

How do we charge for services? Daily rates have to cover costs for on-site work. There is a natural conflict – clients want to know what a contractor will cost, a contractor asks what the budget is. Negotiation is the path to a compromise. Neither approach necessarily results in the best match of skills to product. The daily rate is simply a cost for time. A budget is an invitation to limit scope.

Agile software development suggests a better way to charge. Development clients can be given a proposal – mapping features against planned sprints. Each sprint is effectively a delivery stage in a continuous integration. Software must work, test-driven development certainly helps! Each sprint can result in an invoice. Customers expect delivery of integrated features rather than the time spent on the journey.

Remote Development is proving less expensive than onsite contracting. More can be achieved. It is progress.

For more information see www.RemoteDevelopment.co.uk

Introductory package idea

In a single week “Sprint” we can often train a dedicated client to maintain their own blog with social networking, membership and informational pages.  Our Introductory offer is to use our site configuration skills to provide a framework to work with from Day One.  We include up to 5 day of developer time in the Introductory offer.  This 5 days may be taken over a period of 3 months or 6 months.  The website may be visible the whole time (we advise this), or it can be kept private (sometimes a good idea for two weeks at the start or for a release event).

For the Introductory duration you continue to have daily support contact without any fuss to build new website capabilities, provide configurations, apply your design and colour plans, adjust any of the above.

We work with Clients who want to know how to achieve good site content that is both relevant to their own customers.  You can also use this time to provide online ecommerce purchase pages and totally secure isolated payment systems.  We can install your software and configure it and teach you to use it online in a support session.  If we need to send you a screen shot or a link we can.  We are (for the foreseeable future), human.

We realise this may take you month, but 15 minutes a day support may keep you making better content.  You do the posting, writing, uploading.  We help you organise and maintain it.

 

 

Intro to the intro site

The Introductory site deal is for those who want to build a website that they can update themselves with as much work as can be achieved to implement the site design in a One Week Sprint.  That is Six Days of whatever effort you want to put in to learn how to use your new website and CMS.  Providing you interact with us on Slack this is what we achieve for the average user:

  1. complete WordPress installation with 100% support for one week followed by Casual support for the rest of one year.
  2. A potentially intense one-week online development interaction to shape your new site exactly how you want to see it.  You can schedule the days but depending upon availability, this may run for 5 contiguous days or, for example, two days, followed by a week’s gap, followed by 3 days in a row.  You may have to book the days you want on a first come-first served basis.
  3. After five days of development we spend one day tidying up code, documentating, and sprint planning the next stage of your overall plan.  We then propose the sprint plan as a development project which is already hosted.  If the new Client wants to add more features to their CMS they can,  if they want to integrate a Development Project then Development Hosting is required.  This may involve moving the CMS site to a Cloud host which is a part of the delivery unless a separate Development Hosting is purchased.  The only thing that is “paid up” in a Intro site is the intro site itself which is generally hosted on cloudhosting.co.uk which is the Answerable DNS for all assets including cloud hosted subdomains.
  4. We are unlike others: we create a service delivery and ensure that you can use it on whatever hosting you need.  If your service delivery needs more than one host, we simply add the name and sprint plan with you any work to create a new function.  We charge extra for bandwidth when you get very successful, we charge for each domain name, but you only pay for hosting once per annum.  Your overall hosting strategy may mean that basic hosting is no longer suitable for you, but will probably suffice while we configure for your expansion.  Expansions to hosting need not be extravagant but bandwidth costs must always be covered. You may however need both CMS and Cloud hosting accounts to support a Development Project with staging and a CMS which is never staged.
  5. as well as subdomains, we can use meaningful domain name suffixes to point at related sites.  Additional domains can be added for the cost of renewing them, we do not charge for the number of domains but it may use up more of the development time you have to make a structure any more complex than it absolutely has to.  It is usually best to have ONE domain name.
  6. It is vital to get used to creating content.  Write. Publish.  Revise. Rewrite.  Republish.  Start again.  Be fluid about content.  Link all your posts to social media so people can link to them and publish articles that people will read under menu listed categories that your audience need.  You can make it members only (they have to join/subscribe to see it) or public.
  7. The important thing is to write like a river – you are guiding a “user journey” – basically you want them to do one thing – the next thing they need to do – offer too many or a not compelling choice and that is the attention span filter at work.
  8. Every page is best done with an image, a story start point (the image) and end point (link to the shop page or a forum, for example).
  9. When a new content creator is to be added to the site, they are going to have to create content as Contributors until they get the idea and then Authors until they really get it.
  10. Editor status granted to one user at a time.  They take responsibility for all content.
  11. A user who wants Admin rights basically takes over the reigns completely and only seeks support from RD.  Out of scope of the Intro package.
  12. Intro package could have add-on services like Remote Backup that may be chargeable, as they can be done by the Admin using Export.
  13. Supported Admin for small sites can be included, but once we start adding a structure of users, they are not small sites.  So we need a break point of where intro sites have one Editor user needing to be upgraded to CMS sites to establish the Admin Role, perhaps.
  14. The Admin sets the roles for all other users.