<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:blogger='http://schemas.google.com/blogger/2008' xmlns:georss='http://www.georss.org/georss' xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-8171940499402566116</id><updated>2024-03-07T22:14:41.846-08:00</updated><title type='text'>My Opinion</title><subtitle type='html'>A casual blog</subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://ineni.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8171940499402566116/posts/default?redirect=false'/><link rel='alternate' type='text/html' href='http://ineni.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><author><name>Sumanth</name><uri>http://www.blogger.com/profile/12832477486389303210</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>10</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-8171940499402566116.post-8699837913987060249</id><published>2016-05-29T04:35:00.001-07:00</published><updated>2016-05-29T04:36:59.473-07:00</updated><title type='text'>Value of Time vs Money</title><content type='html'>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;
I have a special person in my life and she has been my inspiration and guidance since my birth.&lt;br /&gt;
In our recent conversation she mentioned about the true value of time and how people waste it by giving more importance to money.&lt;br /&gt;
Following is the excerpt from that conversation:&lt;br /&gt;
&lt;br /&gt;
We keep hearing people speak about the value of time but its unbelievable that most of us don&#39;t realise it, never take it seriously and very rarely get it into our head&lt;br /&gt;
Let me say this to you again - Time is the most important thing in life. No matter what you do lost time won&#39;t come back. On the other hand money gone can be earned back.&lt;br /&gt;
Every second is valuable and not worth wasting. If most of us think back and look through out lives we will realise that we did nothing great.&lt;br /&gt;
Some don&#39;t excel in their career, don&#39;t excel in their earnings, kill off all the hobbies and never show interest in anything.&lt;br /&gt;
People even don&#39;t enjoy their lives. And when they think deep why they lost time doing nothing they like, they will realise that its because they give undue importance to money.&lt;br /&gt;
They don&#39;t want to let go of money and they end up giving up something more precious.&lt;br /&gt;
Whenever I speak to my friends or colleague they express great ideas they have but never took the step to implement them and when you ask why, more often than not they say &#39;it costs money&#39;.&lt;br /&gt;
It is true that everything costs money and one should earn enough before thinking of spending that money. But it doesn&#39;t mean to stop living your life to save for the future. One should find the balance.&lt;br /&gt;
Being so money minded people forget to live their life. They end up dumb, good for nothing person. All because they valued money over time. If they value time, they will start to live life, with that comes happiness and money automatically follows.&lt;br /&gt;
Once we realise this we feel like we solved a complex puzzle of our lives.&lt;br /&gt;
Money is needed. We should save for future but not at the cost of basic happiness in life. And we simply waste time, just because we never valued time. Once we realise time is so important and 100s of 1000s of times worth more than money then even sleeping feels like wasting time.&lt;br /&gt;
Once we unleash this life&#39;s most simple yet valuable secret to happiness and money we will never waste time for money. We won&#39;t waste life for money.&lt;br /&gt;
It is hard to put this into practise but once we start repeating it until it becomes a habit we can get the best of us. We will not regret wasting valuable time.&lt;br /&gt;
&lt;br /&gt;
Have a good day.&lt;/div&gt;
</content><link rel='replies' type='application/atom+xml' href='http://ineni.blogspot.com/feeds/8699837913987060249/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/8171940499402566116/8699837913987060249' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8171940499402566116/posts/default/8699837913987060249'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8171940499402566116/posts/default/8699837913987060249'/><link rel='alternate' type='text/html' href='http://ineni.blogspot.com/2016/05/value-of-time-vs-money.html' title='Value of Time vs Money'/><author><name>Sumanth</name><uri>http://www.blogger.com/profile/12832477486389303210</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8171940499402566116.post-6206059811784332943</id><published>2015-04-04T11:44:00.001-07:00</published><updated>2015-04-04T11:44:26.257-07:00</updated><title type='text'>Money Money Money</title><content type='html'>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;
&lt;br /&gt;
It is fascinating to think that money is such an important part of our world today. Because money is just an improvised version of barter system.&lt;br /&gt;
During the barter system only few human skills were useful - all related to the basic needs of humans. After barter system humans started using commodities to buy or sell various skills, these commodities ranged from precious metals like gold to consumables like wheat. This introduction of commodity money has allowed humans to measure value of a skill in a common denominator, this in turn allowed skills to blossom or I should say explode.&lt;br /&gt;
&lt;br /&gt;
The commodity money has changed to coins that are made of precious metal and endorsed by rules and finally took the form that we know it today. Just like everything else in the world the transformation of money is not going to stop here, there are signs that the electronic currency might be the future.&lt;br /&gt;
&lt;br /&gt;
While currency has solved various problems it has also created numerous new problems. Undue accumulation of wealth is the prime one. Though it looks like this accumulation is getting worse I would like to think otherwise. Just think of the days when rulers had vast amount of wealth and the rest of us just had enough to survive. I am not saying that today&#39;s world is much different to that but definitely better even if the improvement is infinitessimally small. Hopefully the situation improves as the time passes by.&lt;br /&gt;
&lt;br /&gt;
Today there are things that we can&#39;t yet measure in money, but the list of things that can&#39;t be measured is reducing fast and technology is the prime source aiding this reduction. As we keep adding items to the list of things that we can buy with money we keep imagining about new stuff that can&#39;t be bought and this goes on.&lt;br /&gt;
&lt;br /&gt;
Having a common measure is good in many ways but being as powerful as it is, it is easy to be abused. Technology should be able to solve this too and I am confident that there will be a day when technology helps level the playing field&lt;br /&gt;
&lt;br /&gt;
One of the effects of money is that it made us very competitive as it, being the arbitrary measure of most things in the world today, has allowed us to measure most of our possessions. As long as this competitiveness is helping us get better, without causing harm to others, it is all well and good but it is becoming more and more common that this competitiveness is turning into ugly battles.&lt;br /&gt;
&lt;br /&gt;
Hope humanity can see a day where no human being suffers for survival. Beyond that a healthy competition is always good for the progression of human race&lt;/div&gt;
</content><link rel='replies' type='application/atom+xml' href='http://ineni.blogspot.com/feeds/6206059811784332943/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/8171940499402566116/6206059811784332943' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8171940499402566116/posts/default/6206059811784332943'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8171940499402566116/posts/default/6206059811784332943'/><link rel='alternate' type='text/html' href='http://ineni.blogspot.com/2015/04/money-money-money.html' title='Money Money Money'/><author><name>Sumanth</name><uri>http://www.blogger.com/profile/12832477486389303210</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8171940499402566116.post-8704238419015630941</id><published>2014-02-09T13:45:00.000-08:00</published><updated>2014-03-19T14:59:50.688-07:00</updated><title type='text'>Various ways to react to a mistake</title><content type='html'>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;
&lt;div class=&quot;MsoNormal&quot; style=&quot;text-align: left;&quot;&gt;
When a person makes a mistake it is fascinating to see how they
respond. Based on the situation and nature of the person who makes the mistake
there are various ways one can react. I tried to broadly divide the reactions into
following 7 categories:&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot; style=&quot;text-align: left;&quot;&gt;
&lt;/div&gt;
&lt;ol style=&quot;text-align: left;&quot;&gt;
&lt;li&gt;&lt;span style=&quot;text-indent: -18pt;&quot;&gt;&lt;b&gt;No I&amp;nbsp;didn&#39;t&amp;nbsp;make a mistake – I never do any!&amp;nbsp;&lt;/b&gt;&lt;/span&gt;&lt;br /&gt;&lt;span style=&quot;text-indent: -24px;&quot;&gt;This is the kind of response we give when we don’t want to agrees
to the mistakes we do. Even the mistakes of worst nature i.e. blunders would
not deter us from self-protection. This behaviour could be because the person
really believes that it&amp;nbsp;isn&#39;t&amp;nbsp;their mistake or it could be that the person
knows it&amp;nbsp;but&amp;nbsp;isn&#39;t&amp;nbsp;brave enough to accept the mistake.&amp;nbsp;&lt;/span&gt;&lt;span style=&quot;text-indent: -24px;&quot;&gt;The problem with this behaviour is that the person doesn&#39;t
learn from the mistakes and keep making them again and again. &amp;nbsp;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;div&gt;
&lt;b&gt;It’s not my mistake, I did it because...&lt;/b&gt;&lt;br /&gt;
Most of us use this in scenarios where we try to
find excuses for our short comings. The hard core section of this group of
people try to find a reason and believe that is unavoidable and not in one’s
control. Sometimes the reasons are so bizarre that the believing in the reason
itself becomes a mistake.This behaviour helps in reducing any sadness caused due to
the mistake as finding the reason, however absurd the reason might be, gives
the person a chance to be relieved of any guilt.&lt;/div&gt;
&lt;/li&gt;
&lt;li&gt;&lt;span style=&quot;text-indent: -18pt;&quot;&gt;&lt;b&gt;It’s others fault&lt;/b&gt;&lt;/span&gt;&lt;span style=&quot;text-indent: -24px;&quot;&gt;&lt;br /&gt;This kind of behaviour is almost similar to the one above
but it is different in a way that the reason we find is always other people
rather than things. At times the blame can be moved from one person to other
based on who is readily available to blame on&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span style=&quot;text-indent: -18pt;&quot;&gt;&lt;b&gt;Who are you to point out my mistakes!&lt;/b&gt;&lt;/span&gt;&lt;span style=&quot;text-indent: -24px;&quot;&gt;&lt;br /&gt;This is the reaction you get from people who are either
arrogant or really crossed about their mistake. The only problem is that this
leads to confrontation with the person who pointed out the mistake unless the other
person is composed&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span style=&quot;text-indent: -18pt;&quot;&gt;&lt;b&gt;Yeah I made a mistake so what?&lt;/b&gt;&lt;/span&gt;&lt;br /&gt;&lt;span style=&quot;text-indent: -24px;&quot;&gt;When the person “thinks” that the mistake is very small then
one gives this response. But this thinking might irritate others who bear the brunt
of the mistake. So it’s better to be humble to every mistake done and try to
think from others perspective.&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span style=&quot;text-indent: -18pt;&quot;&gt;&lt;b&gt;Oh sorry I made a mistake – will try not to
repeat&lt;/b&gt;&lt;/span&gt;&lt;br /&gt;&lt;span style=&quot;text-indent: -24px;&quot;&gt;This is probably the ideal response. As some famous person
said – one who doesn’t make any mistakes is not human – it is impossible to
lead a life without mistakes so the best thing to do is to not repeat the same
mistakes but try doing brand new ones. This is only possible if we learn from
the mistakes we make&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;b style=&quot;text-indent: -18pt;&quot;&gt;I made a mistake – I should make others life
hell with my apologies&lt;/b&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;span style=&quot;text-indent: -24px;&quot;&gt;When people think that their mistake is so naïve and/or horrible
they try to undo the mistake by apologising very hard. But this makes apologising
itself a bigger mistake than the original one. Yes one should apologise to
mistakes but should not go overboard. If the mistake is so bad that it caused irreversible
damage then it is better to show that you are sorry in action rather than just
by words which after some time becomes useless.&lt;/span&gt;&lt;br /&gt;
&lt;ol style=&quot;text-align: left;&quot;&gt;
&lt;/ol&gt;
&lt;div class=&quot;MsoNormal&quot; style=&quot;text-align: left;&quot;&gt;
&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot; style=&quot;text-align: left;&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot; style=&quot;text-align: left;&quot;&gt;
Though some of reactions are mistakes themselves every
person must have used almost all the kinds of reactions in various situations.
If making mistake is bad, not reacting appropriately is a blunder. As we keep
growing up we need to learn how to not repeat a mistake and this learning
starts from our response to mistakes.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;br /&gt;
&lt;div class=&quot;MsoNormal&quot; style=&quot;text-align: left;&quot;&gt;
Ideally we should all be humble to every mistake we make but
as we are human it is not possible, so the best we can do is to learn from them
and make learning a habit.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;/div&gt;
</content><link rel='replies' type='application/atom+xml' href='http://ineni.blogspot.com/feeds/8704238419015630941/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/8171940499402566116/8704238419015630941' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8171940499402566116/posts/default/8704238419015630941'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8171940499402566116/posts/default/8704238419015630941'/><link rel='alternate' type='text/html' href='http://ineni.blogspot.com/2014/02/various-way-to-react-to-mistake.html' title='Various ways to react to a mistake'/><author><name>Sumanth</name><uri>http://www.blogger.com/profile/12832477486389303210</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8171940499402566116.post-5760743135724987563</id><published>2013-09-28T05:11:00.002-07:00</published><updated>2013-09-28T05:11:38.088-07:00</updated><title type='text'>Time for a United Telugu Front</title><content type='html'>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
Past few years have been stressful for a person of Telugu
origin, be it a supporter of separate state or in favour of a unified state.
The agitations had a bad impact on the economy of the state, which at one
point, not distant past, has been the most talked about for its booming economy.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
People in favour of a separate state for Telangana should
not misunderstand ‘United Telugu Front’ to a ‘Unified State’. Regardless of
Telangana state being formed or not it is apparent that a deep division has
been created between Telugu people from Telangana and Non-Telangana region
because of vested interests of Politicians and so called well-wishers. This
division should be cured with utmost urgency and care, otherwise Telugu people
will only have failed state(s). Idea behind ‘United Telugu Front’ is to have a common
organisation for Telugu people which is non-political and which helps us fight
as a single force.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
It is very clear, after the issue of bail to a political
leader, that central government doesn&#39;t care about us, the common man, of the
state. As long as they win in next general elections they are ready to do
literally anything. Sadly this is the state of every major political party,
there are one or two small political parties that are an exception but they
don’t get any media coverage as they don’t have their own media house.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
Regardless of Telangana state formed or not we, the Telugu
people, should be united. Unity is the only way we can keep the corrupt
political leaders at bay. We can’t do the same mistake we did few hundred years
ago when British rulers started taking control of our land.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
Today, apart from Telangana statehood issue Telugu people
are suffering from other grave issues like share of water from other states, failing
agricultural system and poverty among many others. We have been depending on our
elected governments to solve these problems for many decades now and they
failed us miserably, not because they couldn&#39;t solve but just because political
parties thrive on keeping these issues alive. If we don’t do anything and rely
on governments believe me these issues will still remain for generations to
come.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
Why should we leave the issue of separate state, which is
very sensitive and of utmost importance to us and our future generations, in the hands of our political leaders? Why should we keep
waiting for statements from central government, which by the way doesn&#39;t know a
damn about us or our problems? Why can&#39;t we discuss among ourselves on all the
problems we are experiencing and come to a peaceful, useful and importantly a
common decision?&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
Under the united front we shall openly discuss among
ourselves about pros and cons of having one or two states. After extensive
discussion on all the issues regarding separate state we can come to a common
conclusion, not a Telangana people or Andhra people conclusion but a Telugu
peoples&#39; conclusion. If the decision is in favour of separate state we should
discuss on how assets and liabilities will be divided, we should discuss how
each new state will be helped by the other to develop, being administered by
two different governments does not mean that Telugu people can’t be united. If
the decision is in favour of having a single state then we should discuss on
how to solve the root causes of the agitation.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;













&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
Lastly after seeing all the news about the games our
political parties are playing with our beliefs I hope we make a turning that
brings joy to any true Telugite.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;/div&gt;
</content><link rel='replies' type='application/atom+xml' href='http://ineni.blogspot.com/feeds/5760743135724987563/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/8171940499402566116/5760743135724987563' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8171940499402566116/posts/default/5760743135724987563'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8171940499402566116/posts/default/5760743135724987563'/><link rel='alternate' type='text/html' href='http://ineni.blogspot.com/2013/09/time-for-united-telugu-front.html' title='Time for a United Telugu Front'/><author><name>Sumanth</name><uri>http://www.blogger.com/profile/12832477486389303210</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8171940499402566116.post-2604356168664741741</id><published>2012-04-22T09:39:00.000-07:00</published><updated>2012-04-22T09:39:05.278-07:00</updated><title type='text'>Is caste system really bad?</title><content type='html'>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;
&lt;br /&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
Most of us, if not all of us, have said at some point that
caste system should end for the good of society. I don’t actually disagree with
that and until recently I am a strong supporter of that idea. But after some thinking
during recent weeks I started to have second thoughts about it.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
Castes in the region I come from are mainly formed on the
basis of their profession. Like priests are Brahmins, Gold smiths are Kamsali,
Carpenters are Vadrangi and so on. This isn’t true for all castes but it can be
fairly generalised. And in the days they are formed these professions are
hereditary. So, this way of grouping similar profession people into a caste makes
a lot of sense and in fact is very beneficial in providing unity and provides a
platform to exchange new ideas and improve the professions. If the caste system
remained to just grouping people from similar professionals it would have never
gone into the troubled waters as it is now. &lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
Caste system has become unpopular because of some obvious and
some not so obvious reasons. The fact that caste system was and sadly is used
for discriminating people is one of the very obvious reasons. Discrimination
among humans based on anything should be absolutely and strongly condemned. So,
in that respect caste system has no place to exist in the modern age. One of
the not so obvious bad effects of caste system is the fact that some of the
castes have got a rare gene disease because of lack of gene mutation which is a
result of intra caste marriage system. &lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
Along with these two there are many other problems caused by
caste system which has no place in this age of globalisation.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
Having mentioned the issues of caste system it is not all
bad after all. Caste system has its own benefits even today. There are caste level
organisations which provide services like free food, free education, subsidised
training and others. Also caste system brings in the unity that it was
initially intended for. &lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
End of the day caste system is a kind of division system. If
division based on religion and region are accepted then so is the division
based on caste. If we are happy to fight for our region what is wrong by
fighting for a caste as long as the fights are for a good cause.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
There are currently numerous division systems based on
religion, country, state, region, financial and social status and so on and so
forth. Just recently one of the regions in the state I was born in was fighting
with other and this is as bad as the discrimination in caste system. So as long
as there are divisions in the world irrespective of what they are based on
there will be trouble if they lose the ability to tolerate other divisions. &lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
Caste system has the power to unite people from several
parts of world. If this power is used for good purposes then caste system can
have a very long future and it can turn out to be a good source of empowerment
to various individuals.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
So, if people who believe in caste system can increase their
tolerance towards other castes and respect other castes then yes caste system
can be good for the society and can be used for better purposes.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://ineni.blogspot.com/feeds/2604356168664741741/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/8171940499402566116/2604356168664741741' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8171940499402566116/posts/default/2604356168664741741'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8171940499402566116/posts/default/2604356168664741741'/><link rel='alternate' type='text/html' href='http://ineni.blogspot.com/2012/04/is-caste-system-really-bad.html' title='Is caste system really bad?'/><author><name>Sumanth</name><uri>http://www.blogger.com/profile/12832477486389303210</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8171940499402566116.post-8576791357812714430</id><published>2012-04-09T05:00:00.000-07:00</published><updated>2012-04-09T05:00:11.028-07:00</updated><title type='text'>Autonomous Working</title><content type='html'>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;
&lt;br /&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
Some recent studies highlighted that humans are more
creative in solving problems and coming up with new ideas when they are allowed
to work on their own, without any management control or guidelines. Though the
concept sounds new and radical for technology professional like me, where
management has major say on individual’s work, this isn’t new to the world of
scientists and research professionals. &lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
As technological revolution started after industrialisation most
of the technology firms have an organisation structure similar to manufacturing
companies which is a hierarchical structure where every person has a boss and he/she
works according to what the boss decides. This caused innovation to stall and
most of the innovations came from new start-ups or individuals who had the
freedom of working on their own terms. &lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
In todays’ world of patent wars technology companies can
survive and outpace their rivals only if they can come up with futuristic
technologies before their rivals does, or they should be bidding for new
start-ups who has a better technology. This huge reliance on innovation has led
to the above mentioned studies, whose results make us think ‘Isn’t it obvious’.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
So the outcome of all the competition and these studies has
resulted in some major organisation implementing ‘Autonomous Working’ as a
pilot project. So, the employees who are part of autonomous working group can
do whatever they want and in fact work whenever they want to. So, in essence &lt;b&gt;they are their own boss,&lt;/b&gt; except that
they don’t get all the money their work is going to generate, if it does
generate anyway.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
This new concept is slowly but surely gaining ground and
today such autonomous groups are present in all the major companies who strive
on innovations. But can this new concept ever be implemented across the board?
I doubt that it would, at least I can’t see it happening in my lifetime. The
main reason for my scepticism is that even though the new structure brings
innovations it doesn’t work well in majority of other situations. For example
if the new innovations have to take shape they need to be developed by a group
of people and this group of developers have to work according to specifications
of the new innovation. So, though autonomous work groups are a great idea it still
needs the help of classic hierarchical organisation structure to get the innovation
to market.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
I might be wrong and some day there might be another
research which makes me think ‘How did I miss that’. But for now I can’t see
the death of management in the world of technology where innovation is the cog
for survival.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://ineni.blogspot.com/feeds/8576791357812714430/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/8171940499402566116/8576791357812714430' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8171940499402566116/posts/default/8576791357812714430'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8171940499402566116/posts/default/8576791357812714430'/><link rel='alternate' type='text/html' href='http://ineni.blogspot.com/2012/04/autonomous-working.html' title='Autonomous Working'/><author><name>Sumanth</name><uri>http://www.blogger.com/profile/12832477486389303210</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8171940499402566116.post-5973002987974826397</id><published>2012-03-14T15:20:00.000-07:00</published><updated>2012-03-14T15:20:05.148-07:00</updated><title type='text'>Art of Storytelling</title><content type='html'>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;
&lt;br /&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
One day I was driving back home through a deserted road
after a hectic day at office. It was already late in the night and except the head lamps of my car there is no other light source that is visible. I was cruising along at around
the prescribed speed limit and suddenly my car started to make some unusual noise. This
noise gradually increased and all of a sudden my car shuddered to a halt with a
big bang. I switched on the hazard lights, pulled the lever to open the bonnet,
jumped out of the car and opened the bonnet and as I am not very good at car
mechanics couldn&#39;t find any obvious fault. I was feeling more resigned than frustrated
and slowly closed the bonnet. When I looked around I realised that I was in the
middle of no-where and my car&#39;s hazard lights are the only lights I could see.
I quickly pulled out my mobile, searched for the entry of&amp;nbsp;car recovery company&amp;nbsp; in the
contacts and dialled it. Immediately after dialling I heard &#39;No network
coverage in your area&#39;. My heart sank and I couldn&#39;t think of any other
alternative. I looked at both sides of the road to see if there is any vehicle
coming my way, but nothing came for the next half an house. After thinking
through various options, including walking along the road until I find some
help, I decided that none of them are safe. So finally decided to stay in my
car for the rest of the night and find some help in the morning. So I got back
into my car, closed the door, pulled back my seat and started to relax and suddenly I saw something strange racing my way...&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
And the story continues. This is my attempt at describing a
small incident. After reading the above paragraph it should be pretty obvious
that I don&#39;t possess the great art of storytelling. But if my parents or grandparents
narrated the same story it would have been very interesting and gripping to read with lot more
detail.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
In this age where people prefer to
watch videos or animations rather than reading an article it is not hard to
understand the reason why the art of storytelling is dying at such a fast pace.
Sadly I can’t say that this is wrong for humankind. In the process of evolution
humans lost various skills which are once thought to be essential and acquire
new skills. In the same way we are in the process of losing the skill of
storytelling. I am afraid that the future of storytelling isn’t looking very
bright. I can only hope that this is just another step in human evolution and
it is for the sake of good.&lt;/div&gt;
&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://ineni.blogspot.com/feeds/5973002987974826397/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/8171940499402566116/5973002987974826397' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8171940499402566116/posts/default/5973002987974826397'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8171940499402566116/posts/default/5973002987974826397'/><link rel='alternate' type='text/html' href='http://ineni.blogspot.com/2012/03/art-of-storytelling.html' title='Art of Storytelling'/><author><name>Sumanth</name><uri>http://www.blogger.com/profile/12832477486389303210</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8171940499402566116.post-7915405901956327337</id><published>2011-10-22T02:22:00.001-07:00</published><updated>2011-10-22T02:22:58.261-07:00</updated><title type='text'>Agile Scrum Estimation</title><content type='html'>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;
&lt;br /&gt;
In this article I will try to explain the estimation process in Agile Scrum methodologies.&lt;br /&gt;
&lt;br /&gt;
Before going into details here is just an advice: As the team has to estimate for every sprint it is a&lt;br /&gt;
good practice to follow same principles right from the first sprint and keep improving or modifying&lt;br /&gt;
the process as you progress through the project, but never completely ditch the process and start&lt;br /&gt;
afresh, unless every member of the team is completely at ease with the new process changing to a&lt;br /&gt;
brand new process will cause confusion above the team and all the lessons learned in all previous&lt;br /&gt;
sprints will be lost.&lt;br /&gt;
&lt;br /&gt;
While using Scrum each item chosen to be developed in the sprint have to be estimated. Now&lt;br /&gt;
this estimation process is drastically different to the old practices like single person estimating for&lt;br /&gt;
the whole work and on behalf of the entire team or each developer estimating their own work in&lt;br /&gt;
isolation.&lt;br /&gt;
&lt;br /&gt;
Estimation process in Scrum helps to bring the whole team work as a single unit rather than&lt;br /&gt;
individuals. So, what it suggests is to have a meeting exclusively for estimating all the work that is&lt;br /&gt;
planned for next commencing sprint. All team members should attend the meeting along with the&lt;br /&gt;
manager, testers, developers, business analysts and also the end user. Feel free to call up any other&lt;br /&gt;
stake holders if you deem are important for the development process.&lt;br /&gt;
&lt;br /&gt;
Take up each requirement and analyse it in detail with in the team, unless the requirement is very&lt;br /&gt;
straight forward there should be some questions raised and subsequently answered by different&lt;br /&gt;
members of the team. Once the requirement is satisfactorily understood by all parts of the team&lt;br /&gt;
every member of the team except the end user and business analysts estimate the complexity of the&lt;br /&gt;
requirement. This complexity should be from a set of Fibonacci series – 1,2,3,5,8,13 etc.&lt;br /&gt;
&lt;br /&gt;
Every estimating member should estimate the complexity in isolation, so poker style estimation is&lt;br /&gt;
a popular practice. But feel free to be creative. If the estimations of team are not same then the&lt;br /&gt;
reasons behind this variance is understood by asking the reasons behind each developers’ estimate.&lt;br /&gt;
This way the requirement is further discussed and everyone will have a better understanding of&lt;br /&gt;
the complexities involved in the requirement. Carry out the estimation process again and the&lt;br /&gt;
estimations should narrow down, repeat this until variance of estimations from all the members falls&lt;br /&gt;
within reasonable limits.&lt;br /&gt;
&lt;br /&gt;
Carry out this process for all other requirements chosen for next sprint.&lt;br /&gt;
&lt;br /&gt;
Based on the estimated complexity and the velocity of the team you can work out how many of the&lt;br /&gt;
planned requirements can be completed in the sprint. If all planned requirements doesn’t fit in the&lt;br /&gt;
sprint then chose the requirements in the order of their priority.&lt;br /&gt;
&lt;br /&gt;
Some teams also allocate the requirements to individuals as part of this meeting, but this isn’t&lt;br /&gt;
mandatory.&lt;br /&gt;
&lt;br /&gt;
Following this process will make sure that the entire team works in unison and every member of&lt;br /&gt;
the team will have exact idea of the work load. And more importantly the end user expectations are&lt;br /&gt;
pegged to what the team can achieve, not more and not less.&lt;br /&gt;
&lt;br /&gt;
Finally, don’t blindly follow this process. Though the above explained process works most of the time&lt;br /&gt;
and is a major improvement to the prevailing practices there might be instances where it doesn’t&lt;br /&gt;
work or where there need some minor tweaks. So feel free to come up with your own process. Agile&lt;br /&gt;
is all about adapting to the circumstances. If anything in the entire agile process isn’t working for&lt;br /&gt;
your project then try to mend it. There is no hard and fast rule of what is correct and what is wrong&lt;br /&gt;
it all depends on circumstances.&lt;br /&gt;
&lt;br /&gt;
Feel free to throw any questions you have at me, I shall try my best to answer them.&lt;br /&gt;
&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://ineni.blogspot.com/feeds/7915405901956327337/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/8171940499402566116/7915405901956327337' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8171940499402566116/posts/default/7915405901956327337'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8171940499402566116/posts/default/7915405901956327337'/><link rel='alternate' type='text/html' href='http://ineni.blogspot.com/2011/10/agile-scrum-estimation.html' title='Agile Scrum Estimation'/><author><name>Sumanth</name><uri>http://www.blogger.com/profile/12832477486389303210</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8171940499402566116.post-855060047587717989</id><published>2011-10-14T12:24:00.000-07:00</published><updated>2011-10-14T12:24:03.626-07:00</updated><title type='text'>Agile Methodologies</title><content type='html'>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;&lt;br /&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;These days ‘Agile’ has become so prevalent that every developer must have come across this word. The word in the market is that Agile is the best way forward, though this isn’t true for every project developed but true for many of them.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;&lt;div class=&quot;MsoNormal&quot;&gt;&lt;br /&gt;
&lt;/div&gt;&lt;div class=&quot;MsoNormal&quot;&gt;In this article I want to introduce you to Agile, if you just heard the word ‘Agile’ and want to know a bit more then you came to the right place.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;&lt;div class=&quot;MsoNormal&quot;&gt;&lt;br /&gt;
&lt;/div&gt;&lt;div class=&quot;MsoNormal&quot;&gt;Agile is actually a simple development methodology, there are various types of Agile methodologies but all of them are closely related to each other and have same overall principles. In this article I shall details the overall principles that all the agile methodologies follow. It may be the case that I speak mainly about ‘Scrum’ methodology as I worked mostly in projects that used Scrum.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;&lt;div class=&quot;MsoNormal&quot;&gt;&lt;br /&gt;
&lt;/div&gt;&lt;div class=&quot;MsoNormal&quot;&gt;Before agile has been introduced all the software development projects has more or less the following lifecycle:&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;&lt;div class=&quot;MsoNormal&quot;&gt;Requirement gathering -&amp;gt; Analysis -&amp;gt; Design -&amp;gt; Develop -&amp;gt; Test -&amp;gt; UAT Deploy -&amp;gt; UAT -&amp;gt; Live&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;&lt;div class=&quot;MsoNormal&quot;&gt;&lt;br /&gt;
&lt;/div&gt;&lt;div class=&quot;MsoNormal&quot;&gt;Each stage of this cycle was carried out once for the entire project. All the requirements analysed once for the whole project, design the entire system at a single go, developed the whole system according to the analysed requirements and so on. The problem with this mainly comes from the important stakeholder of any software project, the end user. The end user changes his/her mind as they see different systems or as they start using the system. Because of this the end product after the entire lifecycle isn’t always according to the user’s exact needs/wants.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;&lt;div class=&quot;MsoNormal&quot;&gt;&lt;br /&gt;
&lt;/div&gt;&lt;div class=&quot;MsoNormal&quot;&gt;Now agile tries to solve this problem by carrying out parts of the above lifecycle multiple times over entire life cycle of the project. So, it looks something like this:&lt;/div&gt;&lt;div class=&quot;MsoNormal&quot;&gt;&lt;/div&gt;&lt;ol style=&quot;text-align: left;&quot;&gt;&lt;li&gt;High level requirement gathering&lt;/li&gt;
&lt;li&gt;Requirement analysis [for small set of requirements]&lt;/li&gt;
&lt;li&gt;Design&lt;/li&gt;
&lt;li&gt;Develop&lt;/li&gt;
&lt;li&gt;Test&lt;/li&gt;
&lt;li&gt;UAT [Go to Step 2 for next iteration]&lt;/li&gt;
&lt;li&gt;Live&lt;/li&gt;
&lt;/ol&gt;&lt;br /&gt;
&lt;div class=&quot;MsoListParagraphCxSpLast&quot; style=&quot;mso-list: l1 level1 lfo1; text-indent: -18.0pt;&quot;&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;&lt;div class=&quot;MsoNormal&quot;&gt;Note: The loop can carry on until live but this depends on the type of system being developed&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;&lt;div class=&quot;MsoNormal&quot;&gt;&lt;br /&gt;
&lt;/div&gt;&lt;div class=&quot;MsoNormal&quot;&gt;What’s happening here is that the requirements are broken down into chunks and the process of designing, develop, test and UAT are carried out for this chunk of requirements. This doesn’t work with bad design, so agile insists on having good design.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;&lt;div class=&quot;MsoNormal&quot;&gt;&lt;br /&gt;
&lt;/div&gt;&lt;div class=&quot;MsoNormal&quot;&gt;At the end of developing for each chunk of requirements the system is shown to the end user and the next set of requirements are gathered. This helps the end user to have a continuous look at the outcome of the project rather than being a surprise at the end of the whole project and also gives the flexibility of changing the requirements as the project progresses.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;&lt;div class=&quot;MsoNormal&quot;&gt;&lt;br /&gt;
&lt;/div&gt;&lt;div class=&quot;MsoNormal&quot;&gt;This is just a high level view of Agile and there is a lot more involved but you get to know them once you start following these methodologies.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;&lt;div class=&quot;MsoNormal&quot;&gt;&lt;br /&gt;
&lt;/div&gt;&lt;div class=&quot;MsoNormal&quot;&gt;There are some keywords used in this methodology, just like any other methodology, which I shall just touch base:&lt;/div&gt;&lt;div class=&quot;MsoNormal&quot;&gt;&lt;/div&gt;&lt;ol style=&quot;text-align: left;&quot;&gt;&lt;li&gt;&lt;b&gt;Sprint&lt;/b&gt;: Each iteration of the above development process loop is called as a sprint. Each sprint can span for a minimum of a week to a maximum of four weeks. The sprint starts when the next set of requirements are analysed, to the point the code is deployed for UAT or even Live. Over the lifecycle of the project it is advised to keep the length of a sprint to constant.&lt;/li&gt;
&lt;li&gt;&lt;b&gt;Scrum&lt;/b&gt;: As the sprint length is short there is very little scope to lose track of the project, so the whole team comes together every day and each person briefly explains what he/she has done last day, say what they are going to do today and inform of any dependency on anything or any other team member. This meeting is called scrum. Now there are some guidelines about people who should attend and who should speak in this meeting. I shall explain this sometime later but keep in mind that agile works only if you customise it to suit your project, so feel free to define your own rules. One main point to remember though is to keep this meeting to the minimum possible length and take any long discussions out of this meeting.&lt;/li&gt;
&lt;li&gt;&lt;b&gt;Sprint Planning and Estimation&lt;/b&gt;: This is the meeting at the beginning of each sprint where the requirements are detailed by the business user, the development team queries are clarified and each requirement prioritised. Each requirement is also estimated during this meeting by the whole development team so that it can be decided on what requirements fit into the sprint.&lt;/li&gt;
&lt;li&gt;&lt;b&gt;Sprint Retrospective&lt;/b&gt;: This is another meeting where the team comes together at the end of every sprint and discusses how the completed sprint has been. All kinds of issues are discussed during this meeting, personal, technical or external, everything that is affecting the project, so that they can be resolved for next sprint and the development can be smoother. It is very important to have this meeting and resolve the issues that are raised during this meeting. Also during this meeting all the good points are mentioned as well, this is as crucial as raising issues as it helps in motivating the team and also helps in identifying where they are improving and where they are not.&lt;/li&gt;
&lt;li&gt;&lt;b&gt;Sprint Demo&lt;/b&gt;: This is the meeting at the end of the sprint where the whole team will give the demo of features developed during the sprint to business users. Sprint planning and estimations follows this meeting. So, it might be a good idea to do these two meeting immediately one after the other.&lt;/li&gt;
&lt;li&gt;&lt;b&gt;Velocity&lt;/b&gt;: This is a bit tricky to understand but for this introductory article I shall just put it in easy terms. This is the speed at which the team is developing. This figure will be low at the beginning of the project and should increase as project progresses. If it isn’t increasing then the team need to figure out why it isn’t and take necessary measures.&lt;/li&gt;
&lt;li&gt;&lt;b&gt;Story Points&lt;/b&gt;: This is the complexity involved in delivering each requirement. It is advised to estimate the effort involved for each requirement in story points, so that the velocity can be measured, but if you are happy to estimate in hours then go ahead with that, it doesn’t fail your project but it is hard to calculate the velocity and thus harder to see if the team performance is increasing or decreasing. Story points are normally numbers from Fibonacci series, so an item complexity could be 1, 2, 3,5,8,13,21 etc.&lt;/li&gt;
&lt;li&gt;&lt;b&gt;Product backlog items&lt;/b&gt;: This is the set of high level requirements that are gathered at beginning of the project for the whole project - well known in its short form of PBI.&lt;/li&gt;
&lt;li&gt;&lt;b&gt;Sprint backlog items&lt;/b&gt;: These are the set of requirements that are taken up to develop during a sprint. SBI should be a subset of PBI. There are some rules defined about PBI and SBI but again feel free to write your own according to your project demands.&lt;/li&gt;
&lt;/ol&gt;&lt;br /&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;&lt;br /&gt;
&lt;/div&gt;&lt;div class=&quot;MsoListParagraphCxSpLast&quot; style=&quot;mso-list: l0 level1 lfo2; text-indent: -18.0pt;&quot;&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;&lt;div class=&quot;MsoNormal&quot;&gt;There might be few more terms that I forgot to mention but these terms should let you get started and understand if someone is speaking about Agile.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;&lt;div class=&quot;MsoNormal&quot;&gt;&lt;br /&gt;
&lt;/div&gt;&lt;div class=&quot;MsoNormal&quot;&gt;Keep in mind that Agile works best if it is used as a guideline and when the process is customised according to the requirements of the project rather than strictly following it to the word.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://ineni.blogspot.com/feeds/855060047587717989/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/8171940499402566116/855060047587717989' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8171940499402566116/posts/default/855060047587717989'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8171940499402566116/posts/default/855060047587717989'/><link rel='alternate' type='text/html' href='http://ineni.blogspot.com/2011/10/agile-methodologies.html' title='Agile Methodologies'/><author><name>Sumanth</name><uri>http://www.blogger.com/profile/12832477486389303210</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8171940499402566116.post-3601730931154991697</id><published>2011-10-14T12:15:00.000-07:00</published><updated>2011-10-14T12:15:10.065-07:00</updated><title type='text'>Development Process</title><content type='html'>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;&lt;br /&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;I worked in different roles for different companies and in each role there was some talk about reviewing and optimizing development process as it was thought that the current process is either too laborious or too simplistic, yes too simplistic processes aren’t too good either. You might think that simple process is the way to go but not always. Let me explain.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;&lt;div class=&quot;MsoNormal&quot;&gt;&lt;br /&gt;
&lt;/div&gt;&lt;div class=&quot;MsoNormal&quot;&gt;If the team is working on a green field project, the development team is aware of the business domain, are technically capable of producing good code and detailed coding standards are defined at team or company level then simple process of [design-&amp;gt; develop-&amp;gt;test-&amp;gt;deploy] will work. But if this team has been working on this project for some time say 6 months and a new developer joins the team then this simple process will start to fail. By the time this developer joins the team there is already some code in place that is developed to certain standard and this developer doesn’t have any knowledge of the application that is being developed and so he tries to do something which, if badly designed, might break something else. So, in order to avoid such cases this development process is deemed too simplistic and review process loops are introduced between design, develop and test actions. So that someone with considerable understanding of the tool will avoid any code that has such ill side effects from being added to the solution.&lt;/div&gt;&lt;div class=&quot;MsoNormal&quot;&gt;&lt;br /&gt;
Now the review process, if not overdone, also improves the quality of the code in other ways. It helps in reducing the bugs because both design and development actions are thought twice and by two different people. Review process also helps the code to at a better standard which I will not go into too much detail. So, it is always suggested to have some sort of review process in the development lifecycle.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;&lt;div class=&quot;MsoNormal&quot;&gt;&lt;br /&gt;
&lt;/div&gt;&lt;div class=&quot;MsoNormal&quot;&gt;Now you might say, hey we found a solution to the problem! But unfortunately development is never that simple. There is a group involved in any IT development whose behaviour is absolutely unpredictable. This group of people are called by different names end user/customer/business user or whatever you want to call them. Introducing these chaps changes the dynamics of development with a huge margin. The ever changing mind of this group of people is the main cause of most of the IT projects failure. Add a business analyst to this situation and it gets really cumbersome. In order to tackle this problem project managers put in various kinds of contingencies but the one we are interested in are the changes to development process.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;&lt;div class=&quot;MsoNormal&quot;&gt;&lt;br /&gt;
&lt;/div&gt;&lt;div class=&quot;MsoNormal&quot;&gt;&lt;b&gt;&lt;u&gt;Agile&lt;/u&gt;&lt;/b&gt;: &lt;br /&gt;
One of the ways to deal with this chaos is to use agile methodologies where the requirements are gathered every few weeks and are signed off and frozen until they are completely developed. This process works well in most of the cases. But the methodologies need to be customised according to the project in order to see the results. These changes are not drastic changes but minor changes like level of documentation needed who attends the scrums, length of each sprint etc.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;&lt;div class=&quot;MsoNormal&quot;&gt;&lt;br /&gt;
&lt;/div&gt;&lt;div class=&quot;MsoNormal&quot;&gt;Anyway, there are certain scenarios where agile doesn’t fit the purpose. For example if the IT project is about adding new features to existing application and these feature requests come at irregular intervals and they need the changes without any delay – like can’t afford to wait until next sprint. Adding to this scenario if there is a support team who maintains the system and helps users use the system then the development process needs to be very different and also a bit involved as there are many stakeholders and multiple developments each at different stage of development cycle are carried out at the same time. And typically such applications life span is long enough to loose part of the team and add new members to the team. &lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;&lt;div class=&quot;MsoNormal&quot;&gt;&lt;br /&gt;
&lt;/div&gt;&lt;div class=&quot;MsoNormal&quot;&gt;All these will demand a stringent development process and checks at every stage. This is where most of the teams adopt a complex and laborious process which is complex to use and reduces the team efficiency.&lt;span&gt;&amp;nbsp; &lt;/span&gt;This makes the team think that they can improve the process, which they surely can.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;&lt;div class=&quot;MsoNormal&quot;&gt;&lt;br /&gt;
&lt;/div&gt;&lt;div class=&quot;MsoNormal&quot;&gt;Development process could be slick yet stringent. For example take a look at the following process:&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;&lt;div class=&quot;MsoNormal&quot;&gt;Requirement -&amp;gt; Review -&amp;gt; Design -&amp;gt; Review -&amp;gt;Develop -&amp;gt; Review -&amp;gt;Test-&amp;gt;deploy.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;&lt;div class=&quot;MsoNormal&quot;&gt;&lt;br /&gt;
&lt;/div&gt;&lt;div class=&quot;MsoNormal&quot;&gt;This isn’t too long compared to our previous process, but the main difference isn’t in the process but the way this process is implemented. At each of the non-review stages at least two people must be involved. This avoids too much dependency on single developer, reduces the bugs, improves coding standards and also improves the individual knowledge over technology and application. So, it is a win-win for both individual developer and the team.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;&lt;div class=&quot;MsoNormal&quot;&gt;&lt;br /&gt;
&lt;/div&gt;&lt;div class=&quot;MsoNormal&quot;&gt;Also it is suggested to involve the support team at the requirement or at least at design phase so that the knowledge transfer to the support team will not be laborious. It is not required for the support team to approve or make their presence felt, they just need to be added to the ‘cc’ list so that they are aware of the change before they go into the KT meeting.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;&lt;div class=&quot;MsoNormal&quot;&gt;&lt;br /&gt;
&lt;/div&gt;&lt;div class=&quot;MsoNormal&quot;&gt;Anyway that is my view about development process – different teams have different requirement and too simple process isn’t always the ideal solution and same with too laborious processes.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://ineni.blogspot.com/feeds/3601730931154991697/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/8171940499402566116/3601730931154991697' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8171940499402566116/posts/default/3601730931154991697'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8171940499402566116/posts/default/3601730931154991697'/><link rel='alternate' type='text/html' href='http://ineni.blogspot.com/2011/10/development-process.html' title='Development Process'/><author><name>Sumanth</name><uri>http://www.blogger.com/profile/12832477486389303210</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry></feed>