Select and Implement Process Models and Methods
This post is a terminology explanation for selecting process models – including exam questions, core components, and tags.
In a Nutshell
The selection of a process model depends on context factors such as risk, regulation, team, and change dynamics. Subsequently, suitable methods and artifacts are combined, tailored, and controlled via metrics.
Compact Technical Description
Process models structure projects into phases/iterations and define artifacts.
- Classical (Waterfall, V-Model XT): Planability, formal evidence
- Agile (Scrum, Kanban): Short feedback cycles
- Hybrid: Combines governance (e.g., stage gates) with iterative delivery
Selection is criteria-driven:
- Criticality / Risk
- Compliance/Regulatory
- Change rate
- Delivery pressure
- Team maturity / Distribution
- Contract type
Important: Document tailoring (what is mandatory, what is omitted, why) + use metrics meaningfully (Lead Time, defect density, Velocity, CFD).
Exam-Relevant Key Points
- Context analysis based on criteria (IHK)
- Explain and justify classical vs agile vs hybrid
- Define artifacts/checklists (DoR/DoD, acceptance)
- Name roles clearly (PO, SM, project management, QM)
- Establish metrics (flow + quality)
- Manage risks (prototypes/spikes, reviews)
- Documentation requirements (tailoring log, acceptances, traceability)
Core Components
- Context analysis + criteria weighting
- Process architecture (phases/sprints/milestones)
- Role model + escalation
- Artifacts + DoR/DoD
- Planning methods (roadmap/release/sprint)
- QA (reviews, TDD, CI/CD, test strategy)
- Risk management
- Tailoring guide
- Metrics + reporting
- Compliance/Security
Practical Example (Decision Matrix)
Web portal (regulatory + integration risk + desire for early increments)
Criteria (weight):
- Regulatory 30
- Change rate 20
- Integration risk 20
- Delivery pressure 15
- Team maturity 15
Rating 1..5:
- Waterfall: 5/2/2/3/3
- Scrum: 3/5/4/4/4
- V-Model XT:5/2/3/3/3
- Hybrid: 5/4/4/4/4 -> highest score
Hybrid Tailoring:
- Stage gates (requirements release, architecture release, go-live)
- Implementation in 2-week sprints
- Mandatory artifacts: risk register, ADRs, test protocols, acceptance
Advantages and Disadvantages
Advantages
- Decision is traceable (matrix)
- Risk/compliance visibly addressed
- Feedback cycles improve quality
Disadvantages
- Assessment can be subjective
- Hybrid requires experience in governance + agility
- Metrics can create perverse incentives
Typical Exam Questions (with Short Answer)
- What criteria help with the selection? Risk, regulatory, change rate, team, delivery pressure, contract.
- What belongs in a tailoring document? Adjustments/omissions with justification, mandatory evidence, roles, reviews, metrics.
- How do you combine V-Model XT and Scrum? Gates/evidence from V, delivery in sprints with reviews.
Learning Strategy
- Compare 2 project contexts and sketch tailoring.
- Calculate decision matrix with 5 criteria.
- Practice brief justification (3 sentences).