Career Forums

 
  Modern Analyst Forums  Business and Sy...  General  when to (not) use agile
Previous Previous
 
Next Next
New Post 12/30/2008 11:30 AM
User is offline Sara Criss
9 posts
10th Level Poster


Re: when to (not) use agile 

thanks for ur help ....it is really useful info .....once again thanks a lot .......

 
New Post 1/9/2009 2:45 AM
User is offline Craig Brown
560 posts
www.betterprojects.net
4th Level Poster




License to hack 
Modified By Craig Brown  on 1/9/2009 5:52:01 AM)

 ajmarkos wrote
Hi: To me it sounds like agile is being defined as "a license to hack". Isn't agile in essence creating minimual documentation - but still producing essential documentation? Isn't such the goal of EVERY project? Granted, the required level of documentation may vary for example for junior developers vs senior level developers, but, for the given environment, I thought the goal is still minimal - but essential - documentation. Tony

Tony, where do you get this impression that agile is a licence to hack. 

I do believe your interpretation on agile documentation is correct, but don't think documentation is a core issue.  It's more about the iterative development and incremental requirements discovery.

 
New Post 1/12/2009 7:08 PM
User is offline Leslie
2 posts
www.umllmu.com
No Ranking


Other reasons not to go agile 
  • When the team is geographically separated - can't have access to all the information you need when you need it, so need to plan up front how to get it.
  • If the project is safety critical - can't risk making a mistake, because somebody could be injured.

Les.

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  General  when to (not) use agile

 






 

Copyright 2006-2025 by Modern Analyst Media LLC