PROCESSES IN KNOWLEDGE AREAS
INTEGRATION MANAGEMENT
COST MANAGEMENT
RISK MANAGEMENT
Develop project charter
Plan cost management
Plan risk management
Develop project management plan
Estimate costs
Identify risks
Direct and manage project work
Determine budget
Perform qualitative risk analysis
Manage project knowledge
Control costs
Perform quantitative risk analysis
Monitor and control project work
Plan risk response
Perform integrated change control
QUALITY MANAGEMENT
Implement risk response
Close project or phase
Plan quality management
Monitor risks
Manage quality
SCOPE MANAGEMENT
Control quality
Plan scope management
PROCUREMENT MANAGEMENT
Plan procurement management
Collect requirements
RESOURCE MANAGEMENT
Conduct procurements
Define scope
Plan resource management
Control procurements
Create WBS
Estimate activity resources
Validate scope
Acquire resources
STAKEHOLDER MANAGEMENT
Control scope
Develop team
Identify stakeholders
Manage team
Plan stakeholder engagement
Control resources
Manage stakeholder engagement
SCHEDULE MANAGEMENT
Plan schedule management
Monitor stakeholder engagement
Define activities
COMMUNICATIONS MANAGEMENT
Sequence activities
Plan communications management
Estimate activity durations
Manage communication
Develop schedule
Monitor communication
Control schedule
PROJECT CHARTER CONTAINS
GROUP CREATIVITY TECHNIQUES
TAILORING COST MANAGEMENT
Project Title and description
Brainstorming, Nominal group technique
Knowledge management – Organization has
Stakeholders
Idea/mind mapping, Affinity diagram
formal knowledge management
Business case
Multi-criteria decision analysis
Estimating and budgeting
Project constraints and assumptions
Affinity diagram
Earned value management
Sponsor for the project
Questionnaire and surveys
Use of agile approach
Stakeholder influence/authority level
Governance
Product description
CONSIDERATIONS FOR TAILORING
Budget for the project
Resource availability – considering the relation
TAILORING QUALITY MANAGEMENT
PM & their roles, authority etc.
between resource availability and
Policy compliance and auditing
Project Risks
productivity
Continuous improvement
Project justification
Life cycle approach – finding out the correct life
Stakeholder engagement
cycle approach for a detailed schedule
Standards and regulatory compliance
WBS DICTIONARY CONTAINS
Project dimensions - considering aspects of
Unique identifier (code of account identifier)
project like complexity, technological uncertainty TAILORING RESOURCE MANAGEMENT
Assumptions and constraints
etc. for the impact of the project
Diversity
Acceptance criteria
Technology Support - Technology used to
Physical location
Schedule, cost estimates
develop, record, transmit, receive, store the
Acquisition of team members
Description about the work to be done
project schedule is accessible
Management of team
The team responsible to do the work
Industry specific resources
Quality requirements
Life cycle approaches
PROCESSES IN AGILE
DOMAIN 1 - VALUE-DRIVEN DELIVERY
DOMAIN 2 - STAKEHOLDER ENGAGEMENT
DOMAIN 3 - BOOSTING TEAM
Maximizing business value through prioritization, Understanding stakeholder needs, getting
PERFORMANCE PRACTICES
iterative delivery, and risk management.
stakeholders involved, and keeping them
Forming teams, empowering them, building team
Prioritize based on value
informed.
commitment, and promoting collaboration.
Perform retrospectives and adaption
Get the right stakeholders
Create team norms collectively
Define acceptance criteria
Continuously engage the stakeholders
Build cross-functional teams
Create situationally specific processes
Cement stakeholder involvement
Promote generalizing specialists
Chunk work to maximize value and gain feedback Actively manage stakeholder interest
Spread agile values, principles, and terms
Reduce risks early
Frequently discuss what "done” looks like
Promote self-organization
Deliver incrementally and get feedback
Show progress and capabilities
Create a safe team environment
Examine value and early termination
Candidly discuss estimates and projections
Research team and personal motivators
Reduce cost of changes
Promote team consensus-making
Proactively reduce risk
Reduce communication costs
Keep stakeholders informed of dependencies
Shield the team from outside interruptions
Do demos and get feedback
Create a uniting vision
Consider value and risk in prioritization
Work with the team to track velocity
Actively reprioritize
Consider nonfunctional requirements
DOMAIN 4 - ADAPTIVE PLANNING
DOMAIN 6-CONTINUOUS IMPROVEMENT
MANIFESTO FOR AGILE SOFTWARE
Estimating, creating different levels of plans,
(PRODUCT, PROCESSES, PEOPLE)
DEVELOPMENT
getting feedback on progress, and
Improve various aspects of the project-including
Individuals and interactions over processes and
updating plans.
its product, processes and people-via
tools
Plan at multiple levels
retrospectives and experiments.
Working software over comprehensive
Involve team & customer to engage them in
Tailor the process to the project
documentation
planning
Improve based on retrospectives
Customer collaboration over contract negotiation
Manage expectations via actual results
Make team adjustments
Responding to change over following a plan
Tailor the process to project characteristics
Eliminate waste
Update the plan based on project priorities
Communicate lessons learned
Ensure encompassing estimates
Work in pairs to spread knowledge and skills
Test out improvement suggestion
DOMAIN 5 - PROBLEM DETECTION AND
RESOLUTION
Encouraging whole-team tracking and resolution
of risks.
Promote open team communications
Manage risks and problem, as a team
Factor in impediments
Track risks visually
Communicate risks
TWELVE GUIDING PRINCIPLES FOR AGILE METHODS
1. Our highest priority is to satisfy the customer through, early and
continuous delivery of valuable software.
2. Welcome changing requirements, even late in development. Agile
processes harness change for the customer's competitive
advantage.
3. Deliver working software frequently from a couple of weeks to a
couple of months, with a preference to the shorter timescale.
4. Business people and developers must work together daily
throughout the project.
5. Build projects around motivated individuals. Give them the
environment and support they need and trust them to get the job
done.
6. The most efficient and effective method of conveying information
to and within a development team is face-to-face conversation.
7. Working software is the primary measure of progress.
8. Agile processes promote sustainable development. The sponsors,
developers, and users should be able to maintain a constant pace
indefinitely.
9. Continuous attention to technical excellence and good design
enhances agility.
10. Simplicity-the art of maximizing the amount of work not done-is
essential.
11. The best architectures, requirements, and designs emerge from
self-organizing teams.
12. At regular intervals, the team reflects on how to become more
effective, then tunes and adjusts its behavior accordingly.