Read: 2424 times    -     Avarage Rate: 5

2010 07 Jun

In traditional projects, and the old life cycle management methodologies, the requirements changes were so hard, and the teams try to resist it as possible. So the detailed requirement catching was the first goals of project. So to minimize the changes in the requirement team shall include whatever they can imagine in their analysis and have to see the and predict the coming path for the software in order to minimize the final cost.
Read: 2117 times    -     Avarage Rate: 4

2010 18 May

The decisions within an agile development project must be the responsibility of all team members, especially the Active users, from here come the importance of the active user involvement. The project team must be empowered to make decisions in order to ensure that it is their responsibility to deliver the product and that they have complete ownership. Any interference with the project team is disruptive and reduces their motivation to deliver.
Read: 2484 times    -     Avarage Rate: 0

2010 17 May

In all development projects, the sales describe the requirements to the client who will understand them in his own way while the development team will understand these requirements in a third way.
Read: 3911 times    -     Avarage Rate: 3.5

2010 17 May

Understanding Success The traditional definition of success is the delivery on time, on budget, and according to specification. [Standish] Agile Methodology When developing software, there are two basic approaches to planning: waterfall and agile. In the waterfall model, the project is planned, Scheduled, Built, Tested, and then Deployed, the larger the project, the more problematic the waterfall metho