Comments on: A Closer Look at Agile Software Development http://softwarecritics.info/software/agile-software-development/?utm_source=rss&utm_medium=rss&utm_campaign=agile-software-development Blog about software reviews, computer tips and tricks, technology news, web applications, and social media. Sat, 12 May 2012 04:00:05 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: Mathdelane http://softwarecritics.info/software/agile-software-development/comment-page-1/#comment-1046 Mathdelane Fri, 22 Jan 2010 14:34:20 +0000 http://softwarecritics.info/?p=2395#comment-1046 Based on my understanding, agile software development doesn't need much manpower because the open communication within an agile team is extraordinary thus there's not even a hierarchical distinction between people e. g., who's the leader and who's the member. Anybody could coordinate with anyone regardless of ranks thus an open channel makes it dynamic thereby completing a project is less time. Based on my understanding, agile software development doesn’t need much manpower because the open communication within an agile team is extraordinary thus there’s not even a hierarchical distinction between people e. g., who’s the leader and who’s the member. Anybody could coordinate with anyone regardless of ranks thus an open channel makes it dynamic thereby completing a project is less time.

]]> By: James Moralde http://softwarecritics.info/software/agile-software-development/comment-page-1/#comment-1041 James Moralde Fri, 22 Jan 2010 07:32:38 +0000 http://softwarecritics.info/?p=2395#comment-1041 Sounds like one sophisticated approach to app development. My immediate hunch is that while it may allow for rapid development (in a week's time), it probably involves a lot of manpower than the traditional sequential method. But it must essentially be not just a quicker method but also a more efficient one. After all, the agile development methodologies were supposed to be 'developed in response to the weaknesses of the waterfall model'. During my programming days, I never got to work in a real full team project. Thus, I did not get the opportunity to be possibly exposed to these methods of rapid application development. .-= James Moralde´s last blog ..<a href="http://moralde.com/google-search-engine-ranking-pattern/" rel="nofollow">Google Search Engine Ranking Pattern</a> =-. Sounds like one sophisticated approach to app development. My immediate hunch is that while it may allow for rapid development (in a week’s time), it probably involves a lot of manpower than the traditional sequential method. But it must essentially be not just a quicker method but also a more efficient one. After all, the agile development methodologies were supposed to be ‘developed in response to the weaknesses of the waterfall model’.

During my programming days, I never got to work in a real full team project. Thus, I did not get the opportunity to be possibly exposed to these methods of rapid application development.
.-= James Moralde´s last blog ..Google Search Engine Ranking Pattern =-.

]]>