CPMAI Phase IV: Model Development

5 minutes 5 Questions

In the PMI Cognitive Project Management for AI (CPMAI) methodology, Phase IV, Model Development, is where the AI solution is built. It follows Business Understanding (Phase I), Data Understanding (Phase II), and Data Preparation (Phase III), and it comes before Model Evaluation (Phase V) and Model Operationalization (Phase VI). In the PMI-CPMAI domain 'Manage AI Model Development and Evaluation,' the project manager does not need to code. Instead, the role is to oversee the work, align it with goals, and keep it governed. The phase begins by selecting a modeling approach suited to the AI pattern chosen in Phase I. Examples include recognition, conversational systems, predictive analytics, pattern and anomaly detection, personalization, goal-driven systems, and autonomous systems. Teams choose among supervised, unsupervised, and reinforcement learning. They also decide whether to build a custom model, fine-tune a pretrained or foundation model, or use a vendor API. These choices weigh accuracy against cost, time, explainability, and available skills. Key activities include: - Splitting data into training, validation, and test sets. - Engineering features. - Training candidate models and tuning hyperparameters. - Comparing results against a baseline. - Applying ensemble or transfer-learning techniques where useful. The project manager makes sure the team tracks experiments and versions both data and models. Documentation of assumptions and reproducible pipelines support auditability. Trustworthy AI considerations are built in from the start. These include bias detection, fairness, transparency, explainability, privacy, and security. CPMAI stresses iteration and the 'think big, start small, iterate often' principle. Teams develop a minimum viable model rather than pursuing perfection. If data proves insufficient, they loop back to earlier phases. The project manager also manages several practical concerns: - Compute resources and budget. - Timeboxing of experiments. - Overfitting and underfitting risks. - Communication with stakeholders. The main deliverable is a trained candidate model with documentation. This model must be ready for rigorous testing against the business and technical success criteria defined in Phase I. Those criteria determine whether the project proceeds to Phase V evaluation or returns to an earlier phase.

CPMAI Phase IV: Model Development - Complete Exam Guide

CPMAI Phase IV: Model Development

What Is CPMAI Phase IV?
The Cognitive Project Management for AI (CPMAI) methodology, now part of PMI's AI project management offerings, is an iterative, data-centric framework for running AI and machine learning projects. It has six phases:
1. Business Understanding
2. Data Understanding
3. Data Preparation
4. Model Development
5. Model Evaluation
6. Model Operationalization

Phase IV, Model Development, is where the prepared data is turned into a working AI model. The team chooses algorithms and approaches, trains models, tunes hyperparameters, and produces candidate models. These candidates move on to formal evaluation in Phase V.

Why Is Phase IV Important?
- It turns plans into a working asset. Earlier phases define the problem and prepare data. Phase IV produces the model that delivers the value.
- It decides fitness for purpose. Choices about algorithms, features, and training methods directly affect accuracy, explainability, fairness, and cost.
- It controls risk. Poor development practices lead to overfitting, data leakage, bias, and models that fail in production. Disciplined development lowers these risks.
- It manages cost and time. Training can be expensive in compute and talent. Smart choices, such as reusing pre-trained models, save resources.
- It keeps the work tied to the business. CPMAI insists that development stays linked to the success criteria set in Phase I. A technically impressive model that does not solve the business problem has failed.

Key Activities in Phase IV

1. Selecting the Modeling Approach
- Match the approach to the AI pattern identified in Phase I. The seven patterns are recognition, conversational/human interaction, predictive analytics and decisions, patterns and anomalies, hyper-personalization, autonomous systems, and goal-driven systems.
- Choose the learning type: supervised, unsupervised, semi-supervised, reinforcement, or self-supervised.
- Weigh trade-offs: accuracy versus explainability, complexity versus maintainability, compute cost versus performance.
- Decide on build, buy, or reuse. Options include pre-trained models, foundation models, transfer learning, fine-tuning, third-party APIs, or training from scratch.

2. Choosing Algorithms
- Examples include decision trees, random forests, gradient boosting, neural networks, support vector machines, clustering algorithms, and large language models.
- Constraints shape the choice: data volume, labeled data availability, latency needs, regulations requiring explainability, and deployment environment.

3. Data Splitting and Training Strategy
- Split data into training, validation, and test sets to prevent overfitting and give an honest performance estimate.
- Use cross-validation where appropriate.
- Guard against data leakage, where information from the test set or the future gets into training.

4. Model Training
- Feed training data to the algorithm so it learns patterns.
- Monitor training metrics and loss curves.
- Manage compute resources, whether cloud, GPUs, or on-premise.

5. Hyperparameter Tuning and Optimization
- Adjust settings such as learning rate, tree depth, number of layers, and regularization strength.
- Techniques include grid search, random search, Bayesian optimization, and AutoML.

6. Ensemble and Iteration
- Combine models through bagging, boosting, or stacking to improve performance.
- Iterate. Development often reveals data problems that require going back to Phase II or III.

7. Documentation and Versioning
- Track experiments, model versions, data versions, parameters, and results. MLOps tools help with this.
- Record design decisions to support transparency, reproducibility, auditability, and trustworthy AI.

8. Trustworthy AI Considerations
- Build in fairness, bias mitigation, explainability, privacy, and security during development, not after.

How Phase IV Works Within CPMAI
- Iterative and agile. CPMAI favors short iterations. Teams should build a minimum viable model quickly, test it, and refine it rather than aim for perfection in a single pass.
- Feedback loops. If model performance is inadequate, the team may return to Data Preparation (Phase III), Data Understanding (Phase II), or even Business Understanding (Phase I). Phase IV and Phase V are especially tightly linked.
- Go/no-go mindset. Every phase includes checkpoints. If a model cannot meet the success criteria, the project may need to pivot, rescope, or stop.
- Cross-functional teams. Data scientists and ML engineers lead the technical work. Project managers coordinate scope, schedule, resources, risk, and stakeholder communication. Subject matter experts validate that model behavior makes sense.

Key Inputs and Outputs
- Inputs:
  - Prepared, cleaned, and labeled datasets from Phase III
  - Business success criteria and KPIs from Phase I
  - AI pattern identification
  - Technical and regulatory constraints
- Outputs:
  - Trained candidate models
  - Documented configurations and hyperparameters
  - Experiment logs
  - Preliminary performance metrics
  - Readiness for Phase V evaluation

Common Pitfalls
- Overfitting: the model memorizes training data and fails on new data.
- Underfitting: the model is too simple to capture patterns.
- Data leakage that inflates performance numbers.
- Picking overly complex models when simpler ones would do. CPMAI favors the simplest effective solution.
- Ignoring explainability requirements in regulated industries.
- Building from scratch when a pre-trained model or vendor solution would work.
- Losing alignment with business objectives.
- Poor version control that prevents reproducibility.

Exam Tips: Answering Questions on CPMAI Phase IV: Model Development

Tip 1: Know the phase order and boundaries. Model Development is Phase IV. It sits after Data Preparation and before Model Evaluation. Questions often test whether an activity belongs in this phase:
- Training and tuning belong to Phase IV.
- Formal validation against business criteria belongs to Phase V.
- Deployment and monitoring belong to Phase VI.

Tip 2: Think iteratively. When a question describes poor model performance, the best answer often involves going back to an earlier phase, especially data preparation or data understanding, rather than endlessly tuning. CPMAI says that data, not algorithms, is usually the root cause.

Tip 3: Favor business alignment. If an option prioritizes technical sophistication over meeting business success criteria, it is usually wrong. Look for answers that tie model choices back to Phase I objectives.

Tip 4: Prefer the simplest effective solution. CPMAI encourages reusing pre-trained models, transfer learning, or third-party solutions when appropriate. "Build from scratch" is rarely the best first choice unless the scenario demands it.

Tip 5: Watch for trustworthy AI cues. When a scenario mentions regulated industries, customer impact, or fairness concerns, choose answers that build in explainability, bias checks, and documentation during development.

Tip 6: Recognize overfitting and leakage scenarios. Very high training accuracy with poor test performance means overfitting. Unrealistically perfect results suggest leakage. Correct responses include:
- Regularization
- More data
- Simpler models
- Cross-validation
- Fixing the data split

Tip 7: Remember the PM's role. The project manager does not tune hyperparameters personally. They facilitate, manage scope creep (the temptation to keep improving), track compute costs, manage risks, ensure documentation, and communicate with stakeholders. Choose answers that reflect facilitation and governance.

Tip 8: Small, fast iterations. CPMAI favors short iterations and minimum viable models. Avoid answers proposing long, waterfall-style development before any testing.

Tip 9: Link to the AI patterns. Questions may describe a use case and ask which approach fits. Match the pattern to the method, for example:
- Recognition: image classification, computer vision
- Patterns and anomalies: anomaly detection, clustering
- Predictive analytics: regression or classification

Tip 10: Eliminate extreme answers. Options with "always," "never," or skipping phases are typically wrong. Choose balanced, process-respecting answers.

Sample Question
A team's model shows 99% accuracy on training data but 62% on unseen test data. What should the project manager encourage the team to do first?
A) Deploy the model and monitor it
B) Investigate overfitting and possible data issues, applying regularization or revisiting data preparation
C) Replace the team with more experienced data scientists
D) Lower the business success criteria
Answer: B. The gap signals overfitting. CPMAI's iterative approach supports refining the model or returning to data preparation. Deploying (A) skips evaluation. Option C is not a process answer. Lowering criteria (D) breaks business alignment.

Summary
Phase IV converts prepared data into candidate AI models through approach selection, algorithm choice, training, tuning, and documentation. It is iterative, tied to business objectives, and closely connected to the Data Preparation and Evaluation phases. For the exam, remember:
- Data-first thinking
- Iteration over perfection
- Reuse over reinvention
- Trustworthy AI built in from the start
- The PM's role as facilitator and governor of the process
Test mode:
More CPMAI Phase IV: Model Development questions
15 questions (total)

Other Manage AI Model Development and Evaluation concepts

Algorithm Selection Criteria and DocumentationCoding Standards and Best Practices for AI DevelopmentConfiguration Management for Model Versions and ParametersCPMAI Phase III: Data PreparationCPMAI Phase V: Model EvaluationCross-Validation and Model SelectionData Augmentation and Synthetic DataData Cleaning and Preprocessing WorkflowsData Normalization and StandardizationData Readiness Decisions and DocumentationDeployment Readiness and Infrastructure RequirementsEvaluating Algorithms for Specific Use CasesEvaluating Model Performance Against Success CriteriaFeature Engineering and Feature SelectionFinal Approval for Model DeploymentFinal Data Quality Assessment Before TrainingHyperparameter Tuning and OptimizationModel Documentation and Operational ProceduresModel Evaluation Metrics: Accuracy, Precision, Recall and BeyondModel Robustness and GeneralizationModel Testing Protocols and Quality AssuranceMonitoring Model Performance Metrics in DevelopmentMonitoring Training Progress and Compute UtilizationOverfitting, Underfitting and GeneralizationPeer Review and Technical Validation of Model DesignsRepresentativeness and Bias Checks Before ModelingReproducible and Documented Data TransformationSupervised, Unsupervised and Reinforcement LearningTrade-offs Between Model Complexity, Performance and InterpretabilityTraining Data Versioning and Experiment TrackingTraining Schedules and Resource AllocationValidating Preprocessing and Transformation ResultsWorking with Data Scientists on Model Architecture