Wondershare EdrawMind
EdrawMindPMP agile knowledge points review
MindMap Gallery PMP agile knowledge points review
- 20
PMP agile knowledge points review
PMP agile knowledge points are summarized. The content includes three parts: agile, waterfall, iterative and incremental development methods, agile basics and agile practices. Learn together.
Edited at 2023-03-06 18:32:33- bacteria
This is a mind map about bacteria, and its main contents include: overview, morphology, types, structure, reproduction, distribution, application, and expansion. The summary is comprehensive and meticulous, suitable as review materials.
- Plant asexual reproduction
This is a mind map about plant asexual reproduction, and its main contents include: concept, spore reproduction, vegetative reproduction, tissue culture, and buds. The summary is comprehensive and meticulous, suitable as review materials.
- Reproductive development of animals
This is a mind map about the reproductive development of animals, and its main contents include: insects, frogs, birds, sexual reproduction, and asexual reproduction. The summary is comprehensive and meticulous, suitable as review materials.
PMP agile knowledge points review
- bacteria
This is a mind map about bacteria, and its main contents include: overview, morphology, types, structure, reproduction, distribution, application, and expansion. The summary is comprehensive and meticulous, suitable as review materials.
- Plant asexual reproduction
This is a mind map about plant asexual reproduction, and its main contents include: concept, spore reproduction, vegetative reproduction, tissue culture, and buds. The summary is comprehensive and meticulous, suitable as review materials.
- Reproductive development of animals
This is a mind map about the reproductive development of animals, and its main contents include: insects, frogs, birds, sexual reproduction, and asexual reproduction. The summary is comprehensive and meticulous, suitable as review materials.
- Recommended to you
- Outline
No relevant template
agile
development method
agile
Agile is about user value
Fall
Waterfall is for management costs
Iterate
Iteration is about doing things accurately and well
Increment
Increment is to do things quickly and deliver them quickly in stages
Agile basics
4 core values
1) Individuals and interactions are higher than processes and tools
Agile requires more to stimulate individuals' subjective initiative rather than restricting individuals with a large number of process tools.
2) Working software takes precedence over detailed documentation
Try to produce results that are valuable to customers
3) Customer cooperation is higher than contract negotiation
Win-win cooperation rather than disputes
4) Responding to change over following a plan
embrace change
12 principles
1) Continuously deliver valuable software to satisfy customers as early as possible
2) Be good at taking advantage of changes in requirements
Don't resist change
3) Short cycle, fast delivery and fast iteration (the shorter the better)
4) War room, business and development must work together
5) Inspire & Believe
6) Face to face
7) Available software is the primary measure of progress
8) Sustainable development (not faster is better, encourage stable output)
9) Lean thinking, continuous improvement of technology and continuous improvement of design
10) Be concise and reduce unnecessary work as much as possible
11) Self-organizing team
12) Reflect regularly & make corresponding adjustments
Agile practices
SCRUM-3355 Framework
SCRUM Framework Overview
The scope of the plan does not change in an iteration (agile is not about embracing change without a bottom line)
Iteration planning → Daily stand-up meeting (daily planning) → Next iteration requirements sorting (demand sorting meeting)
Potentially releasable product increments generated by iterations
Iteration review meeting and iteration demonstration meeting (customer review)
iteration review meeting
"3355"
3 roles
PO
product owner
Customer Representative (Party A’s Representative)
Define all product features
Decide on product release content and dates
Responsible for product input and output ROI
Prioritize features that need development based on market changes
Reasonably adjust product functions and iteration sequence
Agree or reject the iteration’s delivery
SM
Agile coach
Play the role of a coach (auxiliary role, improve skills, eliminate interference)
Lead the team to complete the practice of SCRUM and embody its value
Troubleshoot team difficulties
Ensure the team is competent at their job and maintains high productivity
Enable the team to work closely together and enable team members to have the ability to work in multiple functions
Protect the team from unwarranted external influences
DT
development team
Number of people: Classic team has 5-9 people
Team members are all-rounders
Team members all work full-time
Team self-organization and management
Team relationships should be fixed within an iteration, and individual relationships can only be adjusted at the beginning of a new iteration.
3 types of artifacts
product
Iterate
product increment
5 rituals
Product review meeting
Sorting and sorting requirements
Pre-meeting for iteration planning meeting
iteration planning meeting plan
1) Select user stories and determine iteration goals (po & team members)
2) Split tasks (tasks)
Daily stand-up meeting do
Attributes
1) Open every day
2) Time should be controlled within 15 minutes
3) Driving while standing
Not to solve the problem (to expose the problem)
1) All relevant parties can be invited
2) Only SM, PO, and DT can speak
Avoid irrelevant discussions
Review meeting check
Product specific
1) The team needs to demonstrate the iteration completed
2) The typical approach is to use demonstrations to show the implementation of new functions or underlying architecture
3) informal
1) 2 hours of advance preparation
2) No formal presentation document required
4) The entire team needs to participate
5) Invite everyone who cares about the product to participate (everyone is welcome to participate)
open meeting
iteration review act
Targeted at the process
1) What worked well (and should continue to work)
2) What is bad (should be stopped)
3) What can be improved (reach a consensus on prioritized actions for improvement)
Internal meetings only require SM, PO, and DT to participate
Iterative PDCA
5 values
courage
fair
focus
promise
respect