Wondershare EdrawMind
EdrawMindPMP-18 Other Agile Practices
MindMap Gallery PMP-18 Other Agile Practices
- 32
- 1
PMP-18 Other Agile Practices
This mind map, Based on Xisai PMP mind map, expansion. The contents of this chapter are: PMP-18 Other Agile Practices At the same time, there are PMP test questions with relevant knowledge points. From knowledge points to corresponding test questions, It can deepen your understanding and memory of knowledge points!
Edited at 2023-06-01 17:38:54- 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-18 Other Agile Practices
- 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
PMP-18 Other agile practices
Hybrid Agile Methods
1. team approach
Scrum
A single team process framework for managing product development
Extreme Programming (XP)
Is a software development method based on frequent delivery cycles
Kanban method
Kanban in lean manufacturing is a system for planning inventory control and replenishment
Ensures continuity of workflow and value delivery
Scrumban
1. Scrumban is an agile method originally designed as a transition method between Scrum and Kanban
2. It is another hybrid agile framework and method that evolved by itself, where teams use Scrum as the framework and Kanban as the process improvement method
Function-Driven Development (FDD)
Developed to meet the specific needs of large-scale software development projects
Dynamic Systems Development Method (DSDM)
1. is an agile project delivery framework
2. Known for emphasizing constraints to drive delivery
3. The framework sets cost, quality, time from the outset and then leverages formal scope prioritization to meet these constraints
Agile Unified Process (Agile UP) (AgileUP)
Is a branch of the Unified Process (UP) in software projects
2. extension method
crystal method
1. Crystal is a family of methodologies
2. The Crystal Methodology is designed to quantify and provide options for methodological rigor based on project size (the number of people involved in the project), as well as the criticality of the project
Lean
1. Lean concept
focus on value
small batch
Eliminate waste
2. The relationship between Lean, Kanban and Agile
Think of Agile and Kanban methods as derivatives of Lean thinking
Lean thinking is a superset of
Agile is an umbrella term for many practices
commonality
Deliver value, respect people, reduce waste, be transparent, adapt to changes, and continue to improve
Scrum of Scrums (SoS)
Also known as "meta Scrum"
Is a technique used by two or more Scrum Teams rather than one large Scrum Team, where a team includes three to nine members to coordinate its work
Hold regular meetings
Usually two or three times a week
The model is similar to daily stand-up meeting
Scaled Agile Framework (SAFe®)
Provides a knowledge base for all levels of the enterprise to carry out large-scale development work
Agile Development at Scale (LeSS)
It is a framework for organizing multiple development teams with the common goal of extending the Scrum method.
Disciplined Agile (DA)
1. It is a process decision-making framework that integrates multiple agile best practices in a comprehensive model.
2. DA aims to balance popular approaches that are too narrowly focused (like Scrum) or too detailed (like AgileUP)
Enterprise Scrum
1. Is a framework designed to apply the Scrum methodology through a more holistic organizational layer rather than a single product development layer
2. The aim is to extend agile methods beyond project execution by enabling disruptive innovation
Lean
Lean concept
1. focus on value
2. small batch
3. Eliminate waste
The relationship between Lean, Kanban and Agile
1. Think of Agile and Kanban methods as derivatives of Lean thinking
2. Lean thinking is a superset of
3. Agile is an umbrella term for many practices
4. commonality
Deliver value, respect people, reduce waste, be transparent, adapt to changes, and continue to improve
1. Lean thinking
Spend the least amount of money to do the best thing, the core is to eliminate waste
2. A waste of 3M
unbalanced
overload
waste
3.Seven core concepts
Eliminate waste
Empower your team and respect your employees
Fast delivery, delivery as soon as possible
Comprehensive optimization, optimization of the whole
Quality first, focus on quality
Making decisions late, delaying commitments
Reinforce learning and encourage improvement
4. Seven Wastes of Lean Manufacturing
transportation
wait
action
defect
in stock
overproduction
over processing
5. Value stream map
identify
The flow of each process in a work item
find out
defects (waste) and develop improvement measures
turn up
Activities that do not provide added value to the product
Kanban
1. definition
Kanban, in lean manufacturing, is a system for planning inventory control and replenishment
Ohno Taiichi
toyota
The word "kanban" literally translates to "visual symbol" or "card"
Physical Kanban panels with cards enable and enable visualization of workflow within the rectification system for everyone to see
2. The defining principles of the Kanban method
Start from current state
Agree to adopt incremental evolutionary changes
Respect current processes, roles, responsibilities and titles
Encourage leadership behaviors at all levels
3. Core Properties of the Kanban Method
Workflow visualization
Limit work in progress
management process
Clarify process policies
Implement feedback loops
Improve collaboration
4. effect
Visualize work flow
Consensus Information and Risks
Designed specifically for knowledge-based work
Can ensure continuity of workflow and value delivery
5. Six core practices of Kanban (Task Board)
Visual workflow
Constrained work-in-progress (WIP)
Measure and manage activities (pull)
display rules
Create a feedback loop
Improve through collaboration and experimentation
task board
Task Board: Pull Production
pull system
Once the team completes an item, it can pull another item into the process
Task boards serve a dual purpose
Provides the development team with a convenient mechanism to organize work
It also allows the development team to see at a glance how much work is left.
Provide workflow, bottlenecks, blockers, and overall status information
Provide the latest information on the status of the team's work
6. Limit work in progress
Reasonable planning, team efficiency, and identifying bottlenecks
WIP
Work in process
Work in progress can be understood as a process
If there are too many processes, computers and mobile phones will easily become stuck, so you need to plan appropriately and limit WIP.
In the Kanban approach, completing work is more important than starting new work
1. No value can be gained from work that is never done
2. So the team will help implement and comply with WIP limits so that every job in the entire system can be "done"
7. information transmitter
burn down chart
1. Indicate the remaining workload
burn down chart
It is a graphical representation of the relationship between the remaining work and the remaining time in the time box. Use the burndown chart to view the progress of the project over time.
Comparison with other plans
iteration planning
Shows the work to be completed in this iteration
product roadmap
It is a desired state or certain characteristics at a certain point in time.
release plan
Mainly publish product vision and goals and formulate high-level requirements
2. Iterative burndown chart
3. Publish a burndown chart
Ignition chart
Indicate work completed and distance from goals
cumulative flow graph
1. Cumulative flow chart is the core measurement in the Kanban method, which can well reflect the flow of work items in each process link.
Holistic
2. What is shown in the cumulative flow diagram is
Lead time
Backlog size
Remaining to-do items
period time
Work in process quantity information
3. Through the cumulative flow diagram, we can see the process of analysis, development, testing and deployment.
Work in progress
Number of tasks completed
4. Therefore, creating a cumulative flow chart needs to be based on the WIP limit information executed on the Kanban board.
5. Cumulative flow graph
Completion statistics based on different modules of Kanban
Determine scope changes and trends for current projects
8. Scenarios where the Kanban method is most suitable
flexibility
Teams are generally not time-boxed and will execute the highest priority work on the backlog
Focus on continuous delivery
The team focuses on completing the entire system workflow and does not start new work until the WIP is completed
Improve work efficiency and quality
By limiting WIP, work efficiency and quality will be improved
Improve efficiency
Examine each subtask for value-added and non-value-added activities, then clear out non-value-added activities
Team member focus
Limit WIP so teams can focus on current work
Workload variability
If there is unpredictability in the upcoming work, the team will not be able to make predictable commitments, even for short-term work
reduce waste
Transparency will make waste visible and therefore eliminate it
Extreme Programming (XP)
1. definition
Is a software development method based on frequent delivery cycles
2. The limits of development, the limits of feedback loops
3. Extreme Programming (XP) Practice Areas
organize
1. main
Centralized office
the whole team
A well-informed workplace
2. secondary
real customer engagement
team continuity
sustainable rhythm
technology
1. main
pair programming
test first programming
incremental design
2. secondary
Shared code/collective ownership
Code and test documentation
Refactor
planning
1. main
user stories
weekly cycle
quarterly cycle
jet lag
2. secondary
Root Cause Analysis
tailoring team
Pay as you use
Negotiate Scope Contract
Daily stand-up meeting
Integrate
1. main
10 minutes to build
continuous integration
Test first
2. secondary
Single code base
incremental deployment
Daily deployment
4. advocated method
During the process, at least one customer representative
fast delivery
pair programming
1. Two developers
work together
one writes code
a real time review
2. Function
Be more focused and efficient
Break down team barriers
develop new skills
3. Semi-private space
Caves and common areas
4. Remote pairing with fish tank window
fish tank window
Create a fishbowl window by establishing long-term video conferencing links between the team’s various locations
At the beginning of each day's work, open the link; at the end of the day, close the link
remote pairing
Establish remote pairings by using virtual meeting tools to share screens, including voice and video links
They are all communication technologies and methods that may be used in distributed teams
For example: when a team member has insufficient skills, you can give the member enough trust through pair programming to help him or her grow.
Test Driven Development (TDD)
1. Test-Driven Development
2. Write test cases before development
3. Code while testing
4. If the test fails, it can be refactored
Code collectively owned
No overtime (no more than 40 hours per week)
open workspace
Adjust plans promptly
Refactor
Optimize and reorganize the code without changing the function to improve the maintainability of the code
5. continuous integration
Integrate immediately to quickly find code problems and solve them
6. automated test
Avoid frequent failures after delivery
Avoid increased costs of manual testing
7. Scrum and XP
XP corresponds to software engineering and technology
Scrum corresponding links and processes
Test Driven Development (TDD)
1. Write test cases before development
2. Test while coding
3. If the test fails, it can be refactored
Refactor
Optimize and reorganize the code without changing the function to improve the maintainability of the code