tags:

views:

523

answers:

5

If you were the head of your current company/IT department, what would you change?
Would you:

  • introduce SCRUM to all teams or stop using it?
  • hire more software testers?
  • change the policy on IT related courses?
  • change the bonus system?
  • ...?

Please mention the reason(s) behind the non-trivial changes you'd make. All ideas for improvement are welcome.

+3  A: 

Just one area, but... ... I think motivation is a big key if you want to score big. You want to have motivated workers that always strive to be up to date on knowledge all by themselves. Workers that love to go to their job. If you don't, it's easy that your organization will have a rather low roof of knowledge. To get a feel for what motivates your employees I'd take them out, one by one and ask them what their ideal working environment would be and what they would want to change to the current one. Ask them to loose the boundaries on that question to get really open answers.

miccet
What will you suggest if you find that many people come to work to just exchange their man-hours for money?
sharptooth
I know this is not really realistic, but in my ideal company you don't have that kind of workers for the above mention reason that these people will not evolve in the same way as motivated people do.
miccet
+4  A: 

Optimize meetings. They are often conducted in such a way they become a waste of time and a killer of productivity - many people get together and sit for two hours discussing things which only some of them have heard about and can affect.

In most cases it's much better to plan several smaller meetings.

sharptooth
+2  A: 
  1. Organise enough number of meeting. As of now there lot of unwanted meetings.
  2. Avoid personal meetings and introduce call conf
  3. Introduce IM . My current company does not have one :(
  4. Give developers more freedom to use their own ideas (My current company's development standards are formed by some architects who have no clue about the current developments in s/w development)
  5. Reduce the number of documents and increase time in innovative ideas.
  6. More peer reviews than the testing by testers.
Shoban
A: 
  • Introduce design and code reviews. They have a higher ROCE than hiring more testers.
  • Can all regular meetings, they're a crutch for inadequate managers. All meetings should be ad-hoc.
  • Introduce a rule that states all documents written prior to coding are for discussion purposes only, i.e. paper is considered ephemeral.
  • Remove all bonus systems. Bonuses require metrics to be objective, and metrics are counter-productive because they encourage gaming.
  • Introduce a rule that states any methodolgy consultant entering the building will be shot on sight. These people can destroy your company.
Bob Moore
Are you actually saying specs are for discussion only?
tehvan
Seriously ? Specs are so fluid they couldn't be for anything else. Most customers don't even know what they DON'T want until they see it. Nor do they have even the weakest grasp of what is actually possible.
Bob Moore
A: 

I would:

  • increase communication between the different departments (it's an IT company, so the competence is spread out)
  • have an architect join the salesmen to restrain them from making too big promises
  • arrange for some regular tech-talk courses, where employees can learn about new technologies and deepen their knowledge by asking questions and going over things in group.
  • have code reviews a requirement in stead of an exception
tehvan