Friday, July 25, 2008
Professionalism = Knowledge First, Experience Last
Very interesting comparison of doctor with 20 years of experience and what is a difference having long years of experience and being professional. Read the article here.
Saturday, July 12, 2008
Agile Failures
To be able to learn how to avoid common pitfalls it is not enough to read about agile success. Even maybe more important is to read abut agile failures. Only when you know what happened on other projects, what went wrong, and how this situation could be avoided you can really improve your agile skills. On Scrum Alliance wiki there is place to document Agile/Scrum failures. Link to the page is here.
Friday, July 11, 2008
10 Principles of Agile Project Time Management
Just excellent post. All 10 points are excellent. You should really read this from time to time. Original link is here.
Wednesday, July 9, 2008
Another reason to try agile development
Read a very interesting blog and very interesting reasoning why it was decided in waterfall company to start using agile process. Original post is here.
Saturday, July 5, 2008
Affinity Estimating: A How-To
If you need an advice how to estimate size (not effort) of the project following post is very interesting. You will learn how to estimate rougher and make even finer size estimation. Have a look at the original post.
Thursday, July 3, 2008
The Simplest Thing That Could Possibly Work
What “The Simplest Thing That Could Possibly Work.” in agile means?
One of the principles of Agile, mostly related to design and architecture, is “The Simplest Thing That Could Possibly Work.” This is sometimes interpreted as “take every shortcut” or “slap something together.” But that is not the intention. A better way to express it would probably be something like “The Simplest Solution That Could Possibly Satisfy Your Requirements.” For instance, if you have a requirement to create the back end for a web site like amazon.com, then while a perl/cgi solution on a single core machine could possibly “work,” it doesn’t work from the point of view of high availability, fast response time, or reliability. Continue reading on http://damonpoole.blogspot.com/2008/07/simplest-thing-that-could-possibly-work.html
One of the principles of Agile, mostly related to design and architecture, is “The Simplest Thing That Could Possibly Work.” This is sometimes interpreted as “take every shortcut” or “slap something together.” But that is not the intention. A better way to express it would probably be something like “The Simplest Solution That Could Possibly Satisfy Your Requirements.” For instance, if you have a requirement to create the back end for a web site like amazon.com, then while a perl/cgi solution on a single core machine could possibly “work,” it doesn’t work from the point of view of high availability, fast response time, or reliability. Continue reading on http://damonpoole.blogspot.com/2008/07/simplest-thing-that-could-possibly-work.html
Tuesday, July 1, 2008
Agile: Is, Is Not, May Be
Very interesting thought on Agile, what agile is and what it can became if we are not careful. Can you really be agile if you are doing detailed design upfront, or do UI specification before project is started. Have a look at this post and opinion about it http://xprogramming.com/xpmag/jatAgileIsIsNotMayBe.htm
Subscribe to:
Comments (Atom)