Conversation
First draft - WIP Ref: #114
Clarify labels and team member permissions, per #114 (comment)
| @@ -0,0 +1,34 @@ | |||
| # New client setup | |||
|
|
|||
| So you've won some work from a new client - good for you! | |||
There was a problem hiding this comment.
I would add a little 🎉 at the end of this sentence for both visual interest, dwylifying the readme and because otherwise we risk it coming across as a bit sarcastic 😆
| * 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 |
There was a problem hiding this comment.
at once = 5 days before the first sprint begins
| * 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 |
There was a problem hiding this comment.
Shouldn't this come before the contract so that it can be saved immediately and other materials (proposals, budgets, etc) can also be saved there
| * Proposal | ||
| * Contract | ||
| * Budget planner | ||
| * [ ] Set up github |
There was a problem hiding this comment.
I read this as Create a github and was like... huh? 😆
| * Contract | ||
| * Budget planner | ||
| * [ ] Set up github | ||
| * Create a client organisation |
There was a problem hiding this comment.
*Ensure the client creates an organisation on github and either also creates the project repository or provides a member of the dwyl team with enough permissions to create a project repo (provide them with a reference to https://github.com/dwyl/github-reference ?)
| * [ ] Set up github | ||
| * Create a client organisation | ||
| * Create project repo | ||
| * Initialise with `readme` |
There was a problem hiding this comment.
Could we simply reference this checklist here rather than duplicating? https://github.com/dwyl/contributing#minimum-requirements-for-a-new-repository
|
|
||
| * [ ] 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 |
There was a problem hiding this comment.
I should add something in here about the aims of the initial workshop too... 😬
|
|
||
| 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. |
There was a problem hiding this comment.
Something about the wording here makes the hairs on my arms stand on end - we spend so much time minimising the number of systems we use, could we simply say something like 'This is a checklist of what we aim to have completed before we start working with any new client:' or something to make it seem less "spread out"? 😛
| * 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 |
There was a problem hiding this comment.
Add:
- Determine key success metrics for project with client
- Ensure your client is aware of what user stories and acceptance criteria are and how to use Github to create them - if not, provide them with a training call/meeting
Answered all points raised in PR review, except for the part about the kickoff workshop - on which I'll have to defer to @iteles
2 participants
First draft - WIPRef: #114