List of requisites which are needed for the successful enactment of the analyzed method fragments:

Major Requisite Minor Requisite
Adaptations be quickStart and complete feature within iteration
Be able to express every idea
Be able to say everything once
Be EffectiveBetter design, velocity and correctness
Company does not overly influence the customer
Customer does not overly influence the company
Minimize customer/company cultural conflict
Be EfficientImprove speed of unit tests
Increase number of automatic tests
Reduced Formality
Code be maintainableReduce entropy
Update code in the face of evolving needs
Collaboration be GoodAvoid under-utilization of customer
Collaboration be Viable
Culture of Team Work
Customer Collaboration be Explicit
Customer collaborates effectively
Equal engagement of both programmers
Equal participation of all group members
High sense of product ownership
Increased participation
Increased participation
Joint Decision Making
Minimize technological gap between customer and developers
Overcoming barriers in groups (increase productivity)
Simillar Working and Resting Hours
customer be beneficial to the teamCustomer be available when needed
Customer can handle multiple tasks and roles
customer be competent
customer be credible
customer be knowledgeable (about domain needs, priorities)
customer have managerial support
features be jointly decided by team and customer
Data be GatheredActual outcomes be compared to projected outcomes
All stakeholders be encouraged to contribute
Decision-Making be ImprovedAll stakeholders be encouraged to contribute
Client input be increased
Decisions be based on data and insights
Defect be DiscoveredAcceptance tests be clear
Testable code be written
Testing be done at every iteration
User stories be described and prioritized
Defect be Resolved QuicklyAll defects be resolved at every iteration
Designer's understanding of code be increased
Development be constant and incrementalImprove code readability and reusability
Reorganize and simplify legacy code
Elicitation be EffectiveActive user involvement
Effective communication skills
Extract unanticipated information
Faster elicitation process
Have some structure
Integration of different viewpoints
Less ambiguity
Requirements be codeable
Environment be SupportiveDevelopers be encouraged to add unit tests to their code
Development environment provides rapid response to changes
TDD be practiced from the beginning of the project
Expertise be accessibleDevelop and practice standards
Encourage learning
Facilitate knowledge transfer
Take advantage of consultants
Have no superfluous partsDo not anticipate future enhancements
Meet current requirements only
Individuals be motivated to be empowered and show full potentialImproved sense of belonging
Improved sense of competence
Improved sense of progress
Improved sense of safety
Insights be GeneratedProblems be identified
Iteration be plannedIteration only include features that can be completed within iteration
Objectives and task list be set
Timebox be set
Iteration Plan be RealisticBalanced requirements prioritization
Requirements be prioritized properly
Task be broken down properly
Task estimates be accurate
Maintenance be Up-To-DatePass release tests often
Meeting be EffectiveConcrete, tangible goal
Everyone committed to attend meetings
High quality of collaboration
High quality of communication
Real-time information passing
Skilled Leadership
Trust and mutual respect
Optimal Learning Be AchievedPartner changes be frequent
Quality DesignComponents be highly cohesive and loosely coupled
Design / Code be extensible
Self-MotivationPractice be Encouraged (not Enforced)
Stories (requirements) be well-defined Features Support Requirements
Story be business-oriented
Story be estimatable
Story be short and implementable during one iteration
Story be testable
Team ExperienceTask estimates be accurate
Team Leadership Rather Than ManagementSuperiority of knowledge rather than bestowed authority
Waste Items be Properly SeenDefects be detected
Extra features be eliminated
Extra processes be eliminated
Motion be minimized
Partially done work be identified
Task-switching be reduced
Waiting times be reduced