Creating QR Codes with Python
Serious About Your Software Career? Leave your job
5-Minute Beginner's Guide: Installing / Testin Redis and Node.js on OS X
Adding "Filter as you type" Support to IndexedDB
Apache Giraph: Distributed Graph Processing in the Cloud
Automata Invasion: Finite-State Technology in Lucene
CamelOne and JEEConf Wrap-Up | |
| BIRT 3.7 | |
| Written by: Michael Williams | |
| Featured Refcardz: Top Refcardz: | |
| 150+ Refcardz Available · Get them all | |
By coderfriendly
via coderfriendly.com
Published: Sep 25 2009 / 10:54
Comments
bageshsingh replied ago:
> nice one click to see more >
,> nice one click to see more >
bageshsingh replied ago:
http://www.bageshsingh.com nice one click to see more
Guy.Harel replied ago:
I agree. It is possible to model and develop a software in non-iterating phases, and deliver on time and on budget. It requires talented and experienced programmer. Agile says "dont do that, its wrong, dont think in advance, think during the dev process". This become attractive to inexperienced or unprooven programmers, since Agile allows them to do whatever they want, any mistake they want, no problem we will fix this in the next iteration. Most people I've seen doing Agile have been more concerned about playing being Agile and learning Scrum, than actually delivering a competive software in a competitive time.
bageshsingh replied ago:
yes i am agree with you thanks
http://www.bageshsingh.com
Voters For This Link (11)
Voters Against This Link (1)