3 ms·

Thank you for reply. I think it also depends a lot on the individual. You need more motivation to invest some thoughts instead of just getting it over with.

tonyarkles 8y ago
Is this front-end guy an employee? Or a contractor? That changes things a little bit, but I think things below still apply. > You need more motivation to invest some thoughts instead of just getting it over with. That's where your team's standards help, especially if you get them set up early. If, at the point this employee was hired, it was standard to (per the article's example) spend 40% of the task time up front thinking about the problem and writing it out, then the motivation is simple: If I don't do it this way, then I won't fit in with the team that I joined and I'll probably get fired. Onto the situation you're in right now, where this person has been on your team for a while and not doing this... Do the other teammates do this? Is there code review? Do they flag the fact that this person is implementing features sloppily and push back on that at review time?
- anotheryou 8y ago
  I joined the team half year ago and since then we started code review (but quite technical, so sloppy UX won't be caught here), I write actual concepts (instead of just 1/2 page of a rough draft before implementation starts), we discuss and adjust the concepts together and there is a roadmap (not super agile, but suits what we currently do best). So there is little culture to build upon, but we take steps in the right direction (though time pressure from upper management makes progress plateau a bit here). About the (sole) front-end guy: he's an employee and a little less independent than the others. Thank you for the encouraging me to develop the culture a further. Currently I try to get the devs to write propper tickets themselves at least (in a way that lets QA do their job afterwards).
  - tonyarkles 8y ago
    > I write actual concepts (instead of just 1/2 page of a rough draft before implementation starts), we discuss and adjust the concepts together and there is a roadmap (not super agile, but suits what we currently do best) Keep doing what you're doing! That's awesome!

tonyarkles 8y ago

Is this front-end guy an employee? Or a contractor? That changes things a little bit, but I think things below still apply. > You need more motivation to invest some thoughts instead of just getting it over with. That's where your team's standards help, especially if you get them set up early. If, at the point this employee was hired, it was standard to (per the article's example) spend 40% of the task time up front thinking about the problem and writing it out, then the motivation is simple: If I don't do it this way, then I won't fit in with the team that I joined and I'll probably get fired. Onto the situation you're in right now, where this person has been on your team for a while and not doing this... Do the other teammates do this? Is there code review? Do they flag the fact that this person is implementing features sloppily and push back on that at review time?

anotheryou 8y ago
I joined the team half year ago and since then we started code review (but quite technical, so sloppy UX won't be caught here), I write actual concepts (instead of just 1/2 page of a rough draft before implementation starts), we discuss and adjust the concepts together and there is a roadmap (not super agile, but suits what we currently do best). So there is little culture to build upon, but we take steps in the right direction (though time pressure from upper management makes progress plateau a bit here). About the (sole) front-end guy: he's an employee and a little less independent than the others. Thank you for the encouraging me to develop the culture a further. Currently I try to get the devs to write propper tickets themselves at least (in a way that lets QA do their job afterwards).
- tonyarkles 8y ago
  > I write actual concepts (instead of just 1/2 page of a rough draft before implementation starts), we discuss and adjust the concepts together and there is a roadmap (not super agile, but suits what we currently do best) Keep doing what you're doing! That's awesome!