Have no doubts about the approach to software development

Pros;Cons

The client is constantly involved in the development process; A risk of project disruption if the client's manager changes their mind The project team is ready to change the client's requirements; To ensure that the quality of the project does not suffer due to ongoing adjustments, the project manager always needs to allocate additional time for implementation A new release (the next stage) in no way affects the previous one; The final project cost cannot be correctly estimated The project can be constantly improved; The total cost of agile approach implementation is somewhat more expensive but the result is satisfactory for the client Reduces the risk of failure, the process is entirely based on incremental progress; Constant modifications can demotivate the project team, the project manager needs to think about motivation

Pros;Cons

The team knows the project timeline well; There is a high probability of project vulnerabilities being discovered The client does not participate in the project process but only accepts the final work; There are no intermediate project results, you can test only once the work is completed The team follows a determined project structure; At project launch, account may not be taken of changes in external factors that might have an impact Work may be planned immediately for the long term; If the initial requirements are unclear, the project will be less effective The team knows precisely what it has to do, the deadline and final budget; What the client expects from the final project might not quite comply with what was agreed at the beginning