Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

How to be a agile programmer? [closed]

Tags:

agile

I am a trainee in development sector. My Boss says that i should be an agile programmer.

I went through through the net and found some interesting things about agile programming. Being a newbee how should I start with agile?
What should be my first step in Agile programming?

At present I am in pair programming. But it's not exactly pair programming as I am just watching what my co-developer is doing. I also wish to be an agile developer.
Can you suggest a way for me stepwise?

I wish to develop myself and also my programming skills.

like image 241
IamIronMAN Avatar asked Oct 03 '10 14:10

IamIronMAN


People also ask

Is working in Agile stressful?

Agile can be stressful. Yes, really. Any time you embrace change, change happens. And change can be stressful, especially when it happens all the time.

Does Agile require coding?

Agile is not a programming language. Agile is not even a framework. Agile can best be described as a mindset or a set of principles to help developers produce the work in an efficient and sustainable way.


2 Answers

The keyword is Courage.

Courage to estimate and discuss your work

Courage to start work on small stories with insufficient detail

Courage to talk to customers to elaborate said stories

Courage to constructively critique team members code

Courage to review your mistakes (in public) and learn from them

Courage to release "unfinished but good and shippable" code when it already delivers value.

Courage to stick to the agreed team processes when management has a bright idea

Courage to amend agreed processes in team when a better way is found

Courage to deliver high quality code using test driven development and continuous integration.

...

Note: The unfinished part does not mean "low quality", it means satisfying the customer, cleanly implemented, tested, ship-ready. However falling short of the developers idea of perfection, i.e. spring configuration is a bit clunky, some refactoring can be made, some auto configuration, some speed improvement, some corner cases... I found that some developers take the "user story hostage" and keep it unshippable till it is perfect. If it is good, you should let go, better is for the next sprint.

like image 178
Peter Tillemans Avatar answered Sep 19 '22 09:09

Peter Tillemans


In my organization, all you have to do is declare yourself to be an Agile Programmer. Magically, the need for planning and documentation disappears.

like image 28
Dave Avatar answered Sep 18 '22 09:09

Dave