Se afișează postările cu eticheta application. Afișați toate postările
Se afișează postările cu eticheta application. Afișați toate postările

duminică, 29 ianuarie 2012

Team velocity

1 comment
`First time I heard about team velocity has been when I read some things on Agile development. There are various descriptions of the team velocity in Agile and I invite you to read this one.
I said this is a great descriptor of the team performance and I should introduce it as objective reference for comparison with the other teams. Thinking back, I realized that it is not easy to implement this due to the way estimations are made and planning is implemented. Therefore, I put this on the shelf, for more reflection...
But, I came to the idea that there is another velocity of the team. I wrote some weeks ago about the team seen as road. If you are the vehicle, and the speed of this vehicle is the speed of your personal development, we come to the idea that the team velocity is actually the average development speed of the team members plus the development of the team itself (different than of the individuals).

According to physics, the speed is the ration between the distance and time. Of course, we will make, for this concept, a similar ratio between the personal development achieved and the time elapsed. When your are thinking
It's excellent for any human being to progress. The trick that manager has to master is the direction of development. How this direction is in the interest of the team, respectively of the company. It's the post-capitalism era we face now. Talents are important, this are the competitive advantage. Money are a fantasy.

Let's continue with some more considerations about team velocity, how can it be ensured and what are the consequences of it.

The first idea you could put in practice is the set of trainings for a certain role. This is obvious and there are not so many things to say on it. I would add that each training shall be discussed by the manager with the team member to underline the objectives for the team and to reflect on the objectives for self development.
This is putting me to a next suggestion: consciously or not, each individual is developing from point A to point B. Having identified the two points A and B, the manager can use specifically the trainings and other development measures to facilitate this journey. Enrolling the individual in irrelevant trainings for his journey makes the journey longer and decreases the team velocity.
Trainings are not enough. Everyone needs practice. With the destination point in mind, with the next role in mind, the manager can facilitate learning experiences within controlled environment. For instance, there is the need that John becomes a very efficient software release engineer (you, that guy that prepares the releases and makes sure that the others gets what they have been promised). So, John can prepare some internal releases, can do some less important projects where he can practice his knowledge and imagine own working style.
Of course, development is harder as one advance in seniority. Things become fuzzy and manager should add his visionary talent to identify possibles steps ahead. There is always the need of transformation. A team does not remain the same, in roles, activities and responsibilities.Team velocity cannot be measured objectively in all aspects, but there is one obvious output: the thrive of team members.
I've read recently a post on HBR.org on Creating Sustainable Performance. One of the main ideas has been that people thrive within an environment that supports learning and based on their inborn skills. You can read full article, I noted down two things I could do in my team to ensure a great team velocity.
Delegate decisions.
This comes with a bunch of benefits (see the theory of distributed computing power) and with certain drawbacks in dealing with mistakes. For me, looking for the rootcause, fixing it and not dealing with guiltiness and guilty people fixed most of the things. People love to decide and to participate to decisions, but they are afraid of mistakes. Having this fixed, manager can embrace a participative leadership style that prevents him on being part of every decision and leaves some time to think forward.
Constantly offer feedback
Based on my personal leadership style, I tried to improve the way I collect and give feedback. I've started with giving feedback only during evaluations, but I am trying (keep trying...) to offer positive and constructive feedback through out the year and make the evaluations only a sum of previous discussions. Additionally, I am looking constantly to facilitate the expression of feedback between team members. I think is not yet where it should be. Keep trying...

One thing it sure helps in team velocity is to explain and discuss. The journey should be a team journey. The development of one team member should be in the direction of the team development and should not do any harm to others. Constant discussions about the team's roadmap increase the awareness and facilitate contribution. Also, one can identify other potential leaders during these discussions, gather useful insights and include common vision of the future.

This is not all about velocity. Next weeks we will speak about:
- adjustment of velocity for each team member
- expectations for senior team members
- how to retain the know-how and release the humans
- how to make the development speed uniform and avoid internal turmoils

Read more on the same subject:
Team velocity [1] -the mission of the team slightly influence the velocity

Team velocity [3] - the entry points
Read More...

vineri, 2 decembrie 2011

despre programatori

1 comment





De la http://www.facebook.com/pages/I-am-ProgrammerI-have-no-life/241806149201604
Read More...

luni, 31 octombrie 2011

Application development vs Kernels and drivers development

Leave a Comment


When speaking about how to develop software, one is usually making the difference between drivers, OS and rest of the application software.
It is always about different strategy in developing the software. The lower software layer have to be generic, scalable and easy to use, if possible. The developer is applying some paradigm, even defined by the OS itself and has to optimize the usage of the hardware. The primary customer of his application is the colleague next to him who will develop further the application


The application has slightly different constraints. It has to meet the expectations of the customer, as well as to implement non-functional requirements. Now, the customer is identified and the generic cases are not in the focus. One can argue that re-use of software is a trend now. A trend yes, but a primary focus very seldom.

Then, it is the pressure of delivery date. The generic development has some buffers in the timescale. The application has to meet the delivery date to customer. This is not easy to negotiate and it is part of the product to be delivered. The generic software is part of a strategy. We start early, it is nothing yet defined and there is no recipe how to do it.

This fight with uncertainty combined with the scarcity of information in what regards the new technology is giving the developers of basic software this aura of pioneers or medieval knights who are pushing the limits. The others, as harsh it might seem, are actually the bourgeois who are the core of society and they are keeping where there are the existing limits.
Read More...

marți, 27 septembrie 2011

Interviewing software developers

Leave a Comment
A summary translation of two older posts about interviews.

I had tens of interviews with young software developers. The market in my town is quite hard and I had to imagine which types of candidates I could have.
Some of the candidates have a genuine interest in money, others in having a great career, but there is a significant number of people who are interested in "software engineering". They are not coders (see rent-a-coder), they are looking to implement something that is really working.
Some of them start with embedded in second or third year,  crafting a small PCB, they stay nearby a passionate professor. They continue with participation to various contests, sometime they are hired even before graduation, still keeping the crafting passion.

In a few years, you find them in the core team of the project. They are quite happy as they know what they like and, due to nice advance in career, a little bit more relaxed related to their future.
My humble opinion is that they enjoy what they like and don't have to go home to practice their hobby. They come with most innovative ideas, they are change agents in their organization. No wonder about that. I have quite a lot colleagues like this and it's always a pleasure to work in such a team.

Nevertheless, there is a significant number of people, have a great potential, but lacking the perspective about their life. They start great, seems to break records and suddenly they are stucked. They start to doubt about the organization they are part in, but never come with concrete alternative. They are not at all attached emotionally by the team, more likely driven by a rough idea. It's very surprising to see them collecting a row of failures, like you would look to a BMW M5 which cannot overcome a Dacia Logan on the highway. On top, the BMW is pumping out smoke like an old train.

  • There is no recipe to identify the people born talents which will die as a big hope. But, I always look to this criteria when deciding about a candidate. It is same important as what he knows.

This is one criteria. Others would be
  • Gifted engineers do make the difference in projects.
  • You cannot make a team out to "out-of-ordinary" guys. It is a tautology. Still, it is not evident for everyone.
  • It is hard to wait for "perfect fit". Still, the compromises you have to make need to be acceptable for long run of the team.
  • Consider, if possible, the next 2-3 moves of the person. Imagine the person in the next job, either as expert or managerial. After all, a manager should be an acceptable chess player.
  • Look for recommendation. If you know people that could give you hints, you gain two things. First, you know better the candidate. Then, when recommendation come from team members, you make them responsible and they will work for the integration of the new comer.
  • Don't look for the best candidate from know-how point of view. The best employee is the one who is integrated first and can offer great results on short and medium time-frame.
  • If you value the Pygmalion effect, it really works.
  • For a great candidate, don't give up after the first No. Always consider the second.
Hopefully, this post is not too intricate. Please give feedback if you have used the idea.
Read More...