Agile Programming : Just a Common Sense

Do you wanna go wild and extreme in software development methodology ?
Go Agile.Agile is cool and easy way to clear up all the mess created by managerial development in software industry . This kills all the bosses who give a sar smile and drinking coffee when you burn your ass . Well I mean in a hard way that it gives clear transparency between customer who buys and labor who implements.

Why Agile ?
Simple customer is the one knows what he want and labor are the one who does it . So these two entity should be tightly communicated. Picture explains how the information flow in agile environment.



Agile for God of dummies :
It has two important terminologies

1. product backlog -> Wish list of Customers
2. sprint backlog -> Work list of Labors

So every 30 days they take one wish list from product backlog basket and put it sprint backlog basket . So then labor implements it .

Terms & practices :

Scrum : In practical means as a team work of doing something .Taken from Rugby And word web describes that as (The method of beginning play in which the forwards of each team crouch side by side with locked arms; play starts when the ball thrown in between them and the two sides compete for possession)
Scrum master : A Chinese drunken master who knows everything about scrum practices. His job is to interact with different scrum teams.
Scrum Cycle : once in 24 hours meeting & 1 month of sprint backlog implementation.

Peer Programming : Instead of one developer thinking on his own . Group with another one and think with two brains . (Hehee:We all know one brain could make a great mess and other brain can clear it . So the net result is zero )





Adv :

• Less process headache
• Clear visibility of what you are doing
• Less intermediate from Customer to Labor
• Fast adaptation for changes
• Clear communication inside team since it supports peer programming
  

DisAdv :

• No idea how the changes could affect old design
• If the peer sucks then the whole work will go down , since there is no other check points.
  
• No clear idea how the bugs are fixed ( If someone please comment on this)
• Demands more skills than required . (For example a requirement manager should know little bit coding too ?? )

Read this Blog to get an alternative View :
http://lukehalliwell.wordpress.com/2008/11/16/the-agile-disease/