Two Way Expectations When Working with Developers
In my consultancy, I’ve worked with close to 25 freelance devs. It’s a weird culture bring people on who are very temporary. Even still, I’ve found that setting a culture of clear, up front expectations makes for a far better experience for everyone! No surprises. Here is what I have sent to the new developers I have worked with in the past couple of years. Feel free to use any of it that is helpful:
Expectations for Jevin’s developers
I love working with smart, fast, friendly people who can get things done. If there is one thing I’ve learning in working with people is that clear expectations can really help keep a relationship running smoothly. As such here are the expectations you can expect of me and what I expect from those whom I work with.
What you can expect from me:
- I will give you clear designs and user stories that are not ambiguous on the task to do.
- I will give you feedback on our relationship and the quality of your work on a regular basis.
- I will respond to emails within 24 hours unless otherwise noted.
- I pay you in a fair timeframe as per our initial agreement.
What I expect from you:
- When you provide an expected delivery time for a task, you will work on and deliver the task by that time. This can be in the form of user story estimates and velocity in Pivotal Tracker if you so choose.
- I expect to receive updates on the progress on tasks at a minimum every second day.
- You will complete work without me having to ask you to complete it.
- If you cannot make the deadlines, you will proactively reach out to me as soon as you know you won’t be able to.
- Stories will have a associated unit tests and acceptance tests. You may use discretion about how far to take this.
Let me know if these are okay with you. If it seems after we start working together than these expectations are not working out on either side, we will have to part ways.
All good things,