In a software technology startup team, there is a colleague who is perceived to resist this desired workflow:
- Use self-hosted GitHub:
- Open issues
- Regularly comment/update on in-progress issues
- Specially when stuck in a problem
- Submit pull requests
- Provide requested APIs for developed packages
- Follow test-driven development i.e. TDD
- Be active in sprint talks
- Provide agenda and talk in detail about work in-progress
- Document your efforts
- Seek help by sharing the progress
- Let everybody know what you're up to
For some reason, the colleague resists the above workflow. Trying to push the colleague has a negative effect, due to self-reported motivation loss.
By resist, I mean, he:
- Doesn't use the workflow
- Doesn't test
- Doesn't provide requested API
- Doesn't communicate regularly with the workflow tools
The colleague is a knowledgeable one. But our guess is that he focuses too much on distracting details. For example, he starts using a tool, right after he studies its whole specification. But he doesn't need to get to know every detail.
The colleague is a student in graduate school and is very involved in academic studies.
I wonder what might be a fine method to approach him regarding our workflow?