Lets try Extreme Programming-Day 1

Ritu — Thu, 11 Dec 2008 12:37:31 +0000

Well I am reading a book on XP (Extreme Programming)currently and by almost every page its quoting the best amongst the good programming practices. The great part about XP is that though it is named as XP, if we apply the same practices in general life it can make our sailing smooth. I will be quoting some of them here time by time.

So today’s quotes are:

“XP is about the process of becoming more of our best selves and in the process our best as developers.”

“Good relationships lead to good business.”

“Leave yourself exposed and prepare for success. Dont scare.”

“People aren’t computers.”

VERY INTERESTING ONE HERE…

“Its not my job to manage someone else’s expectation. Its’s there job to match there expectation. It’s my job to do my best and to communicate clearly.”

“XP is fully appreciating yourself for total effort today and striving to do better tomorrow.”

What I learnt today:
There are values which programmer thinks are good for program/team/company/himself. And there are practices which make them apply these values. These both are complimentary. Good practice enhance the role of value and good values escalates the adoption through practice. Together they become principles.

Team Work: A key to success

Ritu — Tue, 05 Jun 2007 11:04:56 +0000

You will say whats new in this… everybody know that working in teams is lot more effective then working individually. Well i must say i am not going to write anything new but what i am writing here are the points which everyone knows but only few of us follows. The success of a team depends totally on the attitude of team members. I just want to highlight some points to remember as a member of an agile team…

Learn to Listen

Want people to listen to you…then first start listening to them.

Criticize idea not People

If there’s a substantial risk that you will be ridiculed or that you’ll lose face for suggesting an idea, you won’t be inclined to offer another suggestion.

Only outcome is important not credit/blame

In the end only result is what is worth so individual credit/blame are all exercise to kill precious time actually.

Quick fixes become Quicksand

As said above outcome is important.A minor quick fix can revert the whole result in a big picture.Never ever go for it.

Understand Pareto’s Principle

Pareto’s Principle, the 80/20 Rule, should serve as a daily reminder to focus 80 percent of your time and energy on the 20 percent of you work that is really important. Don’t just “work smart”, work smart on the right things.

In last Remember the team work’s motto “none of us is as good as all of us“.

See my favourite example of teamwork…

Ruby, Rails and Ritu » agile