Browse by Tags
All Tags »
Agile (RSS)
Sorry, but there are no more tags available to filter with.
6) Reduce unnecessary communication Agile developement reduce unnecessary communication by keeping things simple Instead of having complicated design for an application, the application is breaking down into simple user story. It keeps every people involved
Read More...
I was working in C# team for almost 7 years as a software design enginner in Test. I learn a ton of things from there and the most important things is that I almost meet a lot of smart people from there. After a lot of thinking and personal reasons, I
Read More...
5) Reactive I’ll explain this using a “see doctor” analogy. illness == problem need to solve cure the illness == software developed which solve the problem Analogy When you are sick, you will visit your doctor and describe the symptoms. The doctor based
Read More...
3) Reduce expensive communication In agile development, instead of create team based on their disciplines, agile development promotes creating team based on the task they are going to handle. The team should consistent of teammate from different disciplines
Read More...
I read "Managing Agile projects" by Sanjiv Augustine recently. I found the book quite interesting and like to share what I think about agile development. 1) Don't give upper management any suprise Agile project will break down big project into smaller
Read More...
I came across a very funny blog written by Matt Warren about Agile development in Microsoft. http://blogs.msdn.com/mattwar/archive/2007/06/04/agile-at-microsoft.aspx I am not sure whether it is a fiction story or it is real story, but it is very funny
Read More...
