Please enable JavaScript.

Coggle requires JavaScript to display documents.

SWE102 - 3 - AGILE SOFTWARE DEVELOPMENT (Agile methods (Principles (focus…

- - - - A plan-driven approach to software engineering is based around separate development stages with the outputs to be produced at each of these stages planned in advance.
      - Not necessarily waterfall model – plan-driven, incremental development is possible
      - Iteration occurs within activities
    - - Specification, design, implementation and testing are interleaved and the outputs from the development process are decided through a process of negotiation during the software development process.
- - - - Increments are delivered to customers every 2 weeks;
      - All tests must be run for every build and the build is only accepted if tests run successfully.
      - New versions may be built several times per day;
  - - - All previous and new tests are run automatically when
        new functionality is added
      - Tests are written as programs rather than data so that
        they can be executed automatically.
      - Writing tests before code
    - - is part of the team writes tests as
        development proceeds
      - customer role have limited
        time available
      - help develop acceptance tests
    - - tests are written as
        executable components before the task is implemented
      - there is always a set of tests
        that can be quickly and easily executed
- - - - The starting point for planning is the product backlog, which is the list of work to be done on the project. During the assessment phase of the sprint, this is reviewed, and priorities and risks are assigned. The customer is closely involved in this process and can introduce new requirements or tasks at the beginning of each sprint.
      - The selection phase involves all of the project team who work with the customer to select the features and functionality to be developed during the sprint.
      - Once these are agreed, the team organizes themselves to develop the software. Short daily meetings involving all team members are held to review progress and if necessary, reprioritize work. During this stage the team is isolated from the customer and the organization, with all communications channelled through the so-called ‘Scrum master’. The role of the Scrum master is to protect the development team from external distractions. The way in which the work is done depends on the problem and the team. Unlike XP, Scrum does not make specific suggestions on how to write requirements, test-first development, etc. However, these XP practices can be used if the team thinks they are appropriate.
      - At the end of the sprint, the work done is reviewed and presented to stakeholders. The next sprint cycle then begins.
      - Sprints are fixed length, normally 2–4 weeks. They correspond to the development of a release of the system in XP.