14 Questions
What is a key characteristic of agile development methods?
Incremental development with small releases
Which of the following is NOT a principle of agile methods?
Following prescriptive processes
What is the typical duration between new releases of a system in agile development?
Two to three weeks
Which agile method is probably the best-known?
Extreme Programming (XP)
What is the role of customers in agile development?
To provide and prioritize system requirements
What is the purpose of incremental delivery in agile development?
To deliver functional software in small chunks
What is the focus of agile development in terms of complexity?
To maintain simplicity
What is typically part of the contract between the customer and the supplier?
The software requirements document
What is the main challenge in writing contracts for agile development?
Specifying a set of requirements
What is the primary purpose of formal documentation in system development?
To make it easier for people changing the system to understand
Why do agile methods enthusiasts argue that formal documentation is a waste of time?
Because it is often not kept up to date
What is the key to implementing maintainable software according to agile practices?
Producing high-quality, readable code
What is the primary document required for system maintenance?
System requirements document
What is the likely outcome of using agile methods without creating a coherent requirements document?
System maintenance becomes more difficult and expensive
Study Notes
Agile Methods
- Agile methods are incremental development methods that involve customers in the development process to get rapid feedback on changing requirements.
- New releases of the system are created and made available to customers every two or three weeks.
- Agile methods minimize documentation by using informal communications rather than formal meetings with written documents.
Principles of Agile Methods
- Customer involvement: customers should be closely involved throughout the development process to provide and prioritize new system requirements and evaluate the iterations of the system.
- Incremental delivery: the software is developed in increments with the customer specifying the requirements to be included in each increment.
- People not process: the skills of the development team should be recognized and exploited, and team members should be left to develop their own ways of working without prescriptive processes.
- Embrace change: expect the system requirements to change and design the system to accommodate these changes.
- Maintain simplicity: focus on simplicity in both the software being developed and in the development process, and actively work to eliminate complexity from the system.
Contracts and Documentation
- Writing contracts for agile development may be difficult due to incremental specification.
- Agile methods rely on contracts in which the customer pays for the time required for system development rather than the development of a specific set of requirements.
- Formal documentation is often not kept up to date and does not accurately reflect the program code.
- Agile methods emphasize the importance of writing well-structured code and investing effort in code improvement.
System Maintenance
- The lack of documentation should not be a problem in maintaining systems developed using an agile approach.
- The system requirements document is the key document for system maintenance, but many agile methods do not create a coherent requirements document.
- The use of agile methods is likely to make subsequent system maintenance more difficult and expensive.
This quiz covers the basics of agile methods in system development, including their needs, benefits, and processes. It also touches on customer involvement and minimal documentation in agile development.
Make Your Own Quizzes and Flashcards
Convert your notes into interactive study material.
Get started for free
