Wondershare EdrawMind
EdrawMindPMP-15 Life Cycle Options
MindMap Gallery PMP-15 Life Cycle Options
- 15
PMP-15 Life Cycle Options
This mind map, Based on the mind map of Xisai PMP, Expand. This chapter is: PMP-15 Life Cycle Options 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-05-12 17:42:04- 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-15 Life Cycle Options
- 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-15 Life Cycle Options
stacey diagram
According to the degree of certainty of needs and technology, divide areas and choose appropriate management methods.
agility triangle
value, quality, constraints
project life cycle
1. concept
Refers to the series of stages a project goes through from initiation to completion
2. effect
It provides a basic framework for project management
Development life cycle
1. concept
There are usually one or more phases within the project life cycle related to the development of products, services, or results. These phases are called the development life cycle.
2. four types
Predictive, iterative, incremental, adaptive or agile
Four life cycle types
Predictive
1. Requirements determined
2. Scope determination
3. Low delivery frequency
Iterative
1. Demand dynamics
2. Uncertain scope
3. Low delivery frequency
Incremental
1. Requirements iteration fixed
2. Overall dynamics
3. High delivery frequency
Similar to going to a hotel to eat, the process of serving food is delivered one by one.
Agile
1. Demand dynamics
2. Uncertain scope
3. High delivery frequency
In agile projects, incremental delivery uncovers hidden or misunderstood requirements
Comparison of four life cycles
Characteristics of the Four Life Cycles
Predictive
1. fixed
2. administrative costs
3. The entire project is only executed once
4. one delivery
Iterative
1. correctness of solution
2. dynamic
3. Repeat until corrected
4. one delivery
Incremental
1. speed
2. dynamic
3. Execute once for given increment
4. Frequent smaller deliveries
Agile
1. Achieve customer value through frequent small-scale delivery and feedback
2. dynamic
3. Repeat until corrected
4. Frequent small-scale deliveries
Agile suitability filter
culture
1.Support
Does the senior sponsor understand and support the use of agile methods on the project?
2.Trust
Consider the attitude of sponsors and business representatives working with the team
Stakeholders are confident that with ongoing support and feedback from both parties, the team can transform its vision and needs into a successful product or service
3.Decision making
Whether the team can autonomously make local strategies for how to implement the work
team
1.Team size
Core team size
3-9
2.Experience level
Assess the experience and skill levels of core team roles
3. Degree of customer/business contact
Does the team have access to at least one business/account rep every day to ask questions and get feedback
project
1.Possibility of change
What is the likelihood that requirements will change and new requirements will be discovered each month?
2. Criticality of product or service
To help determine additional validation levels and document stringency requirements
3. Incremental delivery
Can products and services be built and evaluated at scale?
Are business and customer representatives able to provide timely feedback on the increments being delivered?
summary
hybrid life cycle
1. Both predictive and agile, or in a transitional phase, you can adopt a hybrid life cycle
2. Based on the degree of change and frequency of delivery, judge prediction and agility, who is the master and who is the auxiliary
3. four types
Be agile first, predict later
first, last
Predictive and agile combined
combine
Predictive method is the main method, agile method is supplemented
main, auxiliary
Agile methods are the main method, and predictive methods are supplemented.
main, auxiliary
4. Purpose
Accelerate return on investment
1. Design a hybrid lifecycle based on project risks
2. Incremental approaches focus resources so project results are completed sooner
Create business value
1. The goal of project management is to create business value in the best way possible, given the current circumstances.
2. “What can we do to succeed?”
spying risk
To manage risk when exploring ideas, an iterative or agile approach can be helpful
Deliver intermediate value
Agile methods may not be very useful when the organization is unable to deliver intermediate value
Get feedback quickly
1. Agile delivers frequently to customers and brings feedback to the team
2. Use feedback to re-plan the next part of the work
5. Hybrid Agile Methods
team approach
1. Scrum
A single team process framework for managing product development
2. Extreme Programming (XP)
Is a software development method based on frequent delivery cycles
3. Kanban method
Kanban in lean manufacturing is a system for planning inventory control and replenishment
Ensures continuity of workflow and value delivery
4. Scrumban
Scrumban is an agile method originally designed as a transition method between Scrum and Kanban
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
5. Function-Driven Development (FDD)
Developed to meet the specific needs of large-scale software development projects
6. Dynamic Systems Development Method (DSDM)
is an agile project delivery framework
Known for emphasizing constraints to drive delivery
The framework sets cost, quality, time, and Then use formal scope prioritization to meet the requirements of these constraints
7. Agile Unified Process (Agile UP) (AgileUP)
Is a branch of the Unified Process (UP) in software projects
extension method
1. crystal method
Crystal is a family of methodologies
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
2. 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
3. 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, One of the teams 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
4. Scaled Agile Framework (SAFe®)
Provides a knowledge base for all levels of the enterprise to carry out large-scale development work
5. Agile Development at Scale (LeSS)
It is a framework for organizing multiple development teams with the common goal of extending the Scrum method.
6. Disciplined Agile (DA)
It is a process decision-making framework that integrates multiple agile best practices in a comprehensive model.
DA aims to balance popular approaches that are too narrowly focused (like Scrum) or too detailed (like AgileUP)
7. Enterprise Scrum
Is a framework designed to apply the Scrum methodology through a more holistic organizational layer rather than a single product development layer
The aim is to extend agile methods beyond project execution by enabling disruptive innovation
6. Project factors affecting tailoring and tailoring plans
demand pattern
Stable or occasional hair
1. Many teams find that using cadences (in the form of periodic timeboxes) helps them demonstrate, review, and understand new tasks
2. Some teams need more flexibility as they take on more tasks
3. Teams can use flow-based agile methods to leverage cadence to achieve the best of both worlds
The rate of process improvement required by the team’s experience level
Review more frequently and select improvements
Workflow is often interrupted by various delays or obstacles
1. Consider using Kanban panels to make work visible
2. Experiment with constraints on different areas of the work process to improve workflow
Poor quality of product increment
Consider leveraging various test-driven development practices
This error-proofing mechanism makes it difficult to hide defects
Creating a product requires more than one team
Scale from one agile team to several agile teams with only minor disruption
1. First, understand Agile Program Management or Formal Scaling Framework
2. Second, craft an approach that fits the project context
Project team members lack experience using agile methods
1. Consider starting with training team members, agile thinking modules, and the fundamentals of agile principles
2. If the team decides to use a specific method, such as Scrum, Kanban, seminars will be held on the above methods so that team members can learn how to use them
Cutting plan table for improved fit