List of requisites which are needed for the successful enactment of the analyzed method fragments:
| Major Requisite | Minor Requisite |
|---|---|
| Adaptations be quick | Start and complete feature within iteration |
| Be able to express every idea | |
| Be able to say everything once | |
| Be Effective | Better design, velocity and correctness |
| Company does not overly influence the customer | |
| Customer does not overly influence the company | |
| Minimize customer/company cultural conflict | |
| Be Efficient | Improve speed of unit tests |
| Increase number of automatic tests | |
| Reduced Formality | |
| Code be maintainable | Reduce entropy |
| Update code in the face of evolving needs | |
| Collaboration be Good | Avoid 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 team | Customer 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 Gathered | Actual outcomes be compared to projected outcomes |
| All stakeholders be encouraged to contribute | |
| Decision-Making be Improved | All stakeholders be encouraged to contribute |
| Client input be increased | |
| Decisions be based on data and insights | |
| Defect be Discovered | Acceptance tests be clear |
| Testable code be written | |
| Testing be done at every iteration | |
| User stories be described and prioritized | |
| Defect be Resolved Quickly | All defects be resolved at every iteration |
| Designer's understanding of code be increased | |
| Development be constant and incremental | Improve code readability and reusability |
| Reorganize and simplify legacy code | |
| Elicitation be Effective | Active 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 Supportive | Developers 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 accessible | Develop and practice standards |
| Encourage learning | |
| Facilitate knowledge transfer | |
| Take advantage of consultants | |
| Have no superfluous parts | Do not anticipate future enhancements |
| Meet current requirements only | |
| Individuals be motivated to be empowered and show full potential | Improved sense of belonging |
| Improved sense of competence | |
| Improved sense of progress | |
| Improved sense of safety | |
| Insights be Generated | Problems be identified |
| Iteration be planned | Iteration only include features that can be completed within iteration |
| Objectives and task list be set | |
| Timebox be set | |
| Iteration Plan be Realistic | Balanced requirements prioritization |
| Requirements be prioritized properly | |
| Task be broken down properly | |
| Task estimates be accurate | |
| Maintenance be Up-To-Date | Pass release tests often |
| Meeting be Effective | Concrete, 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 Achieved | Partner changes be frequent |
| Quality Design | Components be highly cohesive and loosely coupled |
| Design / Code be extensible | |
| Self-Motivation | Practice 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 Experience | Task estimates be accurate |
| Team Leadership Rather Than Management | Superiority of knowledge rather than bestowed authority |
| Waste Items be Properly Seen | Defects 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 |
