From b377070b1fd51147a9ae447e72584d1b4965cbba Mon Sep 17 00:00:00 2001 From: Alex Rubner Date: Wed, 31 Oct 2018 18:04:43 +0000 Subject: [PATCH 1/3] create new clients process First draft - WIP Ref: https://github.com/dwyl/process-handbook/issues/114 --- new-clients.md | 33 +++++++++++++++++++++++++++++++++ 1 file changed, 33 insertions(+) create mode 100644 new-clients.md diff --git a/new-clients.md b/new-clients.md new file mode 100644 index 0000000..088628b --- /dev/null +++ b/new-clients.md @@ -0,0 +1,33 @@ +# New client setup + +So you've won some work from a new client - good for you! + +This is how we set new clients up on all of our various systems. + +* [ ] Create and sign contracts + * Template contract is saved in the `Clients` folder. Unless there are non-standard terms, only pages 1, 9, and 10 should change +* [ ] Book initial workshop + * This will be the responsibility of the client contact + * Bear in mind that our standard terms are for the first invoice to be paid at once, so that can be raised and sent out immediately +* [ ] Set client details up on Xero for invoicing + * `Xero > Contacts > Customers > Add customer` + * You'll need their accounts contact email address at least + * Other contacts can be copied in or not as they prefer + * (You should also ask what information they need for their system, if they haven't already requested it.) +* [ ] Set up Google Drive + * (This is still a WIP as it's not currently possible to duplicate entire folders on Drive) + * Set up a folder to match the `.template` structure (hopefully we'll find a way to just dupe it) + * Be careful to keep the `permissions` the same + * Save all documents with financial/sensitive information in the `.private` folder + * Proposal + * Contract + * Budget planner +* [ ] Set up github + * Create a client organisation + * Create project repo + * Initialise with `readme` + * Call it something _sensible_ + * Copy across our labels + * Give permission to all team members who'll be working on the project +* [ ] Set up gitter + * Decide whether this will be a `dwyl` channel or coming from the client repo From 22d053b686af90479b407f4ef38d6888788eb5b8 Mon Sep 17 00:00:00 2001 From: Alex Rubner Date: Wed, 13 Mar 2019 14:56:26 +0000 Subject: [PATCH 2/3] Clarify labels and team member permissions Clarify labels and team member permissions, per https://github.com/dwyl/process-handbook/issues/114#issuecomment-439016016 --- new-clients.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/new-clients.md b/new-clients.md index 088628b..eb540bb 100644 --- a/new-clients.md +++ b/new-clients.md @@ -27,7 +27,8 @@ This is how we set new clients up on all of our various systems. * Create project repo * Initialise with `readme` * Call it something _sensible_ - * Copy across our labels + * Copy across our labels using [labelsync](https://label-sync.herokuapp.com/) as per https://github.com/dwyl/labels * Give permission to all team members who'll be working on the project + * Either at the `org` level, if we have access to that, or at the repo level if that's all we have access to * [ ] Set up gitter * Decide whether this will be a `dwyl` channel or coming from the client repo From b1354d59e4a8532aaac7edfd69007b0cd328942f Mon Sep 17 00:00:00 2001 From: Alex Rubner Date: Wed, 27 Mar 2019 17:14:55 +0000 Subject: [PATCH 3/3] Responses to review Answered all points raised in PR review, except for the part about the kickoff workshop - on which I'll have to defer to @iteles --- new-clients.md | 36 +++++++++++++++++------------------- 1 file changed, 17 insertions(+), 19 deletions(-) diff --git a/new-clients.md b/new-clients.md index eb540bb..1045bd5 100644 --- a/new-clients.md +++ b/new-clients.md @@ -1,34 +1,32 @@ # New client setup -So you've won some work from a new client - good for you! +So you've won some work from a new client - good for you! :tada: But the work has only just begun (literally), my friend. -This is how we set new clients up on all of our various systems. +This is a checklist of what we aim to have completed before we start working with any new client: +* [ ] Set up Google Drive folders + * (This is still a WIP as it's not currently possible to duplicate entire folders on Drive) + * Set up a folder to match the `.template` structure (hopefully we'll find a way to just dupe it) + * Be careful to keep the `permissions` the same + * Save all documents with financial/sensitive information in the `.private` folder + * Proposal + * Contract + * Budget planner * [ ] Create and sign contracts * Template contract is saved in the `Clients` folder. Unless there are non-standard terms, only pages 1, 9, and 10 should change * [ ] Book initial workshop * This will be the responsibility of the client contact - * Bear in mind that our standard terms are for the first invoice to be paid at once, so that can be raised and sent out immediately + * Bear in mind that our standard terms are for the first invoice to be paid five days before the start of the sprint, so that can be raised and sent out immediately * [ ] Set client details up on Xero for invoicing * `Xero > Contacts > Customers > Add customer` * You'll need their accounts contact email address at least * Other contacts can be copied in or not as they prefer * (You should also ask what information they need for their system, if they haven't already requested it.) -* [ ] Set up Google Drive - * (This is still a WIP as it's not currently possible to duplicate entire folders on Drive) - * Set up a folder to match the `.template` structure (hopefully we'll find a way to just dupe it) - * Be careful to keep the `permissions` the same - * Save all documents with financial/sensitive information in the `.private` folder - * Proposal - * Contract - * Budget planner -* [ ] Set up github - * Create a client organisation - * Create project repo - * Initialise with `readme` - * Call it something _sensible_ - * Copy across our labels using [labelsync](https://label-sync.herokuapp.com/) as per https://github.com/dwyl/labels - * Give permission to all team members who'll be working on the project - * Either at the `org` level, if we have access to that, or at the repo level if that's all we have access to +* [ ] Set up github (organisation, repo, permissions etc.) + * First ensure the client creates an organisation on github, then either... + * ... creates the project repository + * ... provides a member of the dwyl team with enough permissions to create a project repo + * For reference, you can send the client [this](https://github.com/dwyl/github-reference) for reference + * And a dwyler should also ensure they've been through the checklist [here](https://github.com/dwyl/contributing#minimum-requirements-for-a-new-repository) * [ ] Set up gitter * Decide whether this will be a `dwyl` channel or coming from the client repo