7 Good Habits Your Development Team Should Haveby QArea Team on April 1, 2014
Every IT company exercises its own management techniques which employees can be satisfied or not quite satisfied with. Here we present some thoughts our team members say work for both developers and development team management.
- Make each standup focus on a single project.
Daily standup calls and meetings with every person of the department or team in a SCRUM company do not always work as expected. When one person is presenting their update at such a meeting, half of the rest participants are not likely to be on this project, which means they are just wasting time there. If you team has several projects, it’s more recommended to hold a standup meeting in each team in order to keep their focus.
- Dwell on the updates, filter out questions or discussion.
Standup conversations waste time even more. During a standup, let everyone give their update – what they have done, what they are going to do, what obstacles they are facing – and should any part need discussion, address it again when everybody has finished their reports and you still have some time for discussion. Nobody wants to wait while two people are disputing over some feature’s implementation plan that nobody else will touch.
- Take a lunch break.
Try not to have lunch at your desk – better go away from computer for dinner time. It’s quite standard for IT companies that employees just grab some quick lunch and continue working while eating. But this makes the feel exhausted by the working day as they haven’t actually taken a break at the office.
- Spend money on the tools your team needs.
It’s useful for your team to have an account on Github with many private repositories available. Subscribe to some time-tracking service and when you find that you are reaching the limits, get the more expensive account. Remember that labor is your real cost, so it’s no use saving money by manual process as it may make cause just the opposite effect.
- Maintain weekly team assignments.
It’s essential that a developer knows how to distribute his time among the projects for every given week. Having a weekly project assignments plan and knowing the number of hours you are to devote to each assignment let you know where you working focus should be and allow some time for those last-minute problems which might completely scrap your longer-term plans.
- Get an IRC channel.
IRC is free with many free apps to try. Setup such channel for your company to give people a handy way to ask business questions or just chit-chat. This should be done both at the company level and for each project. As with the first tip, all chatter on a particular project should be confined to the team members involved in it. You may just as well invite the client there to facilitate questions and answers on the project.
- Avoid working on Saturdays.
While much work is commonly considered better than insufficient work, but having to do work on weekends regularly means that the planning process has drawbacks. This is the evidence that you’ve taken on too much work on yourself and are doing something wrong. Because the facts are adding extra man-hours to the project won’t get it finished quicker if the staff is too tired for this.
Has your dedicated development team got any good habits yet? Try adding some of the above!
Check out our related articles: