1. Our highest goal is to meet customer requirements through early and continuous delivery of valuable software
1. To verify user needs, Agile often uses prototyping to quickly produce a product model to verify customer needs and collect customer feedback.
The prototyping method is a method of using product development tools to quickly build a product model based on the preliminary needs of relevant parties and display it to relevant parties.
Generally used to collect requirements
2. A minimum viable product is a product or model that is usable and can even be brought to market. It is something that can be released and is generally not used to validate customer needs.
MVP is the minimum viable product
MVP refers to the fastest and most concise way to build a product or demonstration that is usable and can be brought to the market to meet the core needs of users and obtain feedback.
It is generally used for delivery as soon as possible, such as making a product that can be launched into the market first.
Main points
Deliver as early as possible
2. Changes to requirements are welcome, even in the late stages of project development.
Agile processes must be good at taking advantage of changes in requirements to help customers gain competitive advantages.
Main points
1. Traditional project management influences and controls factors that lead to change
2. Agile anticipates changes in requirements
3. Embrace changes, even if they occur late in the project
4. Ensure software is flexible enough through principles, patterns, and practices
5. Responding and adapting quickly to changes can give customers a significant competitive advantage in responding to new opportunities.
3. Deliver usable software frequently, with cycles ranging from weeks to months, and the shorter the better.
Main points
1. Software that delivers work frequently, the shorter the time interval, the better
3. XP iteration cycle
It will be as short as one week
4. Shorter iteration cycles
Strengthen the team's continuous focus on customer value
4. During project implementation, business personnel and developers must always collaborate
Main points
1. In traditional projects, people responsible for business value and software developers work strictly separately.
2. Allow each team to focus on what they do best
3. Agile project management encourages them to work together in the same place
4. Team members and business people can understand each other’s ideas
5. their common goal
Deliver value to customers through working software
5. Be good at motivating project personnel, give them the environment and support they need, and believe that they can complete the tasks
focus on
Provide environment and support
Main points
1. Motivating people, people are more important than having the best processes and tools
2. Build strong teams and actively avoid micromanagement
3. Self-disciplined teams rather than a top-down mandate
4. Provide the team with an environment free from outside interference,
Remove barriers to product creation
5. Give the team room to play freely
6. Whether it is to the development team or within the team, the most effective way to convey information is face-to-face conversation
focus on
Face to face communication
Main points
1. Informal verbal communication is far more common in agile project management than formal written communication
2. Communication in agile projects is open and any team member can freely participate in the conversation
3. Communication is transparent, timely and visual
4. The most efficient communication
face to face conversation
5. penetrating communication
6. wide bandwidth communication
7. Available software is the primary measure of progress
Main points
1. traditional projects
Constant updates make documentation a burden
2. real value
is expressed through results, and the results are expressed through the software that works
3. Working software is the primary metric
4. Pay attention to the degree of completion of requirements
5. Pay attention to the usability of the software
8. Agile processes promote sustainable development
Project sponsors, developers, and users should all be able to maintain a steady pace at all times
Main points
1. Agile projects are more work intensive than traditional projects
Especially when using methods like XP
2. Maintain a stable and sustainable pace of progress so that team members do not rush to work at the end of the iteration cycle, causing problems
3. Do not allow excessive stress and fatigue
4. Not borrowing tomorrow’s energy to get more done today
9. Continuous improvement of technology and continuous improvement of design will improve agility
Main points
1. The better the design, the easier the maintenance
2. Keep your software clean and tidy
3. Write high-quality code
5. Stable and high-quality projects allow teams to respond to changes more quickly than inferior projects.
10. Simplicity, that is, minimizing unnecessary work as much as possible, is an art
Main points
1. The key point is to stay focused on customer value and not hesitate to cut activities that don’t add value
2. This principle is embraced by all agile methods, especially lean methods
3. One of the core aspects of Lean methodology is the elimination of waste
4. Keeping it simple is the most basic principle
5. Don’t build flashy systems
11. The best architecture, requirements and designs will emerge from self-organizing teams
Main points
1. A self-organizing team is one in which the team talks among itself about how work will be distributed and who will do a particular job
2. Tasks are assigned to the remediation team, not to an individual
3. Agile Team: Generalizing Specialist
4. The team is empowered, self-organized, self-managed, and the team makes decisions
5. The most significant difference between traditional projects and agile projects
6. Not only are small teams self-organizing, but larger cross-functional teams can also be self-organizing
7. Not only does one person have responsibility for architecture, requirements, and testing, but the entire team shares these responsibilities
12. The team should regularly reflect on how to be more effective and adjust the team’s behavior accordingly
Main points
1. In traditional projects, when the project or phase is completed, it is the most common practice to hold a meeting to summarize
2. agile
Review more frequently to get the job done
3. Daily scrum, iteration retrospective meeting
4. In an iteration retrospective meeting, review the work or releases that were completed during the previous iteration and evaluate how they can be improved next time
5. Daily stand-up meetings are another important way to coordinate team efforts, team self-evaluation and self-adjustment
Wondershare EdrawMind
