Agile Methodology :
like we know form our last lessons of project life cycles ,there are water fall and Agile methods ,
the difference between water fall and Agile :
the water fall : it's a project life cycle which the scope , time and cost are determines in the early phase of life cycle .
Agile :
a project life cycle that's iterative and incremental environmental which works well in project environments with high levels of change and ongoing stakeholders .
so we can present the Agile Project management : is a project management methodology that use iterative and incremental approach which focusing on customer value and team empowerment .
let's know the Agile manifesto values :
- individual and interactions over process and tools
- work software over comprehensive documentation
- customer collaboration over contract negotiation
- Responding to change over following a plan
The 12 Agile Principles :
- satisfy customer : be high priority is to satisfy the customer through early and continuous deliver of valuable software .
- welcome change : requirements , even late in development for the customers competitive advantage .
- Deliver Frequently : Deliver working software frequently , from a couple of weeks to a couple of months , with preference to the shorter timescale .
- Work together : Business people must work together daily throughout the project .
- Trust and support : Build projects around motivated individuals , give them the environment and support the need , and trust them to get the job done .
- face to face conversation : the most efficient and effective method of conveying information to and within a development team is face to face conversation .
- working software : delivering working software is primary measure of progress .
- sustaining development : agile process promote sustainable development , the sponsors developers and user should be able to maintain constant pace .
- continuous attention : to technical excellence and good design enhances agility .
- maintain simply : simplicity is essential (Barely sufficient) .
- self organization team : the best architectures , requirements and design emerge from self organization team .
- Reflect and trust :at regular intervals , the team reflects on how to become more effective , then tunes and adjust its behavior according .
0 Comments