In part 1, Mike talks about how he got into remote work, SCRUM iterations versus Kanban, why it’s important to assume nothing when communicating with remote coworkers – and much, much more.
Podcast: Play in new window | Download
Show Notes:
01:00 – Mike Zazaian introduction, history & background
[unordered_list style=”bullet”]
- Remote worker for 4 years
- PHP work, project management in L.A., C-Sharp, Java, .NET
[/unordered_list]
02:02 – Key to remote work
[unordered_list style=”bullet”]
- Rigorous communication and organization
- Better to be sure than miss something
- Structuring thoughtful emails
- State of the project emails
- Interpersonal communication
- Teamwide communication
[/unordered_list]
05:30 – Importance of daily state of the project emails
[unordered_list style=”bullet”]
- Look at every day as nobody knows anything
- Item by item completion
- Flexible milestones
- Doesn’t assume arbitrary temporal segments of work to be done
- What is today, may not be the same tomorrow
[/unordered_list]
08:20 – Mike and remote work
[unordered_list style=”bullet”]
- Values freedom
- Background in English and Film Studies
- Rails as an art form
- Environments are crucial
- Everybody has business value
- Perceptible value of happiness
[/unordered_list]
14:40 – Making remote work successful
[unordered_list style=”bullet”]
-
Convey the quality of work as a developer
-
Convey business value
-
Sell the client on yourself
-
Make the client at ease via communication
-
Developer and project manager communication
[/unordered_list]