The goal of the agile project management approach is not to build a large, "complete" product over a "long" project, but to gradually create a "small" product with minimal functionality in a very short iteration, and then add more and more functionality in each subsequent iteration of the project management. The main characteristic of this type of approach is that each stage adds value, right from the start of the project, thanks to user and/or customer feedback , so that the overall scope of the project is constantly evolving. In fact, this continuous evolution and improvement can have the perverse effect of the project "never ending".
It is important to note that, although the origin of this type of methodologies (or best practices in reality) stands out in software development , where it has achieved the best results, this is not the only area where it can be applied. Among the agile proposals, the best known are Scrum , which is fundamentally an agile teamwork framework for project management, and Kanban , which, in essence, is an agile way of managing work , putting the emphasis on "just in time" delivery .
As an essential reference work for a project turkey phone data manager, the Project Management Body of Knowledge (PMBoK) stands out , edited by the Project Management Institute (PMI), the largest international organization focused on project management (more than 600,000 members in nearly 170 countries). The PMBoK is the only standard recognized by the American National Standards Institute (ANSI) and is aligned with the ISO 21500 and ISO 9001 standards .
The guide contains an overview of the fundamentals of project management that are recognised as good practices and are constantly updated. Currently, the sixth edition is in force, where reference is made to agile, iterative and adaptive environments, describing how these practices are integrated into a project setup.
If you've chosen the agile model, you should check out Scrum , written by Jeff Sutherland , one of its creators. The book, according to the author, "is designed to tell the why of Scrum" and, in the final appendix, explains how to do it and where to start.