Trying to check if the API's of various tools really work...my good pass time in the evenings...
Wednesday, 1 April 2009
Tuesday, 13 January 2009
I am sleeping!!!
Posted by Sameer Shaikh
Yes. I am sleeping completely or am a lousy shack now... Its been ages and ages I am keeping myself busy with work without happening to type in the URL www.blogger.com. Wanna know more of what the pity is? I have got my twitter, facebook , google and linked in connected with a few plugins that will help me post through my daily editors and MS outlook (which is like running 24/7 on my muster) I am JUST too LAZY to blog....
Now with my GTD increasing I am trying to find reasons on not to blog... how funny ;) Anyways here is what I got to do...
1. Blog review 2008
2. Template change
3. Pay justice to blogging over www.miniclip.com
Pray to get my brains back on track....
Now with my GTD increasing I am trying to find reasons on not to blog... how funny ;) Anyways here is what I got to do...
1. Blog review 2008
2. Template change
3. Pay justice to blogging over www.miniclip.com
Pray to get my brains back on track....
Tuesday, 30 December 2008
Things that I learnt in 2008
Posted by Sameer Shaikh
I thought I would mention a few of the most important things that I learnt. I learnt from work , life , people, Team , Organisations and of course from Internet:
1. Perception doesnt stay long
2. Unrealistic promises hurts lives of everyone
3. Spend only when it is necessary
4. If you dont care about communication, no one cares about you
5. De-personalize the problems
6. Credibility comes with trust and trust comes with time
7. Commitment is the first step in building success
8. Success and Failures area result of Team work
9. Plans are necessary but they need commitment, support and passion to make it success
10. Dont make your Team burn oil when not needed
11. Your words act as the face of your Team, be careful with the impressions
Wait for other items to come in....
1. Perception doesnt stay long
2. Unrealistic promises hurts lives of everyone
3. Spend only when it is necessary
4. If you dont care about communication, no one cares about you
5. De-personalize the problems
6. Credibility comes with trust and trust comes with time
7. Commitment is the first step in building success
8. Success and Failures area result of Team work
9. Plans are necessary but they need commitment, support and passion to make it success
10. Dont make your Team burn oil when not needed
11. Your words act as the face of your Team, be careful with the impressions
Wait for other items to come in....
Friday, 24 October 2008
A Vital skill - Negotiations
Posted by Sameer Shaikh
All night yesterday I watched the first season of Desperate Housewives and all through the series there was one character that was consistently hitting my mind ... "Mr Soliace" husband of the latina and the Mergers and Acquisation expert. While I went through all of this I realised that for your success at any level you need to have the best negotiation skills.
I took this question forward: what does the skill demand?
1. Perception making
2. Strong confidence
3. A vision to failure
4. No knowledge in detail
5. An Eye on phsycology of others
6. A breath on anger and temperament
7. A not so pleasing personality
8. An attitude to care a shit about
9. Knowledge to know how much you can make for yourself if not for others
10. Last but not the least the power to convince GOD
I wish to write more on this after my this weeks experience, negotiation is a hard core skill and I realise I have a bit of it. The remaining half glass is going to be filled sooner or later.
I took this question forward: what does the skill demand?
1. Perception making
2. Strong confidence
3. A vision to failure
4. No knowledge in detail
5. An Eye on phsycology of others
6. A breath on anger and temperament
7. A not so pleasing personality
8. An attitude to care a shit about
9. Knowledge to know how much you can make for yourself if not for others
10. Last but not the least the power to convince GOD
I wish to write more on this after my this weeks experience, negotiation is a hard core skill and I realise I have a bit of it. The remaining half glass is going to be filled sooner or later.
Tuesday, 17 June 2008
Middle Management blocks Blogs, Wikis and such tools... How true
Posted by Sameer Shaikh
I came across this blog recently and found the statement "Middle Management block the use of blogs, wikis, syndications..." The first statement that read my mind was HOW TRUE.. and why not, I have seen it until very recent.
We recently in our project teams wanted to drive a revolution of using:
1. Wiki for Project documentation
2. XPlanner for Project Management
3. JIRA for Bug Tracking and time scehduling
Eventually not many understand and want to promote the usage of it... why?
1. They are not comfortable with the tools.
2. They are not sure how the tools fit into the process.
3. They are not really thinking on how a tool can make it work for them.
I see some more of the issues....
1. They are not ready to accept the tools that can accelerate Team collaborations.
2. They are not sure on how they can use the Tool.
3. They feel that the tool is a burden if they have to work with it every day.
4. They dont get what is called as readymade data to present to the Management (Heard of a word called Metrics?)
5. They are not sure what team collaboration means.
6. They understand the tool and its usage WRONG.
7. They think that there is a lot of investment in making this tool work for the Team.
A few of the common excuses we get from the Middle Management in implemnting such tools are:
1. It doesnt provide me the metrics.
2. Think we need to evaluate another better tool, can someone take up the investigation on this please?
3. It is a over load of tasks for the Team.
4. We dont have time to train the Team (Remember my earlier post on Highest priority?)
5. We have some other tool coming up and that can do better than this.
6. It will take long before we can roll this out.
7. No one uses it.
8. No one has time to use it.
9. They dont like the way it is now, we need to evolve.
10. There is no easy way to access this information....
Now can you find a way for these lousy bums and can somebody explain them that it will work only if they wish to make it work?
We recently in our project teams wanted to drive a revolution of using:
1. Wiki for Project documentation
2. XPlanner for Project Management
3. JIRA for Bug Tracking and time scehduling
Eventually not many understand and want to promote the usage of it... why?
1. They are not comfortable with the tools.
2. They are not sure how the tools fit into the process.
3. They are not really thinking on how a tool can make it work for them.
I see some more of the issues....
1. They are not ready to accept the tools that can accelerate Team collaborations.
2. They are not sure on how they can use the Tool.
3. They feel that the tool is a burden if they have to work with it every day.
4. They dont get what is called as readymade data to present to the Management (Heard of a word called Metrics?)
5. They are not sure what team collaboration means.
6. They understand the tool and its usage WRONG.
7. They think that there is a lot of investment in making this tool work for the Team.
A few of the common excuses we get from the Middle Management in implemnting such tools are:
1. It doesnt provide me the metrics.
2. Think we need to evaluate another better tool, can someone take up the investigation on this please?
3. It is a over load of tasks for the Team.
4. We dont have time to train the Team (Remember my earlier post on Highest priority?)
5. We have some other tool coming up and that can do better than this.
6. It will take long before we can roll this out.
7. No one uses it.
8. No one has time to use it.
9. They dont like the way it is now, we need to evolve.
10. There is no easy way to access this information....
Now can you find a way for these lousy bums and can somebody explain them that it will work only if they wish to make it work?
Monday, 16 June 2008
A Bad Presentation
Posted by Sameer Shaikh
Yesterday I was supposed to take up the Agile workshop for the part of the team that is really been damaged due to NO process and Process myths in the organisation. The "supposed to" was really for the last 7 months when each time I had to request for this and all I got is an answer saying "At the moment we dont really have time for this", eventually I was lucky enough this time to get through the Team and at least be prepared on some items on what and how I wanted to do things for this Agile workshop to make it more effective and more better. To my own surprise I relied on Powerpoint and really prepared something that I always hated.
But they say you need to have it your day and your way to make it work... eventually the fever, headache and fallout of some ideas and team members in contributing to the workshop lead this to be the BORING ever presentation I have been a part of... remember I have attended some corporate trainings on finance and technologies which were really boring and I claim this one from mine to be worst than any of them. The Idea of running the workshop was bright, though I was not able to successfully convert it to a involved workshop.
I retrospected what went wrong and here are the items I found:
1. Involve the crowd
Seems like I missed it for 2 reasons, I did not analyse the crowd before really kicking it off. The Idea I had was to involve a few guys bring them mid store and ask them some survey questions to bring out the Myers-Brigg indicator model out and also make them aware of how important Team plays in the Agile model.
Second I was not able to create some real time humour out of Agile and waterfall models... things that rushed my mind during my presentations were eventually to heavy than I thought they could be.
2. Never depend too much on PPT
I wanted to start with NO presentations... use the board and the Team speeches to make it more effective, however change of plans last minute made me think that its better to go the PPT way and try to address issues and tips and concerns while I talk... this was a bad plan honestly.
3. Unresponsive crowd is the truth
Its not that I have always seen very energetic crowd in the presentations... half the time I have presented to people who dont even know if they should keep their eyes open in the sessions or not. Anyways today i realised that Teams can really be unresponsive if they dont know why are doing what. Ideally I saw only 5 people involved in the entire presentation:
1. Vinaya the girl who was sitting right in front.
2. Shailesh : Who was trying to understand and respond in a way that would be pleasing to a presenter
3. Bhargavi : Who kind of knew the objective and was curious to know whats next
4. Eric : The guy in the bottom most corner who understands Agile and wants to enhance his knowledge
5. Arjun who wants to know more about it.
Rest I saw were either there by force or for a sake. Eventually some of them may be involved but I did not find it out for some reason.
4. Missing exercises
25 minutes of the kickoff I understood that its getting boring and I need to change something, eventually when I changed to bring in some questions and role playing I found that the Team lacked feel of energy and enthusiasm. It would have been good to have some exercises to make it work better.
5. Wheres the Red Bull
The energizer was missing. These are the things I wanted to do:
1. Ask Deepesh , Yogesh and Nikhita to talk about the developer advantages they feel from the Agile we follow
2. Ask Sidd , Saket to make it work effectively and explain the QA and the Release processes.
3. Have the funfilled Crack my code exercise to get the developers write some code on the fly while others extract the mistakes.
4. Have the QA write flow cases for the developer code.
5. Have the Project Manager plan the 30 mins code and qa exercise
6. Have the architect review
7. Have the Stakeholders explain the requirements and do a official kickoff.
All of this was role playing eventually I dropped this after 25 minutes of session just to make sure that it doesnt go wrong way due to the sleepy crowd.
Anyways as a corrective measure I am going to continue the training and appoint some agile coaches to make this work effectively for the Team. Eventually looking at the team formation I think it will be at least a 6 month task to make this team understand agile and start implementing it to some extent.
Whoa .. Task is ahead......
But they say you need to have it your day and your way to make it work... eventually the fever, headache and fallout of some ideas and team members in contributing to the workshop lead this to be the BORING ever presentation I have been a part of... remember I have attended some corporate trainings on finance and technologies which were really boring and I claim this one from mine to be worst than any of them. The Idea of running the workshop was bright, though I was not able to successfully convert it to a involved workshop.
I retrospected what went wrong and here are the items I found:
1. Involve the crowd
Seems like I missed it for 2 reasons, I did not analyse the crowd before really kicking it off. The Idea I had was to involve a few guys bring them mid store and ask them some survey questions to bring out the Myers-Brigg indicator model out and also make them aware of how important Team plays in the Agile model.
Second I was not able to create some real time humour out of Agile and waterfall models... things that rushed my mind during my presentations were eventually to heavy than I thought they could be.
2. Never depend too much on PPT
I wanted to start with NO presentations... use the board and the Team speeches to make it more effective, however change of plans last minute made me think that its better to go the PPT way and try to address issues and tips and concerns while I talk... this was a bad plan honestly.
3. Unresponsive crowd is the truth
Its not that I have always seen very energetic crowd in the presentations... half the time I have presented to people who dont even know if they should keep their eyes open in the sessions or not. Anyways today i realised that Teams can really be unresponsive if they dont know why are doing what. Ideally I saw only 5 people involved in the entire presentation:
1. Vinaya the girl who was sitting right in front.
2. Shailesh : Who was trying to understand and respond in a way that would be pleasing to a presenter
3. Bhargavi : Who kind of knew the objective and was curious to know whats next
4. Eric : The guy in the bottom most corner who understands Agile and wants to enhance his knowledge
5. Arjun who wants to know more about it.
Rest I saw were either there by force or for a sake. Eventually some of them may be involved but I did not find it out for some reason.
4. Missing exercises
25 minutes of the kickoff I understood that its getting boring and I need to change something, eventually when I changed to bring in some questions and role playing I found that the Team lacked feel of energy and enthusiasm. It would have been good to have some exercises to make it work better.
5. Wheres the Red Bull
The energizer was missing. These are the things I wanted to do:
1. Ask Deepesh , Yogesh and Nikhita to talk about the developer advantages they feel from the Agile we follow
2. Ask Sidd , Saket to make it work effectively and explain the QA and the Release processes.
3. Have the funfilled Crack my code exercise to get the developers write some code on the fly while others extract the mistakes.
4. Have the QA write flow cases for the developer code.
5. Have the Project Manager plan the 30 mins code and qa exercise
6. Have the architect review
7. Have the Stakeholders explain the requirements and do a official kickoff.
All of this was role playing eventually I dropped this after 25 minutes of session just to make sure that it doesnt go wrong way due to the sleepy crowd.
Anyways as a corrective measure I am going to continue the training and appoint some agile coaches to make this work effectively for the Team. Eventually looking at the team formation I think it will be at least a 6 month task to make this team understand agile and start implementing it to some extent.
Whoa .. Task is ahead......
