Traditional Culture Encyclopedia - Traditional stories - Difference between Agile Project Management and Traditional Project Management

Difference between Agile Project Management and Traditional Project Management

1. different management styles are applicable to different types of projects, for the unknown, unknowable or continuous change of the project, more applicable;

2. traditional management styles like the planned economy, more like the market economy, the ability to adapt to change is different;

3. traditional management styles are like the flight of the airplane must be closely planned in advance from the starting point to the destination, the flight altitude and speed are strictly defined, if the situation changes, such as turbulence, the pilot must be allowed to change the flight altitude. Flight altitude and speed are strictly regulated, if the situation changes, such as air turbulence, the pilot must be authorized to change the flight altitude. As if driving to Shanghai, I can choose any route I need at the appropriate time of my choosing, adjusting the route or strategy independently according to changes in the situation encountered, in the car, I am an independent individual, in the framework of the rules of the game of driving, in accordance with their own best interests in decision-making; the more complex the system, the greater the likelihood of the collapse of the centralized control and scheduling system, which is the reason for the decentralization of companies and the government's reduction of control efforts. This is why corporations decentralize and governments reduce regulation. This is why companies are decentralized and governments are less regulated. There is a long history of decentralizing control to the individual when dealing with complex problems;

4. The feedback loop between users and developers, between desired goals and implementation status, and between investment and return on investment has been greatly shortened. The complexity of the situation once again have an impact on the simple system, with which follow-up is not difficult, but in the face of the ever-changing market economy and evolving technology, the need to learn and improve in a shorter discovery cycle, Scrum's simple, continuous integration, continuous delivery, value first, embracing the principle of change is well adapted to the reality;

5. Favorable to the problem solving of the brainstorming. The heavy involvement of front-line personnel facilitates the full use of their experiences, perspectives, and concerns;

6. transforming small teams into managers of their own destinies, with teams accepting challenges, finding ways to meet them, exercising creativity, and avoiding obstacles to their work, all of which can't be pre-arranged by a centralized control and scheduling system;

.