1 / 15

AGILE SOFTWARE DEVELOPMENT

AGILE SOFTWARE DEVELOPMENT. BINA BARAL(2008-BCT-510) SAJANA SHAKYA(2008-BCT-530) SUNITA MAHARJAN(2008-BCT-545). Software Development. Deals with development of software: Systematic development Cost effective Software developed for variety of purposes: Custom software

tomasso-davock
Download Presentation

AGILE SOFTWARE DEVELOPMENT

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. AGILE SOFTWARE DEVELOPMENT BINA BARAL(2008-BCT-510) SAJANA SHAKYA(2008-BCT-530) SUNITA MAHARJAN(2008-BCT-545)

  2. Software Development • Deals with development of software: • Systematic development • Cost effective • Software developed for variety of purposes: • Custom software • Commercial and open source software • Embedded software

  3. The Four Phases of software Development Requirements Analysis Architecture and Design Development Test and Feedback

  4. Methods of Software Development • Broadly divided into two categories: adaptive and predictive. • Predictive: • Old methodologies based on predictive method • exactly what features and tasks are planned for the entire length of the development process. • focus on planning the future in detail. • Have difficulty changing direction. • Change control Board, to ensure that only the most valuable changes are considered

  5. Adaptive: Adapting quickly to changing realities. When the needs of a project change, an adaptive team changes as well. Date is, the more vague, difficulty describing exactly what will happen in the future. An adaptive team may only be able to report the mission statement for the release, or a statement of expected value vs. cost. Agile an Adaptive method of s/w development.

  6. What is Agile? • Agile software development is a group of software development methodologies • Self organizing, cross-functional teams. • Iterative and incremental development.

  7. HISTORY • Agile method derived from the concept of lightweight software development. • In mid 1990’s as a reaction against heavy weight development. • Early implementations of lightweight methods include scrum(1995), crystal clear, Extreme programming (1996), Adaptive software development, Feature Driven Development, and Dynamic Systems (1995).

  8. The agile alliance, a non profit organization that promotes the software development. The better ways of developing software and helping others to do it: Individuals and interactions over process and tools. Working software over comprehensive documentation. Customer collaboration over contract negotiation. Responding to change over following a plan.

  9. CHARACTERISTICS There are many specific agile development Methods. Promoting development Team work Collaboration Process adaptability Break tasks into small increments with minimal planning. Iterations are short time frames (timeboxes). Each iteration involves a team working through a full software development cycle. minimizes overall risk and allows the project to adapt to changes quickly.

  10. Agile teams work in a single open office (called a bullpen). Team size is typically small (5-9 people) to simplify team communication and team collaboration. maintain daily contact through videoconferencing, e-mail, etc… each agile team will contain customer representative. act on stake holders behalf and makes a personal commitment. to answer mid-iteration problem-domain questions.

  11. Software development life cycle

  12. Use a routine and formal daily face-to-face communication among team members. In a brief session, team members report to each other what they did the previous day, what they intend to do today, and what their roadblocks are. emphasizes working software as the primary measure of progress. At the end of each iteration, stakeholders and the customer representative review progress and re-evaluate priorities.

  13. Measuring agility Agility Index Measurements (AIM): score projects against a number of agility factors to achieve a total. Agility Measurement Index: scores developments against five dimensions of a software project (duration, risk, novelty, effort, and interaction). Other techniques are based on measurable goals

  14. Why Agile Software Development? Customer satisfaction by rapid delivery of useful software. Welcome changing requirements, even late in development. Working software is delivered frequently. Working software is the principal measure of progress. Sustainable development, able to maintain a constant pace. Close, daily co-operation between business people and developers. Face-to-face conversation is best form of communication. Projects are built around motivated individuals. Continuous attention to technical excellence and good design. Simplicity Self organizing teams. Regular adaptation to changing circumstances.

More Related