Agile jargon-filled or not?

Does Agile reflect the current project management customer needs? Or is it just another jargon-filled smokescreen to market the project management professionals?

Absolutely, and not only for the customer needs but also for the project team's needs. The primary motivation for agile comes from the difficulties in meeting deadlines, lack of integration between employees and the team, product requirements different from the original order, which are common problems in the waterfall methodology. Agile is here to fill this lack of challenges. For that, 12 principles were created:

1. Value - The main goal is not to deliver a final product as per requirements, but to deliver value to the customer. In other words, deliver a solution that brings the best results.
2. Flexibility - In an increasingly competitive and complex market, it is necessary to develop projects in a flexible way, so that they can undergo changes according to the context in which the company operates and its needs, which may change during development.
3. Frequency - In each sprint completed, the time of the project must integrate functionality to the customer, with a total capacity to be used from the first moment.
4. Union - The implementation of corporate governance is fundamental for projects to be agreed upon as per customer expectations. This collaboration is what will allow you to customize the solution and validate it when each sprint is completed.
5. Motivation - It is fundamental that the project team is motivated to develop its own paper and has an appropriate atmosphere to develop their activities.
6. Communication: Sprint planning meetings are basic, simple. Finally, the register of activities is not effective when a meeting of the project team to set goals, exchange cohorts and plan as close actions.
7. Functionality - The evolution of a project that develops according to aggressive methods is estimated by the delivery of the functional product and not by the conclusion of activities. -?Functionality is the result of the union between value, flexibility and frequency.
8. Sustainability - Build something with the right resources, which will increase and multiply them for future uses.
9. Revision - A constant revision of the technical requirements, as well as the design standards, allows the delivery of a solution that is actually aligned with the customer's negotiation objectives, dispensing large amounts at the time of final entry.
10. Simplicity - Less is more: As aggressive methods dispense with both records and other documents that compromise team pace, the work can be more simple to execute. Sending, bringing, concluding at my own pace. Assim guarantees customer time to market.
11. Organization - Agile teams are composted by professionals with the ability to organize by themselves. That is, to divide the responsibilities between them, without the interference of a project manager.
12. Self-Assessment - Review of the work performed that, at the end of each sprint, allows the team to assess its performance and discover more interesting ways to work and streamline the entire process.

Check the 12 principles of Agile on: https://www.agilealliance.org/agile101/the-agile-manifesto/