How to take the PMP Exam agile on June 25? Share your troubles

In order to help the examinees pass the exam smoothly , Caiju company was established by the former Huawei PMO The minister 、 Huawei's gold medal lecturer is the teaching and research team leader , The former Huawei team 、 Just get together with the lecturer group 、 We just got together 5A A teaching and research group composed of students , Create a series of customs clearance treasures for everyone , This series refers to ACP examination syllabus 、 Just gather the question bank 、PMI Authoritative information 、 And all previous 5A Students' experience summary , cover PMI-ACP a key 、 difficulty 、 Key test points .

Establish seven areas of knowledge panorama ：

field 1- Agile principles and concepts

field 2- Value oriented delivery

field 3- Stakeholder involvement

field 4- Team performance

field 5- Adaptive planning

field 6 Find problems and solve them

field 7 Continuous improvement

Selection of project cycle

◈ Predictive life cycle , Needs are clear , Technical determination , Simple projects

◈ Incremental lifecycle , Unclear needs , Technical determination , Brain burning project

◈ Iterative life cycle , Needs are clear , Technical ambiguity , Tough projects

◈ Agile Projects , The demand is still digging , Technology still needs to be explored , Chaotic project

◈ Don't touch the project , Unclear needs , The technical proposal is uncertain , Chaotic projects

Agile Manifesto

◈ Individuals and interactions are higher than processes and tools

◈ Working products are better than detailed documentation

◈ Customer cooperation is higher than contract negotiation

◈ Responding to changes is higher than following the plan

agile 12 Principle

1) Early and continuous delivery of valuable software

2) Welcome to change the requirements

3. Continuously deliver available software , The cycle varies from weeks to months , The shorter the cycle, the better

4) together , Daily collaboration between business people and developers

5. Be good at motivating project personnel , And believe that they can accomplish the task

6. Whether within or between teams , The most effective way to communicate is to talk face to face

7) Available software is the main indicator of progress

8. Agile processes promote sustainable development . Project side 、 Developers and users should be able to maintain a constant rate of progress

9. The continuous improvement of technology and design will improve the agility

10. Be concise , That is to minimize unnecessary work

11. The best architecture 、 Requirements and design come from self-organizing teams .

12. The team should regularly reflect on how to be more effective , And adjust the team's behavior accordingly .

Agile full view process

Scrum frame 3355

1. 3 A character

◈Development Team The team (DT）: Cross functional 、 Self management 、T Type talent , No subteams

◈ProductOwner Product owner (PO)： A person 、 The only Authorization , Identify product requirements and priorities , Responsible for ROI

◈Scrum Master(SM)： Four role coaches 、 Shepherd Dog 、 A pioneer in reform 、 guide

2. 3 Pieces

◈ Product backlog ： Dynamic list 、 The higher the priority, the more detailed 、 Focus on WHAT,PO Have

◈ Sprint to-do list ： The team promises and receives 、 That is to say WHAT Also have HOW、DT Have

◈ Potential deliverable increment : Accomplished PBI（Product Backlog ITEM） The sum of the , It is stable. 、 Working products ,PO and DT Jointly owned .

3. 5 Events

◈ sprint ： Usually 1~4 Zhou , The shorter the better 、 Once the sprint length is determined, it will not change 、 Previous Sprint After the end , New next Sprint And then it started immediately 、 Each sprint should have a goal

◈ Sprint planning meeting ： What do you do & How do you do it?

◈ Daily station will ： Individual broadcasts and commitments 、 Notification of delivery obstacles 、 Daily commitment status check

◈ Iteration review meeting ： Show the finished product 、 Business audit

◈ Iteration review meeting ： start 、 collecting data 、 Generate insights 、 Decide what to do 、 Close review

4. 5 A values

◈ promise – Willing to commit to goals

◈ focus – Apply your mind and ability to your promised work

◈ to open up – Scrum Open up everything in the project to everyone

◈ Respect – Everyone has his unique background and experience

◈ Courage – Have the courage to commit , Fulfill the promise , Dare to admit defeat

XP The core practice of extreme programming

1. Programming methods

◈ Simple design ：a. Simple design is easy to accept change requirements b. Only provide the functions that customers need

◈ Test-driven development （TDD）： Test cases are completed before development

◈ Pair programming ：a. Two programmers code together b. Pairing can be different in different iterations

◈ restructure ：a. Optimize the original code b. Minimize the risk of change

2. Group practice

◈ Code collective ownership ： Collective responsibility for all code , You can also modify the code of any part of the collective

◈ Coding standards ： Different teams may have different specifications , But the same team uses a uniform set of specifications

◈ Continuous integration ：a. Integration as soon as possible , Several times a day b. The team is constantly dealing with the latest changes , Conflicts are quickly discovered

◈ A steady, high-speed pace ： The team maintains sustainable growth throughout the project

◈ metaphor ：a. Use the real world paradigm b. Technical systems should avoid closed thinking

3. Deliver and manage

◈ The customer is at the scene ：a. Customers are responsible for writing user stories and defining acceptance criteria b. When problems arise , Make sure that customers are happy with

◈ Planning game ：a. Customers write stories , Developers make estimates , And commitment to known iterations .b. The goal is to maximize product value

◈ Small releases ：a. Focus on the smallest available features ,b. Fast delivery .c. Reduce complexity , Each version has high commercial value ,d. Let customers have more participation

◈ A complete team ： All participants （ Development 、 Customer 、 Testers ） Working together in an open space

Lean Lean 7 Core concepts

1) Eliminate waste ： What does not bring value to customers is a waste

2) Strengthen the learning ： Through a short iteration cycle 、 restructure 、 Integration testing and frequent customer feedback meetings enhance learning

3) Postpone a decision ： Too early to get enough information , Decisions are too late to take on higher cost risks , So postpone the decision appropriately to find the best balance .

4) Deliver as soon as possible ： Short iterations or small batches provide valuable feedback opportunities , Promote effective decision making .

5) Delegate to the team : Respect for people , Allow team members flexibility , Attract and retain high-quality employees .

6) Build quality : Not at the end “ test ” quality , Instead, quality is continuously ensured throughout the development process , For example, refactoring 、 Continuous integration 、 Unit test, etc .

7) See the whole picture ： Long term vision , Feet on the ground , Fast failure , Fast learning

The values of practice methodology

Private letters are free pmp Reference materials .