You complete one phase before moving on to the next phase
Your rarely aim to re-visit a 'phase' one it's completed
Your better get whatever you're doing right the first time
Issues
You don't realize any value until the end of the project
You leave the testing until the end
You don't seek approval from the stakeholders until late in the day
These approaches are highly risky, often more costly and generally less efficient than Agile approaches
Agile approache
Agile, what is that ?
Not a process, it's a philosophy or set of values
The Core Beliefs of Agile (1/2)
You cannot know everything required to build a software product at the start of project
Customers cannot accurately tell you what they want at the start of the project; instead, they will gain clarity as the project proceeds
You want feedback from the customer as often as possible and you want to give developers feedback on how they are doing as soon as possible
Working code is the most accurate way of seeing the progress of the development effort
The Core Beliefs of Agile (2/2)
Groups working together minimizes delays as well as the loss of information between people
Moving test to the front of the development cycle improves the conversation between developers and customers and testers and, thus, improves, the quality of the code
While management can set expectations for what work is done, management must not demande how that work is done
Working on one project at a time improves the productivity of a team
Agile manifesto
Individuals and interactions over processes and tools