AGILE SOFTWARE
DEVELOPMENT
Lecture 3
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Guidelines and tips
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Agile Software Development: Adapting to Rapid Change, Slides of Software Engineering
Agile software development is an iterative and incremental approach that emphasizes delivering working software to meet evolving requirements. It focuses on effective communication, customer involvement, and self-organizing teams. Agile methods are suitable for small to medium-sized business systems and custom development within organizations. The agile model includes concept/iteration, warm-up, construction, release, production, and retirement phases. Agile development is compared to plan-driven approaches, considering technical, human, and organizational factors that influence the choice between these methodologies. The document also presents an assignment on aligning agile practices with the challenges of outsourced projects, highlighting the importance of adapting agile principles to distributed software development.
Typology: Slides
2022/2023
1 / 19
This page cannot be seen from the preview
Don't miss anything!
Related documents
Partial preview of the text
Download Agile Software Development: Adapting to Rapid Change and more Slides Software Engineering in PDF only on Docsity!
AGILE SOFTWARE
DEVELOPMENT
Lecture 3
Recap
■ Software Development Life Cycle Models
— Waterfall Model
— V Model
— Spiral Model
— Incremental Models
Agile software development
■ Agile software development is a group of software development methodologies based on iterative and incremental development, where requirements and solutions evolve through collaboration between self-organizing, cross-functional teams.
What is “Agility”?
- Effective (rapid and adaptive) response to change
- Effective communication among all stakeholders
- Drawing the customer onto the team
- Organizing a team so that it is in control of the work performed
Yielding …
- Rapid, incremental delivery of software
5
Agile method applicability
■ Agile methods are probably best suited to small/medium-sized business systems.
■ Custom system development within an organization, where there is a clear commitment from the customer to become involved in the development process and where there are not a lot of external rules and regulations that affect the software.
Agile Model
Agile Model Phases (Cont…)
■ Warm Up
■ The first week or the initial working time of an agile project is referred to as “Iteration 0” (or “Cycle 0”) or in the “Warm Up” iteration stage. This is basically the project initiation stage of the model. The main goal during this period is to basically initiate the project by : Gathering initial support and funding for the project. Actively working with clients and developers to initially model the scope of the system. Begin building the team Setting up the environment for the project development
Agile Model Phases (Cont…)
■ Construction
— In the construction phase we start to shape the concept or product requirements and furnish a working system as per the client's requirements along with the testing of the developed concept.
■ Release
— This phase deals with the certain release iterations of the project. This phase includes: Final testing of the system. Finalization of any system and user documentation Training Deploy the system
Plan-driven and agile development
Plan-driven development
- 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
- you must plan and schedule all of the process activities before starting work on them.
- Not necessarily waterfall model – plan-driven, incremental development is possible
Agile development
- Specification, design, implementation and testing are inter-leaved and the outputs from the development process are decided through a process of negotiation during the software development process.
Plan-driven and agile development
Technical, human, organizational
issues
▪ What is the expected system lifetime? — Long-lifetime systems may require more design & documentation to communicate the original intentions of the system developers to the support team. Use Plan-driven development for such systems. ▪ How good are the designers and programmers in the development team? — It is sometimes argued that agile methods require higher skill levels than plan-based approaches in which programmers simply translate a detailed design into code.
Technical, human, organizational issues
▪ Is the system subject to external regulation? — If a system has to be approved by an external regulator (e.g. the FAA approve software that is critical to the operation of an aircraft) then you will probably be required to produce detailed documentation as part of the system safety case. Use plan-driven development.
How to write a Term Paper?
■ Choose your topic. ...
■ Do your research. ...
■ Refine your thesis statement. ...
■ Develop an outline for the paper. ...
■ Make your point in the introduction. ...
■ Convince the reader with your body paragraphs. ...
■ Conclude with strength…
■ Show some style (Citation etc),,,