Home > Agile > Quizzes > Agile Development
Agile Development
Fast practice, instant feedback. Timer auto-submits when time’s up.
Avg score: 17% Most missed: “Welcome changing requirements - even late in development”
Agile Development
Time left 00:00
25 Questions

1. Simplicity- The art of maximizing the amount of work not done - is essential

2. Most agile implementations use a routine and formal daily face-to-face communication among team members. This specifically includes the customer representative and any interested stakeholders as observers. In a brief session - team members report to

3. In contrast - focus on planning the future in detail. A predictive team can report exactly what features and tasks are planned for the entire length of the development process. Predictive teams have difficulty changing direction. The plan is typicall

4. Specific tools and techniques - such as continuous integration - automated or xUnit test - pair programming - test-driven development - design patterns - domain-driven design - code refactoring and other techniques are often used to improve quality a

5. A set of six management principles initially intended for project managers of Agile Software Development projects. [2005]

6. Dxpect uncertainty and manage for it through iterations - anticipation and adaptation.

7. Face-to-face conversation is the best form of communication (co-location)

8. Behaviour Driven Development where the scenarios are written before the code and form part of an automated suite of tests that can verify whether the code meets the required functionality and/or quality standards.

9. Requirements cannot be fully collected at the beginning of the software development cycle - therefore continuous customer or stakeholder involvement is very important.

10. Large-scale development efforts (>20 developers) - though scaling strategies and evidence of some large projects have been described.

11. Agile methods break tasks into small increments with minimal planning and do not directly involve long-term planning.

12. No matter what development disciplines are required - each agile team will contain a customer representative. This person is appointed by stakeholders to act on their behalf and makes a personal commitment to being available for developers to answer

13. An adaptive team will have difficulty describing exactly what will happen in the future. The further away a date is - the more vague an adaptive method will be about what will happen on that date. An adaptive team cannot report exactly what tasks the

14. Working software is delivered frequently (weeks rather than months).

15. Increase return on investment by making continuous flow of value our focus.

16. Welcome changing requirements - even late in development

17. In agile development - self-organization and motivation are important - as are interactions like co-location and pair programming.

18. Unleash creativity and innovation by recognizing that individuals are the ultimate source of value and creating an environment where they can make a difference.

19. Individuals and interactions over processes and tools

20. Distributed development efforts (non-colocated teams). Strategies have been described in Bridging the Distance[40] and Using an Agile Software Process with Offshore Development

21. Close - daily co-operation between business people and developers

22. Some methodologies focus on development practises (XP) - others focus on the management of the software project (SCRUM).

23. Projects are built around motivated individuals - who should be trusted

24. These meetings - sometimes referred as daily stand-ups or daily scrum meetings - are held in at the same place and same time every day and should last no more than 15 minutes. Standing up usually enforces that rule.

25. One of the differences between agile and traditional testing methods - such as the waterfall model of software design - is that testing of the software is conducted at different points during the software development lifecycle.