“What happen when we move in a new situation” or for the sake of simplicity of understanding let’s say what you feel when you join a new team. You as an “individual” bring in your learning, your individuality to the whole team. You get acquainted with the processes prevailing in the team. Some of these processes you would have experienced before, some you would have never heard of. Things which are new are tough to digest and practice. We react to it: we start questioning, we feel little uncomfortable towards the new things. We start influencing the process by “trying to modify” the existing process. That is the “individuality” you bring on to the team, which should be highly respected. Some of these processes are good, efficient, valuable etc. Some has room for modification, replacement. During the initial phase of settling down we feel strongly about these processes. Given a chance we would want to change it or replace it. This feeling of bringing change lasts from starting few da…
Showing posts from March, 2011
- Other Apps
Individuals with their own individuality, style and uniqueness forms a Team. A Team is defined not by the uniqueness of the individual but by the coherent vision and capability they share. It’s a group of focussed people who lead to the success of any project rather than a bunch of highly talented individuals who just wants to get driven by themselves. Team is very similar to a chariot shown below. If all the four horses starts to run in their own direction then the person riding this horse will never reach his/her destination. The goal of a team should be to achieve higher level of cohesion, trust among peers and increased focus on delivery. It should be performance oriented. The biggest advantage of team is learning from peers. One should be open to learn. I may be good at certain thing but there is always a room for improvement in each of us. Also it’s the onus on each one of us to shape the behaviour of team. There are people who make you feel positive and spread positives vibes …
- Other Apps
In my previous post “Bridging the gap-the ‘Analyst’ way” I have briefly discussed the role of Business Analyst. One important role in addition to that is “testing” the system frequently. I strongly believe that BA should test the system frequently. They should verify the acceptance criteria of the story and augment the QA testing. This is especially important when we have more than one BA on the team. One should continuously be in touch of the system by testing it. Also this will inculcate the feature ownership, which sometimes get lost in day to day rush.