First 5 Agile Myhts- BUSTED

First 5 Agile Myhts- BUSTED

Agile has no Process, doesn’t have Documentation, doesn’t believe in Contracts, doesn’t follow a Plan These four common agile myths most likely come straight from a misunderstanding of the Manifesto’s value propositions. In order to fully understand the value propositions, you have to take all three parts into account, not just the middle section. “That is, while there is value in the items on the right, we value the items on the left more.” Nowhere does the Manifesto say “Stop writing documentation” or “Ban all contracts”. There is indeed value in following a process, writing documentation, and having a plan. And contracts are absolutely necessary when dealing with external parties. However, they should not become the focus of the software project, nor should they prevent the users, customers, and development team from collaborating. Agile Projects don’t provide Budget Estimates When projects are scope-boxed (as they are in traditional development methodologies like waterfall), given a list of requirements, and estimates for those requirements, the budget and schedule are derived completely from the estimates

View post:


First 5 Agile Myhts- BUSTED

     


<script type="text/javascript"><!– google_ad_client = "ca-pub-8334046383696150"; /* PMChat Header */ google_ad_slot = "8203916761"; //–> </script> <script type="text/javascript" src="http://pagead2.googlesyndication.com/pagead/show_ads.js"> </script>

Comments are closed.