Thursday, 20 November 2008
 
 
Knowledge Blog
Welcome, Guest
Please Login or Register.    Lost Password?
Knowledge Blog Research & Development
Development Topics (1 viewing) (1) Guests
Post a new message in "Development Topics"
Name:
Email*:
Subject:
topic icon:
no
Boardcode:
 Colour:  Size:   Close all tags
Message:

Emoticons
B) :( :) :laugh:
:cheer: ;) :P :angry:
:unsure: :ohmy: :huh: :dry:
:lol: :silly: :blink: :blush:
:kiss: :woohoo: :side: :S
More Smilies
 Enter code here   
* - your email address will never be displayed on the site.

Topic History of: Agile Methodologies
Max. showing the last posts - (Last post first)
Author Message
Allie Gentry During the mid 1990’s, many software developers and business users rebelled against the negative aspects of traditional waterfall methodologies and decided to come up with a better way.

In many cases, the waterfall method would deliver a product, but it would take many months and sometimes, many years before any change was released. Not only was there a lengthy timeline, the often-mistaken assumption was that all facts and information was known during the planning session of the process.

Let’s look at why waterfall methodologies did not always address business user’s needs, especially in the business intelligence realm.



Read attached document for more information.
File Attachment:
File Name: SwiftKnowledge___Agile_Methodologies.pdf
File Size: 148372
Powered by FireBoardget the latest posts directly to your desktop
 
Copyright ©1999 -2008 , SwiftKnowledge™. All rights reserved.              Site Map