Wednesday, 20 March 2019

sharm kar

अब बड़े मजे का टाइम है ! अगर ये जॉब आया.. शायद आया. क्युकी दिमाग का को ये लोग सुबह उठते ही ऐसा घटिया हाल कर देते हैं की लगता है की माँ भी ऐसी होती होगी किसी की जो ये बच्चे ऐसे स्कूल जाते हैं खैर ठीक है, क्या पता बच्चे ऐसे भी जीते थे , मगर... अब अभी से आगे सुनियेगा .. ब्लॉग का डेट बदल नहीं सकता ... मगर बाकी तो .. पता नहीं कौन सा क़ानून नहीं है जो इनको सजा नहीं दे सकता !!\

Monday, 28 January 2019

Agile-Team-Challenges

Agile way of delivering business solutions has revolutionized the concept of project management. Gone are the days of waterfall, where interdependent multiple stages of project development kept stakeholders on tenterhooks before release phase. Sponsors having invested in product had to kept waiting for final product for a long periods with two worries constantly hounding them, whether product would meet expectations and whether market expectations  change since initiation ? Agile came as a rescue for all, both sponsors and stakeholders. While stakeholders are able to see product taking shape and they are able to fit in changing market needs, the delivery teams focus is more on developing business features rather than working through mines of documentations. No more burning mid night oils at push of project managers because scope of project has changed and deadlines have arrived. Agile gives solutions for real-life challenges during product life cycle.

While Agile brought more value to all involved parties, its principles are something which sound too-perfect theoretically however too difficult to put in practice. In this article, I would try to focus on one such pillar of agile, that is "SELF ORGANIZED TEAMS".

The most critical component (well, I would stick my neck out and say "the most" ) is self-organized agile development teams. "Self-Organized" is a classical term to define a team which could manage themselves, does pro-actively assess the requirements, is able to wear multiple hats and is able to help each other without prompting. The ultimate load balancer, the ultimate self transformer team can be called "self-organized".

The "self-organized" term could be a fancy term used to boast about a mediocre team as well. Not mediocre as in technical skills always but in terms of team-work, pro-activeness, honesty etc. This may look too critical but there are scenarios where so-called "Wonderful self-organized-team" was seen getting teared in pieces when situations went beyond normal. I am putting some points which may help getting the idea clearly:

1. A sprint required a developer (great JAVA developer) to do some testing. The developer rejected it saying "I was not born to do testing, I am a proud coder". Doing RCA of the situation, it became clear that the developer had experience in waterfall model through out before this project, though he attended some agile sessions, still maintained the earlier principles. (these principals are imbibed since college education times where sharper students go for development career, not-so-sharper ones go for testing career).

2. A team member is struggling to finish story points due to initial impediments and his sickness for couple of days. Another team member has work going smooth, a little ahead on curve and is expected to go smoother as task doesn't have any dependencies. Its apparent that  first member can get some help in completing his story points from the second one, but second one is planning to have some recess time to mingle with old colleagues as he is ahead of curve. Scrum master notices the gap and drop hints for second member to help the first one (remember scrum master is a slave manager here, who can advise but is not suppose to direct), but the second member ignores the hint and sprint goes for a loss of velocity.

3. A senior developer doesn't speak about this new language / tool required to finish tasks in current sprint. The developer is 10+ years of experience, delivered many projects in same company and is considered 1000 pound Tech-gorilla in the team. He is the guru, he can not be seen as not in control any point of time. Sprint starts, goes well for some time and then starts lagging because the language / tool became difficult to maintain pace for the developer. If this knowledge gap was known up front, some training sessions may have helped the situation but the 1000 pound tech gorilla inability to speak honestly about gaps killed the show.

4. Two members of a team do not like each other much. Actually, their relations are beyond repair and these folks are too diplomatic  / senior to speak freely about it. Scrum master gets some hints of this problem, engages with both but hears that things are alright. Sprint starts and falls flat on face, when root cause analysis is done, its evident that there were many fires burning but these two experienced folks chose not to talk about it at all. Things kept moving with fires in belly and ultimately burnt the sprint goal.


There could be many such scenario where sprint goal are compromised due to issues in the team. As a scrum master, its vital to sense the issues lying beneath thin layer of diplomacy and try to address it as soon as possible. Below are some pointers I would suggest from my experiences which could help in finding issues as finding issues is first step towards solving these:

1. Its important to understand that issues can not be found in one day or solved. Give time to yourself and team, of course not forever but sufficient time.

2. Keep eyes on body language too apart from words and actions. An estimate give with legs shaking  is a forced estimate.

3. Develop a taste for coffee if not already :) . Coffee conversations give more clues than any other form of meetups.

4. You can not fix everything. Some things may be beyond repair, be brave to replace in those situations.

5. It may be intimidating to challenge 1000 pound gorilla in room, keep it diplomatic but do not miss to challenge them. Challenging them earns a lot of respect from rest of team, brings confidence in them.



Feel free to add points from your experience. We all would get benefited from different point of views.