Home/ Questions/Q 715091
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-14T05:08:53+00:00

I am working in an environment with a very small team (3 developers only)

  • 0

I am working in an environment with a very small team (3 developers only) and each of us have been assigned a different project, without counting support tasks. I know this is a bad business practice and that we should all work on a single project at a time, and then move on to the next one (Already explained to the management on how much it sucks).

So don’t answer me that we should work all together on one project at a time.
Energizing the work when in a team is mostly pair programming we did that when less project were thrown at us and that was great.

What I would like to know is how you energize your work when working alone on a project.
Do you follow any particular practice?

EDIT

We already do daily stand-up meeting across the whole company, I implemented several “agile” ceremonies while writing my master thesis about Agile software dev practices related to software quality. And that DID improve the overall involvement of the employees.
What I am after is

practices

that anybody could apply, not subjectively questioning the passion of developers.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The situation in our company is similar. We are six developers and work mostly alone on the different projects. To stay at some level of quality and keep some motivation we do:

    • We hold weekly meetings with the developers. Every running project is short summarized in it’s actual state and with the next milestone. Every developer shortly tells what he did last week and will do next week, and talks about problems encountered (some others may have already solved this problem and have advises).
    • Every week on friday one of us does a short talk. Often he introduces in more detail the project he is working on, but we also make talks about interesting technologies, new libraries/languages/tools or try to solve together a bigger problem.
    • We make milestones with releases. Every milestone have to be planned with the tickets included (and which tickets should not be part of this milestone). At the end before the release have to be an approval by another developer to find possible problems before the release.
    • We have continuous-integration with hudson and the continuous-integration-game activated.
    • 0