Answer

1. Satisfy the customer through early and continuous delivery of valuable software.
   
2. Welcome changing requirements, even late in development.
   
3. Deliver working software frequently (shorter time scale)
4. Business people and developers must work together
   
5. Build projects around motivated individuals.
   
6. Use face-to-face conversation to convey information to and within a development team
   
7. Working software is the primary measure of progress.
   
8. Agile process promote sustainable development
   
9. The sponsors, developers, and users should be able to maintain a constant pace indefinitely
   
10. Continuous attention to technical excellence and good design enhances agility
    
11. Simplicity—the art of maximizing the amount of work not done—is essential
    
12. The best architectures, requirements, and designs emerge from self-organizing teams
    
13. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
    

Answer
UP project organizes the work and iterations across four major phases:

Inception—approximate vision, business case, scope, vague estimates.

Elaboration—refined vision, iterative implementation of the core architecture, resolution of high risks, identification of most requirements and scope, more realistic estimates.

Construction—iterative implementation of the remaining lower risk and easier elements, and preparation for deployment.

Transition—beta tests, deployment.

Answer

• Tackle high-risk and high-value issues in early iterations
  
• Continuously engage users for evaluation, feedback, and requirements
  
• Build a cohesive, core architecture in early iterations
  
• Continuously verify quality; test early, often, and realistically
  
• Apply use cases where appropriate•Do some visual modeling (with the UML)
  
• Carefully manage requirements
  
• Practice change request and configuration management
  

Answer

• Less project failure, better productivity, and lower defect rates. Shown by research into iterative and evolutionary methods
  
• Early rather than late mitigation of high risks (technical, requirements, objectives, usability, and so forth)
  
• Early visible progress
  
• Early feedback, user engagement, and adaptation, leading to a refined system that more closely meets the real needs of the stakeholders
  
• Managed complexity, the team is not overwhelmed by “analysis paralysis” or very long and complex steps
  
• The learning within an iteration can be methodically used to improve the development process itself, iteration by iteration
  

Answer

Risk-Driven;

Identify and drive down the highest risks. Early iterations focus on building, testing, and stabilizing the core architecture. For example risk of technology failure etc

Client-Driven;

Build visible features that the client cares most about. Client's interest is first priority.

Answer

• Individuals and interactions

– over processes and tools

• Working software

– over comprehensive documentation

• Customer collaboration

– over contract negotiation

• Responding to change

– over following a plan

Answer
Accepting change in requirement is one of the principle of Agile UP. We collect the changed requirement then plan and implement that changes in next Iteration of development process.