Selecting and Implementing Process Models
This post is a definition guide for choosing process models – including exam questions, core components, and key themes.
In a Nutshell
Your choice of process model depends on context factors like risk, regulation, team capability, and rate of change. From there, you combine suitable methods and artifacts, tailor them to fit, and steer progress using metrics.
Quick Technical Overview
Process models structure projects into phases or iterations and define which artifacts are produced.
- Classical (Waterfall, V-Model XT): Predictability, formal evidence
- Agile (Scrum, Kanban): Short feedback cycles
- Hybrid: Combines governance (e.g., stage gates) with iterative delivery
Selection follows a criteria-driven approach:
- Criticality and risk
- Compliance and regulation
- Rate of change
- Delivery pressure
- Team maturity and distribution
- Contract type
Key point: Document your tailoring decisions (what’s mandatory, what’s dropped, and why) and apply metrics meaningfully (Lead Time, defect density, Velocity, Cumulative Flow Diagram).
Exam-Relevant Points
- Context analysis using criteria (chamber of commerce standard). Before selecting a process model, you must analyze project-specific factors such as risk, regulation, rate of change, delivery pressure, team maturity, and contract type. This analysis is tested because it justifies your choice of approach.
- Classical vs agile vs hybrid – explain and justify. Classical models offer predictability and formal evidence; agile models enable short feedback cycles. Hybrid models combine both and are often chosen when governance and flexibility are both required.
- Define artifacts and checklists (DoR/DoD, acceptance). Artifacts like Definition of Ready and Definition of Done set quality and completion criteria. Acceptance protocols document that deliverables have been released.
- Clearly name roles (PO, SM, project lead, QA). In hybrid projects, roles must be well defined. The Product Owner owns requirements, the Scrum Master owns process, project leadership owns overall coordination, and QA owns quality assurance.
- Establish metrics (flow and quality). Metrics like Lead Time, Cycle Time, Velocity, defect density, and Cumulative Flow Diagram measure progress and quality. They enable data-driven steering.
- Manage risks (prototypes, spikes, reviews). Risks are addressed through prototypes, spikes, reviews, and early testing. Risk management must be integrated into your process model.
- Document everything (tailoring log, acceptances, traceability). Tailoring means recording decisions about model adaptation. Acceptances and traceability ensure auditability and transparency.
Core Components
- Context analysis and criteria weighting – Captures project-specific influencing factors. Criteria like risk, regulation, and rate of change are weighted to enable a justified selection of the process model.
- Process architecture (phases, sprints, milestones) – Defines how the project is structured. Hybrid models, for example, use stage gates for decisions and sprints for iterative delivery.
- Role model and escalation – Establishes accountability. Clearly defined escalation paths ensure problems reach the right people quickly.
- Artifacts and DoR/DoD – Work results like Product Backlog, Sprint Backlog, and increments document progress. Definition of Ready and Definition of Done safeguard quality and understanding.
- Planning methods (roadmap, release, sprint) – Structure execution. Roadmaps show the long-term direction, releases mark delivery dates, and sprints define short work packages.
- Quality assurance (reviews, TDD, CI/CD, test strategy) – Covers reviews, Test-Driven Development, Continuous Integration/Continuous Delivery, and a defined test strategy. It reduces defects and improves delivery quality.
- Risk management – Identifies, assesses, and controls risks. Prototypes, spikes, and early reviews help reduce risks before they become costly.
- Tailoring guide – Documents which parts of the process model are adapted or dropped and why. It ensures all stakeholders understand the decisions.
- Metrics and reporting – Metrics like Lead Time, Velocity, defect density, and Cumulative Flow Diagram provide steering data. Reporting communicates status regularly to stakeholders.
- Compliance and security – Compliance ensures regulatory and contractual requirements are met. Security addresses data and system protection throughout the process.
Practical Example (Decision Matrix)
Web portal (regulation + integration risk + desire for early increments)
Criteria (weight):
- Regulation 30
- Rate of change 20
- Integration risk 20
- Delivery pressure 15
- Team maturity 15
Scores 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 approval, architecture approval, go-live)
- Implementation in 2-week sprints
- Mandatory artifacts: risk register, ADRs, test protocols, acceptance sign-off
Strengths and Weaknesses
Strengths
- Decision is traceable (matrix)
- Risk and compliance are visibly addressed
- Feedback cycles improve quality
Weaknesses
- Scoring can be subjective
- Hybrid requires expertise in both governance and agility
- Metrics can create perverse incentives
Typical Exam Questions (with Short Answers)
- What criteria help you choose? Risk, regulation, rate of change, team, delivery pressure, contract.
- What goes in a tailoring document? Adaptations and omissions with justification, mandatory evidence, roles, reviews, metrics.
- How do you combine V-Model XT and Scrum? Gates and evidence from V, delivery in sprints with reviews.
Learning Strategy
- Compare two project contexts and sketch tailoring decisions.
- Work through a decision matrix with five criteria.
- Practice writing a three-sentence justification.
Key Sources
FAQ: Choosing a Process Model, Tailoring, and Hybrid Approaches
1. What is a process model?
A process model is a framework that structures projects into phases or iterations and defines which activities, roles, and artifacts are used.
2. What is a classical process model?
A classical process model such as Waterfall or V-Model XT is phase-oriented and plan-driven. It works best when requirements are stable early and formal evidence is required.
3. What is an agile process model?
An agile process model such as Scrum or Kanban works iteratively and incrementally. It enables short feedback cycles and rapid adaptation to changing requirements.
4. What is a hybrid process model?
A hybrid process model combines elements of classical and agile approaches. For example, it uses stage gates for governance and sprints for iterative delivery.
5. What is tailoring?
Tailoring is adapting a process model to the specific needs of your project. Activities, roles, or artifacts are added, modified, or removed as needed.
6. What is a tailoring document?
A tailoring document describes which parts of the process model are adapted or dropped and the reasons why. It ensures decisions are traceable and documented.
7. What is a decision matrix?
A decision matrix scores different process models against weighted criteria. It helps justify your choice objectively and transparently.
8. What criteria help you select a process model?
Key criteria include criticality, risk, compliance, regulation, rate of change, delivery pressure, team maturity, team distribution, and contract type.
9. What is a stage gate?
A stage gate is a formal decision point between project phases. At each gate, deliverables are reviewed and the go-ahead for the next phase is granted or withheld.
10. What is Scrum?
Scrum is an agile framework that organizes work into short sprints, typically two weeks. It defines roles like Product Owner, Scrum Master, and Development Team, and events like Sprint Planning, Daily Scrum, and Sprint Review.
11. What is Kanban?
Kanban is an agile approach that emphasizes continuous flow instead of fixed iterations. It limits work in progress and visualizes the process on a board.
12. What is V-Model XT?
V-Model XT is a standardized, phase-oriented process model from the public sector. It is particularly suited for safety-critical and heavily regulated projects.
13. What is the Waterfall model?
Waterfall is a classical process model where project phases run sequentially. Each phase must be complete before the next begins.
14. What is a Product Owner?
In Scrum, the Product Owner is responsible for requirements and prioritizing the Product Backlog. They ensure the team works on what matters most.
15. What is a Scrum Master?
The Scrum Master supports the Scrum process and removes obstacles for the team. They act as a coach and facilitator, not as a manager.
16. What is Definition of Ready?
Definition of Ready specifies when a requirement or task is clear enough for the team to begin work. It ensures understanding and completeness before the sprint starts.
17. What is Definition of Done?
Definition of Done describes when a task or increment is considered complete. It typically includes testing, code review, documentation, and acceptance.
18. What is Lead Time?
Lead Time is the duration from when a request is placed until work is completed. It is a key metric for process speed and efficiency.
19. What is Velocity?
Velocity is the amount of work a team completes in a sprint. Usually measured in story points, it helps plan future sprints.
20. What is defect density?
Defect density measures how many bugs occur relative to a unit of work—for example, per 1,000 lines of code. It is a quality metric.
21. What is a Cumulative Flow Diagram?
A Cumulative Flow Diagram visualizes the status of work over time. It shows how many tasks are in each process stage and helps identify bottlenecks.
22. What is a spike?
A spike is a time-boxed research effort in agile projects. It clarifies technical or business uncertainty before a decision is made.
23. What is a prototype?
A prototype is a preliminary model that gathers early feedback. Prototypes clarify requirements and reduce risk before full implementation begins.
24. What is traceability?
Traceability is the ability to track requirements throughout the project lifecycle. It shows which requirements are covered by which tests and artifacts.
25. When is a hybrid process model useful?
A hybrid model makes sense when your project needs both planability, governance, and auditability as well as flexibility and short feedback loops. It blends the strengths of classical and agile approaches.