Answer: Option (D)
12 Agility Principles:
-
Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
-
Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
-
Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
-
Business people and developers must work together daily throughout the project.
-
Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
-
The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
-
Working software is the primary measure of progress.
-
Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
-
Continuous attention to technical excellence and good design enhances
agility.
-
Simplicity—the art of maximizing the amount of work not done—is essential.
-
The best architectures, requirements, and designs emerge from self– organizing teams.
-
At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
So we can clearly see that option A, B, C all fall under agility principles. [ As for Option (B) "Recognition that change represents opportunity.", clearly agility principle welcomes change at any stage of software development and also it recognizes that these changes will enable its customer to have a competitive edge over the others]
As for Option (D), there is only one thing about testing in the Agile Development and that is
After stories are developed and preliminary design work is done, the team does not move to code, but rather develops a series of unit tests that will exercise each of the stories that is to be included in the current release (software increment).8 Once the unit test has been created, the developer is better able to focus on what must be implemented to pass the test.
So clearly the testing is done throughout the lifetime of the project and not just as a separate phase after building. So Option (D) does not fall within Agile Development.