1. Agile Methods

2. Agile Process/Method lightweight processes/methods that can be used to manage and control software and product development using iterative, incremental practices. The main concept is to improve software processes. The focus on Engineering Practices Examples: –XP –Scrum –Crystal Methodologies 2 PIMSSO Project – Software Engineering Research Group

3. Evolutionary Map of Agile Methods

4. Agile Principles The main principles of Agile Process Development are and as summarized from (Beck et al., 2001): The main priority is to satisfy the customer needs through incremental delivery approach. Requirements change is managed and control. Delivering build by build (i.e. portion if the final product) to the customer, the work period of each individual build ranging from a couple of weeks to a couple of months. The project stakeholders must work together on daily basis throughout the project. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.

5. Agile Principles The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. Working software is the primarily measure of process. Sustainable pace is one core values of agile processes. Sponsors, developers and users are responsible to maintain a constant pace. Continuous focus in technical excellence and prober design enhances agility. Simplicity--the art of maximizing the amount of work not done--is essential. The best architectures, requirements, and designs emerge from self-organizing teams. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

6. Agile Processes: Core Values Also other such as (Boehm, 2002) mention that agile processes core values are: individuals and interactions over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, responding to change over following a plan.

7. Agile Processes: a Review Premium people(Boehm, 2002) Critical systems--leery(Boehm, 2002) Agile methods or processes claiming high quality products as results of their use and with excessive cost. Agile methods or processes claiming simplicity and speed.

8. References 1.BECK, K., et al. (2001). Manifesto for Agile Software Development [Online]. Available: http://www.agilemanifesto.org/principles.html [Accessed April 26 2011]. 2.BOEHM, B. (2002). Get Ready for Agile Methods, with Care. IEEE Computer, 64 - 69. 3.NAWROCKI, J. R., WALTER, B. & WOJCIECHOWSKI, A. (2002(. Comparison of CMM Level 2 and eXtreme Programming. The 7th European Conference on Software Quality. Helsinki, Finland: Springer-Verlag Berlin Heidelberg. 4.SEDDON, J. (2000). The Case Against ISO 9000, Dublin, Oak Tree Press. 5.VRIENS, C. (2003). Certifying for CMM Level 2 and ISO9001 with XP@Scrum. Agile Development Conference (ADC). Salt Lake City, UT, USA: IEEE Computer Society. 6.ABRAHAMSSON, P., et al. (2003). New Directions on Agile Methods: A Comparative Analysis. 25th International Conference in Software Engineering (ICSE'03) Portland, Oregon - USA.