Process models provide structured frameworks for organizing, executing, and managing work. Industry recognizes various process models that help teams understand workflows, develop solutions iteratively, and manage complexity. These models range from simple placeholders to comprehensive development approaches.
Strawman Process Model
Strawman is an intentionally flawed or incomplete first draft created as a starting point for discussion, refinement, and improvement. The purpose is not to present a final solution but to provide something tangible that stakeholders can critique, modify, and enhance.
Key characteristics:
- Deliberately simple or incomplete
- Expected to be torn down and rebuilt
- Stimulates discussion and feedback
- Faster than trying to create the perfect solution initially
- Reduces "blank page syndrome"
- Encourages participation through criticism
Process: Create initial draft → Present to stakeholders → Gather feedback → Revise iteratively → Develop robust solution
This approach works well when requirements are unclear, stakeholders have diverse opinions, or teams are stuck in analysis paralysis.
Other Key Process Models
Waterfall (Sequential/Predictive) - Linear progression through distinct phases (Requirements → Design → Implementation → Testing → Deployment → Maintenance). Each phase must be completed before the next begins. Works well for projects with stable, well-understood requirements but struggles with change and late-stage discovery of issues.
Iterative Model - Develops the solution through repeated cycles, with each iteration refining and expanding the product. Allows for progressive elaboration and incorporation of feedback. Each iteration produces a working version that improves upon the previous one.
Incremental Model - Delivers the solution in pieces (increments), with each increment adding new functionality. Unlike iterations that refine the whole, increments build up the complete solution piece by piece. Users can begin using earlier increments while later ones are developed.
Agile (Adaptive) - Family of iterative and incremental approaches emphasizing flexibility, customer collaboration, and rapid delivery of working solutions. Includes Scrum, Kanban, XP, and others. Embraces change and delivers value frequently through short cycles (sprints).
Spiral Model - Combines iterative development with systematic risk assessment. Each spiral cycle includes planning, risk analysis, engineering, and evaluation. Particularly useful for large, complex, high-risk projects.
V-Model (Verification and Validation) - Extension of waterfall where each development phase has a corresponding testing phase. Emphasizes verification (did we build it right?) and validation (did we build the right thing?). Development and testing phases form a V shape.
Prototype Model - Creates working models of the solution early to gather user feedback, clarify requirements, and validate design concepts. Prototypes may be throwaway (discarded after learning) or evolutionary (refined into final product).
RAD (Rapid Application Development) - Emphasizes rapid prototyping and iterative delivery with heavy user involvement. Uses workshops, reusable components, and compressed timelines to accelerate development.
DevOps Model - Integrates development and operations through automation, continuous integration/continuous delivery (CI/CD), and collaborative culture. Emphasizes rapid, reliable, and repeatable deployment.
Hybrid Approaches
PMI increasingly recognizes hybrid approaches that combine elements from multiple models. For example:
- Predictive planning with agile execution
- Iterative design with incremental delivery
- Waterfall for infrastructure, Agile for features
The key is selecting and adapting the process model to project characteristics, organizational culture, team capabilities, and stakeholder needs.
Key Concepts
Process Model - A framework or methodology that defines how work is organized, executed, and managed throughout a project or product lifecycle.
Strawman - An intentionally incomplete or flawed initial proposal created to stimulate discussion, feedback, and iterative improvement.
Waterfall Model - Sequential development approach where each phase must be completed before the next begins, flowing downward through stages.
Predictive Lifecycle - Project approach where scope, time, and cost are determined early, and work proceeds according to a detailed plan (traditional/waterfall).
Iterative Development - Approach that develops the solution through repeated cycles, each refining and improving the entire product.
Incremental Development - Approach that delivers the solution in functional pieces, with each increment adding new capabilities to the growing product.
Iteration - A single development cycle that produces a refined version of the product, incorporating learning and feedback.
Increment - A functional piece of the product delivered to add value, which can be used independently or integrated with previous increments.
Agile - Family of iterative and incremental methodologies emphasizing flexibility, collaboration, customer feedback, and frequent delivery of working solutions.
Adaptive Lifecycle - Project approach designed to respond to high levels of change and ongoing stakeholder involvement (agile/iterative).
Spiral Model - Risk-driven iterative process model that cycles through planning, risk analysis, engineering, and evaluation phases.
V-Model - Development approach where each development stage has a corresponding testing phase, forming a V-shaped relationship between construction and verification.
Prototype - A working model of the solution created early to validate concepts, gather feedback, and clarify requirements.
Throwaway Prototype - A prototype built solely for learning and validation, then discarded rather than evolved into the final product.
Evolutionary Prototype - A prototype that is continuously refined and eventually becomes the final deliverable.
RAD (Rapid Application Development) - Methodology emphasizing rapid prototyping, iterative delivery, and heavy user involvement to accelerate development.
DevOps - Cultural and technical approach integrating development and operations through automation, collaboration, and continuous delivery.
Continuous Integration (CI) - Practice of frequently merging code changes into a shared repository with automated testing.
Continuous Delivery (CD) - Practice of ensuring code is always in a deployable state and can be released to production at any time.
Continuous Deployment - Extension of CD where every change that passes automated tests is automatically deployed to production.
Hybrid Approach - Combination of elements from different lifecycle models tailored to project needs (e.g., predictive planning with agile execution).
Sprint - Time-boxed iteration in Scrum, typically 1-4 weeks, that produces a potentially shippable product increment.
Scrum - Agile framework using fixed-length sprints, defined roles (Scrum Master, Product Owner, Team), and specific ceremonies.
Kanban - Agile approach focused on visualizing workflow, limiting work-in-progress, and continuous flow rather than fixed iterations.
Extreme Programming (XP) - Agile methodology emphasizing technical practices like pair programming, test-driven development, and continuous integration.
Progressive Elaboration - Iteratively developing and refining project plans and specifications as more detailed information becomes available.
Phase - A collection of logically related project activities that culminates in completion of one or more deliverables.
Gate - A review point at the end of a phase where continuation decisions are made based on performance and business justification.
Phase Gate - Formal review at phase boundaries to assess whether the project should proceed, be modified, or be terminated.
Lifecycle - The series of phases that a project passes through from initiation to closure.
Development Lifecycle - The process for creating, modifying, and maintaining products, from conception through retirement.
Verification - Confirmation that deliverables meet specifications and requirements (building the product right).
Validation - Confirmation that deliverables meet stakeholder needs and business objectives (building the right product).
Feedback Loop - Mechanism for gathering information about process or product performance and using it to make improvements.
Time-boxing - Setting a fixed duration for an activity or iteration, forcing prioritization and completion within constraints.
Product Backlog - Prioritized list of features, enhancements, and fixes for a product, managed in agile approaches.
Minimum Viable Product (MVP) - Smallest version of a product that can be released to gather maximum validated learning with minimum effort.
Spike - Time-boxed research or investigation activity in agile to reduce uncertainty or explore technical solutions.
Retrospective - Regular team meeting to reflect on process, identify improvements, and adapt working methods.
Burndown Chart - Visual representation showing remaining work over time, commonly used in agile projects.
Velocity - Measure of the amount of work a team completes during an iteration, used for planning future sprints.
Work in Progress (WIP) - The amount of work currently being executed, often limited in Kanban to improve flow.
Release - Deployment of a product version to users, which may contain multiple increments or iterations of work.
User Story - Short description of a feature from the user's perspective, typically following the format "As a [role], I want [function], so that [benefit]."
Acceptance Criteria - Conditions that a deliverable must meet to be accepted by stakeholders or customers.
Definition of Done - Shared understanding of what it means for work to be complete, ensuring quality and consistency.