The value of having jelled teams in the company or working in one is pretty obvious. Such teams are more productive and work more efficiently since they feel comfortable with each other. Can we use some magic trick to create a good team? Not really. For managers it’s usually easier to point out team killing factors rather than give a recipe for a healthy team.
FREE SQL Developer database jobs plugin
Java based IDEs (Integrated Development Environment), like Eclipse, Netbeans or JDeveloper are becoming more and more the main tool ...
A recipe for a perfect team doesn’t exist?
CommentsAre company meetings useless?
Comments
The company life is all about communication be it direct, face-to-face or virtual and remote with colleagues, clients and company partners. Have you ever counted how many meetings you attend in the period of a month or a year? Many people’s work days consist of meetings almost entirely. After all these hours of discussing most of them say “Now I can get back to work and finally focus on my job”.
Do they not treat meetings like part of their work then? What does this sentence imply? Do they indirectly send the message that the time spent in a meeting was simply counter-productive?
Is planning the career path pointless?
Comments
http://www.pongoresume.com
The beginning of a new year is always a great time to start moving your career in a better direction. It’s pretty common that at that time many employees set Workplace and Career New Year’ s Resolutions.
This is also the time for looking back on what you achieved last year, what failures you faced and what lessons you learned. Based on that many of us start planning their career paths all over again.
But can you actually plan it? Does a strict career path limit your perspective? Or maybe it’s just pointless since we are unable to control external factors that affect us?
If there was no law, would everybody be criminals? Creating an agile workflow
Comments
Agile methodology gives an enormous amount of flexibility. This is also a challenge because flexibility and freedom means something slightly different to each team member . The goal is very simple – do the best in the most efficient way. Unfortunately without having a specific agreement on how we follow Agile it will become a mess. Due to that fact, based on SCRUM and Agile approach we have designed our own workflow which is applicable to all our employees and clients. We are alltogether in one workflow which is clear to everyone. At least in theory. To make it real we had to configure our project management environment to allow following the Agile approach. After several improvements we think that we managed to implement a very suitable workflow in managing our daily operations and cooperation with customers in Agile way. Have a look!
Redmine Schedule Plugin a precise tool for resource management
CommentsThe core function of each issue tracking system is to effectively manage tasks in projects. Unfortunately, defining issues in such a system can be a painful process. One task may hinder others making the whole work plan more prone to all kinds of changes. If your team is working on more than one project, a proper tasks assignment without having the overview of all other projects is simply impossible. Due to that fact we have created our own schedule plugin, which is not just another calendar tool. We have combined it with an already existing tickets management system, and added a few improvements to make tasks creation and assignment easier than ever. Check this out!
The 6 main qualities that make a Manager a good one
Comments
Recently, I attended a workshops for Managers. I learned what qualities are required to be a successful manager. Of course, each industry needs its own domain knowledge but on top of this specific knowledge, the qualities that make someone a good manager are more or less similar. What do you think are the most important skills? What does it take to manage people efficiently and effectively and get the best out of them?
Agile development – advantages and disadvantages – Part 2
Comments
http://www.sxc.hu
In my previous post I wrote about the simple situation when incorrect agreements and lack of proper reactions leads to poor results. Clients always want to know two things. When the thing will be done, and how much it will cost. The rest is less important because they want to trust you. At least they should. Trust is very important because it usually makes the client come back with another order later on. In waterfall approach, trust is usually on the same level from the beginning to the end of the project. In Agile development, since you keep in touch with the client, there is a risk that trust will go away much earlier. Why does this happen? Is waterfall approach better?

