Home » Без рубрики
Category Archives: Без рубрики
CPMAI – A Methodology for AI projects development by PMI
PMI has released its AI project management methodology — Cognitive Project Management for AI
The first question is why?
Traditional project management and application development methodologies do not fully address the
complexity of AI projects. AI solutions are data-driven, not just software-driven, which requires a
systematic approach that ensures:
● Alignment with business objectives and ROI
● Proper data preparation and management
● Robust model evaluation and operationalization
● Iterative development to adapt to changing data and needs
CPMAI is data-centric and based on an iterative approach.
The methodology provides 7 patterns —
Conversational and human interaction
Recognition
Patterns and anomalies
Predictive analytics and decision support
Hyperpersonalization
Autonomous systems
Goal-driven systems
The methodology includes 6 main phases

Business understanding
Data understanding
Data preparation
Model development
Model assessment
Transfer to operational use
In the presented methodology, a separate section is devoted to the issues of trust in AI, and embedding trust in each phase of the project. (Note: For those interested in issues of trust and ethics in the development of AI systems, I refer to my presentations — 1 and 2)
Key roles in AI projects
Project Manager/AI Project Lead: oversees the entire AI initiative, ensuring its compliance with the CPMAI stages. Project Manager: Provides leadership support to the AI project, allocates resources, and helps align the AI initiative with the broader organizational strategy. This role coordinates timelines, manages risks, engages with stakeholders, and ensures the project aligns with business goals.
● Data Engineer: Creates the data pipelines and architecture that power the AI systems. They
perform tasks such as data ingestion, integration, cleansing, transformation, and ensure the reliability, scalability, and security of data flows, which is critical to smooth model development and deployment.
● Business Analyst/Subject Matter Expert: Ensures the AI solution aligns with real business goals and domain needs. They help define success criteria, interpret results, and translate AI insights into actionable actions for stakeholders and end users.
● MLOps/DevOps Engineer: Bridges the gap between model development and deployment to production by managing version control, continuous integration/continuous delivery, and ongoing performance monitoring.
● Data Scientist: If an ML model needs to be developed from scratch or requires fine-tuning to extend existing models, organizations may also need a data scientist on the team. This role focuses on building and validating models. The data scientist has expertise in statistics, machine learning algorithms, and model experimentation. They must translate business needs into technical requirements and make modeling decisions accordingly.
AI Soft Skills and Culture
● Critical Thinking and Problem Solving: AI projects are experimental by nature, so
teams must be able to conceptualize approaches, test solutions quickly, and iterate.
● Communication and Storytelling: Stakeholders need clear explanations of complex AI results, whether to justify resource allocation or solve user problems.
● Collaboration and cross-functionality: AI projects span data, engineering, and business domains. Strong teamwork and cross-functional alignment are essential.
● Adaptability and tolerance for uncertainty: As models evolve and data changes, teams must be prepared for iterative cycles and the ability to iterate.
SUMMARY
Use CPMAI’s iterative, data-driven, AI-specific approach
● CPMAI’s six stages: From understanding the business (stage I) to operationalizing the model (stage VI), each stage ensures that the right problems are being addressed, the right data is in place, the AI is being developed responsibly, and that real needs are being met.
● Iterative, data-driven approach: AI projects are not static. They require iterative cycles of data preparation, model refinement, and stakeholder feedback to stay relevant and avoid drift.
● Integration with organizational processes: CPMAI stages effectively complement conventional project management practices (including Agile and DevOps/MLOps),
providing the AI-specific conditions necessary for success.
● Trustworthy AI: Ethical, responsible, and transparent development practices are integral to long-term AI adoption. CPMAI places special emphasis on bias detection, governance, and stakeholder engagement at each stage.
● Team and culture: AI success depends on the right distribution of roles – data engineers, data scientists, analysts, subject matter experts, and project managers – working together using an agile, learn-as-you-go approach.
Explore the Latest in AI Technology
https://theresanaiforthat.com/ – is one of valuable AI classifiers.
It crawls on Internet and publishes information about all new AI assistants and agents.
You can subscribe to updates based on your preferences so that you will be always aware about new agents and assistants.
Discussion on PMBOK 8th draft
last month, the PMBOK8 draft was published, and the first comments on it appeared, causing a heated discussion in the professional community.
One of the striking differences is the return of the process model directly to the structure of the PMBOK8 body of knowledge. Let me remind you that in version 7, based on principles, the processes were taken out of the PMBOK itself and placed in a separate material on the website. A serious discussion broke out around this change, which I personally think is excessive, since project management in the modern world is so diverse that it is hardly possible to “drive” all the options into the framework of predefined processes. Therefore, the model of principles (which, by the way, also remain in version 8) seems to me to be quite appropriate.
The number of principles is reduced from 12 in version 7 to 6 in version 8. Let’s see. At the same time, no one is belittling the value of processes as a repetitive activity. The process records the best practices, but at a more local level. So this discussion, in my opinion, is too methodological. Even with the inclusion of processes directly in PMBOK, each enterprise will still adapt the model “for itself”, which has always been the case.
The concept of “Value” is still in the spotlight. However, the focus is shifting to a more practical understanding – Benefits prevail over costs – the classic “scales”.

In the definition of key project characteristics, a very useful concept of a unique context has been introduced, in my opinion. As has been obvious for many years, not every project (or rather most of them) is completely unique, but the conditions for implementation are unique (or different). So this definition is more accurate. In version 8, the division of product and project management roles is developing. In essence, classic analysis (first divide) and synthesis are implemented. As practitioners have been saying for many years (including me, I will be immodest), a project is a way of implementing and developing a product.

The product owner can act as a customer of a project for the creation/development of a product.

It is proposed to remove the chapter “Methods, Models, and Artifacts” from PMBOK 8, which in my opinion will significantly reduce the usefulness of PMBOK itself. Although the authors write in their blogs that this is positive, since the chapter did not fit into the context, but – again in my opinion – the context here is not necessary, this chapter is actually a reference book in version 7, from which you can get the necessary specific information as needed. A step back. Perhaps they will publish it separately, but it is not known yet.
Functional elements have been added to project management – 7 basic functions
- Review and coordination
- Feedback
- Facilitation and support
- Execution of work
- Application of expert skills
- Providing business direction and “inside view”
- Provision of resources
Communications, quality and delivery have been removed from the performance domains. If everything is clear with deliveries, this area has essentially been outside the scope of the project for a long time, and the RP acted as an internal customer, then the removal of communications and quality looks strange.
We look forward to the continuation of the discussion, access to the draft itself can be obtained in reviewer mode (commenting is not required)
Challenges in moving to DevOps Culture
Axelos, famous for its ITIL(r) and PRINCE(r) frameworks, issued a series of publications on DevOps culture and DevOps engineering.
In this publication our authors discuss the presented 4 challenges/barriers on the organization’s road to DevOps culture.
“1. An organization’s structural barrier keeps DevOps teams from thriving:
Organizational structure barriers are easy to spot but difficult to change.These organizational structural barriers include the following:
a) the excessive layers of anxious middle management which stand between ideas and their execution,
b) pathologically siloed organizational structures with no history of or incentives to engage in collaboration, and
c) senior-level executives who are not able, willing, or skilled to lead digital disruption in the company.
2. Cultural habits an fears prevent individuals and teams from innovating: for 25% of global enterprise IT organizations, a change in culture is one of the top three challenges they are facing (Upskilling IT 2023). Culture refers to the organization’s informal patterns that signal to people which behaviors are right and which behaviors define you as difficult.
The challenges can be summarized as:
a) not bringing the right people into the organization or not keeping and developing them once there,
b) aversion to risk-taking and proposing innovative ideas, and existing habits of seeing past failures and successes inhibit change.
3· Existing processes, bureaucracy, and procedural hurdles challenge even motivated staff members and teams: existing complex processes hamper the ability to make changes as there are too many dependencies and constituencies to connect. For 15% of IT enterprise organizations, the lack of innovative operating models hampers their progress. Existing processes and procedures are important as they are useful in getting things done, but they also cause issues if there is too much emphasis on internal processes and procedures versus the focus on outcomes.
4· Technology trends will continue to drive challenges: although there are a variety of technology topics that are interesting, exciting and might provide a variety of benefits, technology challenges are unavoidable, but the continuous adoption of technology continues to increase the technical debt. For 31% of IT enterprise organizations, managing technical debt and/or avoiding technical debt is a significant challenge. “
AI and Risk management
AI tools help us to manage risks in the whole risk management lifecycle, but implementing AI deals with new risks itself.
Watch our new presentation on the AI in Risk Management.
PMI Standard for Program Management 5th Overview
By March 2024. PMI launched a new standard for the promotion of project programs в.
Like recent versions of the PMBOK, the program standard is based on principles that serve as guidelines for the behavior of people involved in programs as they influence and delineate program performance domains.
8 principles of Program management:
Stakeholders
Realization of benefits
Synergy
Team of teams
Changes
Leadership
Risks
Management
Management and control of the program are implemented within 6 domains:
Alignment with strategy
Benefits management
Involving interested parties (stakeholders)
leadership environment (framework)
Cooperation
Lifecycle management
Accordingly, the key competencies of the program manager are determined within the framework of the given domains, as well as – Systematic and analytical thinking and risk management skills, the ability to work in a VUCA environment (volatility, uncertainty, complexity, vagueness).
The basic structure of the program life cycle has remained unchanged (see figure below) and includes:
Defining the program (formulation and planning)
Delivering technical and business deliverables (including authorization and planning of program components, review and integration of components, handover and closure of components)
Consolidation and support of benefits
Program closure (program transfer, support of closure procedures and archiving of artifacts)
Send feedback
Side panels
History
Saved


XP (Extreme Programming) and SAFe (Scaled Agile Framework) were also mentioned as possible program management frameworks.
Program Management Principles
Involved parties (stakeholders)
Realization of benefits
Synergy – achieving super-effect, greater than from individual projects
Team of teams – coordination of multiple teams
Changes
Leadership
Risks
Management

Thus, we see a clear trend towards leadership and flexible approaches, which, in general, has always distinguished program management as a coordinating structure that manages according to benefits and priorities.
Program activities
Program integration management
— Infrastructure development
— Provision management
- performance management
— benefits management activities
— support for the program change plan
Definition phase activities (new entity)
Delivery phase activities (new entity)
Closing phase activities (new entity)
Supporting activities
Integration Management
Change management
Communications management
Financial management
Information Management
Supply chain management
Quality control
Resource management
Management of risks
Schedule management\Content management

A useful feature of the new standard is the addition of an appendix that briefly describes the main tools and techniques.
IT Product consulting services
We are happy to inform that DevOps Agile skills association (DASA) approved us as an accredited consulting partner for DevOps and Product management.
We are happy to offer our services – contact us directly through website forms.
To start with you can take our brief IT Product management online training on Udemy platform at a special price $12.99 till January, 16th.

Updates in PMP exam procedure
PMI announced radical changes in the certification exam procedure starting 2023, September, 25th.
The exam answers will be sent to PMI, so a candidate receives results in within 5 business days AFTER the exam take-date.
In case of candidate’s misconduct, the exam result is put in failure, and the next attempt is allowed in a test center (CBT) only. Online is prohibited.
PMP 180 sample questions by Olivier Lehman
Enjoy the updated to the latest PMP version sample questions. Good luck at you PMPM exam!
CAPM exam changes
PMI published the new contents outline and rules for the CAPM certification.
Now CAPM becomes the next step after student-oriented PM Ready certification.
It includes the same 4 domains:
- PM Fundamentals and core concepts
- Predictive, Plan-based methodologies
- Adaptive frameworks/methodologies
- Business analysis frameworks.
Current eligibility criteria are: secondary diploma AND 23 hours of formal education in PM.
Now CAPM holders can prolong their status by gaining 15 PDUs each 3 years.