Agile process

Agile project management is aimed at traditional project management. Since any project process requires project management, the project management in the process of agile software development is agile project management. The three priorities of agile project management are customers, products and people. Create value for customers, produce adaptable products and let talented people collaborate with each other.

The core values ​​of agile project management are similar to those of agile software development, as follows:
1. People and interactions are better than processes and tools.
2. Commit to the product rather than compile comprehensive documentation.
3. Collaboration with customers is better than contract negotiation.
4. Adapting to change is better than following steps.
 
Software to create customer value is our core goal of creating software products, and the current situation is indeed that our product development principles are more based on step-by-step basis and administrative management rather than excellent technology. Project management should be a leader that inspires and focuses on delivering maximum value to clients, not a simple day-to-day management activity. Agile project management is a combination of values ​​-> principles -> practices, which should be the steps that any methodology should follow.
 
Agile Management Guiding Principles:
 
Agile project management process - reading notes (1)

The guiding principles of agile project management revolve around its core values. Among them, there are three guiding principles for teams and people; three principles for products and customers, which fully demonstrate the importance of people and teams in agile project management. The principles and patterns adopted in agile project management are practical to solve practical problems in our software development process. The specific correspondence is as follows:
 
Unstable customer demand, incomplete demand mining - iteration, prototype, communication feedback, architecture scalability Tight
schedule requirements - iteration, lightweight documentation, communication efficiency, reusable technology
Poor product adaptability - team, self-adaptive, excellent technology, encouragement explore
 
Some practitioners assume that the project management process is the same and can be applied to any project. They believe that people with good project management skills do not need deep technical expertise. While this may be true in some areas, it is generally not applicable to product development where technical, scientific or engineering skills are important. Project managers who don't understand the technology they manage can lose confidence in their teams, especially those that pride themselves on their technical abilities.
                                              
Project managers must support technical excellence, which is the key to adaptability and low-cost iterations, both of which are drivers of long-term product success. A project manager may not be a technical authority, but he had better have an assistant of a technical authority, so as to find a balance among various key elements such as project progress, quality, technology, and function. The core competence of a project manager is reflected in the balance and coordination of these key elements of the project.
 
There are risks and uncertainties at any time during the project process. And these are often the key to the success of the project. In most projects there is too much management and too little leadership. The fundamental difference between management and leadership is that management deals with process complexity, while leadership deals with change. The project manager is both a manager and a leader, and the importance of the latter will increase rapidly as the project exploration system increases. Excellent leadership is an important factor in the success of a project.
 
Adaptive and self-organizing teams do not refer to leadershipless teams, but simply a leadership style.
 
Project managers need to spend time on project communication and collaboration. Need to communicate, coordinate, discuss, confirm and then prepare appropriate documentation. The goal of information transfer is to understand rather than document, and it is difficult for a team with a lot of documents to achieve agility.
The five stages of agile project management:
 
Agile project management process - reading notes (1)

Guess you like

Origin http://10.200.1.11:23101/article/api/json?id=327106628&siteId=291194637