Getting on board

Getting started

The first step is to register and then you can access our services immediately.

Once registered as a client you see this screen:

Here is an illustrative example of our user-friendly introduction form so we know the name of your business and whatever you want to tell us about your objectives:

Some clients have to get a website before they want development services, and we can get you setup usually rapidly.  We then provide support services to help make you independently able to extend your business, your art, your creativity on the web medium more easily.  And then leave you to it.  Yes, we can extend support services but each has a term and a desired set of goals.

Corporate Clients often will have a requirement that is more detailed and which is evolving as each Department may have an input.  They may have approached the market and found they either had to build and staff up a team, budgeting up to five or six figures to resource a project. There are usually holes, contractors may simply not be available. Or it is just too great a risk to contemplate starting, yet.

Our services are used by IT departments, Agencies, and IT Managers to keep a project on target.  You want good developers: some of the hard-working skilled contractors who can win in the tough London market now live remotely.  We offer a structure for subcontracting to add effective workers to existing projects as well as assemble teams for whole projects.  You want people who understand what you need and are good at delivering and understanding client requirements.

Developers

We offer a structure for developers to join who are skilled in delivering software modules to contribute to a sprint and to win a “fair share” of the fee.  Most of our developers are full-stack so they can claim 100% but some may wish to invite other developers to join in.

We only accept payment claims that meet the high level of performance we expect from developers.  We do not employ developers, they may wish to contribute to a project to develop a relationship with a client. We provide an infrastructure to the client and manage projects.

A combination of old-school fundamentals and state of the art frameworks and online service integration means that Developers can leverage our infrastructure to manage remote work for clients more easily.

Client Homepage

Our client home page provides a quick method to understand services and to send your enquiry. For example, you may initially ask us to build a new website so you can blog about the project. Or you may have a defined project you wish to talk about.

We then respond with a proposal by email. This is not a quote but an estimate of how many 2-week sprint iterations are possibly required to get your project working.   New projects can take the MVP approach – what is the core purpose of your project, and develop that, and extend it with other services, or applications.  That way your existing services continue to work without interruption.

New projects can take the MVP approach – what is the core purpose of your project, and develop that, and extend it with other services, or applications.  That way your existing services continue to work without interruption.

We have looked at your requirement and estimate about how long that may take, and how many developers we need to achieve the results we are proposing.

We send the Client a proposal with two links, one is to place an order on account, and the other is to take advantage of a prepayment discount for the first Sprint and/or a down-payment for new clients.

The Client can now order or inquire about additional projects, collecting estimates to on-ramp projects easily.

When an order is placed, the work is scheduled and one of our team of developers will be in touch to commence the first Sprint. In two weeks, results are published on our Staging Server, ready for Client acceptance.

Agile

Agile Software Development was developed by some of the best minds in our industry. Years ago. Since 1998 it has become the way to do things.

Short Iterations
We use 10 day sprints (over two weeks). During each Sprint, we follow a sprint plan. We need two basic sprint plans for the initial sprint for a CMS site or a Development project. These can be patterns, something like:

CMS

  • collect design components from the client using survey page*
  • Create WordPress Instance, connect to domain and email addresses
  • Using a base template* and the core set of plugins* create pages and menus for the Core Items*
  • Liaise with client to collect core information for Contact us and About us page

Development Project

  • Get basic info from the Client
  • Instantiate base site on Cloud
  • Implement User Registration and Auth
  • Client specific steps…

These are not complete! Discussion with the client over Slack is required for 2 – 4 days to flesh out the project.

*there are common elements we can write to make our lives far easier and expand on what we can implement during the first sprint. Each item we develop, we share across the network so that we have constantly rising standards of delivery for that all important first sprint.

TDD (Test Driven Development) – Laravel has an excellent TDD method. Development Projects benefit in quality and speed by using TDD. 100% test coverage is the goal with TDD. It is best practice. If you develop without TDD, then you will spend more time debugging when adding a new feature later.

Sprints – Each ticket on Trello is in a subject column. Each ticket has a label which has a status. These are

Research
Concepts
In DESIGN
ACTIVE
DONE
BUG

When a ticket is done, it stays around until the end of the sprint, and then it is Archived. We do not resurrect a ticket, we create a BUG ticket if the problem arises in a new Sprint or reset the DONE flag if it is not really complete.

Tickets
Each ticket you pick up at the Scrum meeting – you complete that day. Each ticket is given another tag during Sprint Planning which is simply a projection of how many hours the ticket can be done in. This is a planning expectation and helps us organise work. Each ticket is completed with QUALITY first, meaning the deadline is not as important than it is completed professionally and forever. Each Developer has a Label which is used to assign the task.

Example

Scrum
Every day at a strictly appointed time, the team review the Trello board over a Google Hangout. Get your coffee before the meeting, and anyone who does not join the meeting on time will get assigned work. Anyone at the meeting assigns their own work. If work is not completed from the previous Scrum, then it is continued and NO NEW TICKET can be assigned. If it is near the end of the Sprint, other developers may collaborate but most tickets are the singular responsibility of the assigned developer. If you want to claim a share of the reward, then you have to do the work!