Accendo Reliability

Your Reliability Engineering Professional Development Site

  • Home
  • About
    • Contributors
    • About Us
    • Colophon
    • Survey
  • Reliability.fm
  • Articles
    • CRE Preparation Notes
    • NoMTBF
    • on Leadership & Career
      • Advanced Engineering Culture
      • ASQR&R
      • Engineering Leadership
      • Managing in the 2000s
      • Product Development and Process Improvement
    • on Maintenance Reliability
      • Aasan Asset Management
      • AI & Predictive Maintenance
      • Asset Management in the Mining Industry
      • CMMS and Maintenance Management
      • CMMS and Reliability
      • Conscious Asset
      • EAM & CMMS
      • Everyday RCM
      • History of Maintenance Management
      • Life Cycle Asset Management
      • Maintenance and Reliability
      • Maintenance Management
      • Plant Maintenance
      • Process Plant Reliability Engineering
      • RCM Blitz®
      • ReliabilityXperience
      • Rob’s Reliability Project
      • The Intelligent Transformer Blog
      • The People Side of Maintenance
      • The Reliability Mindset
    • on Product Reliability
      • Accelerated Reliability
      • Achieving the Benefits of Reliability
      • Apex Ridge
      • Field Reliability Data Analysis
      • Metals Engineering and Product Reliability
      • Musings on Reliability and Maintenance Topics
      • Product Validation
      • Reliability by Design
      • Reliability Competence
      • Reliability Engineering Insights
      • Reliability in Emerging Technology
      • Reliability Knowledge
    • on Risk & Safety
      • CERM® Risk Insights
      • Equipment Risk and Reliability in Downhole Applications
      • Operational Risk Process Safety
    • on Systems Thinking
      • Communicating with FINESSE
      • The RCA
    • on Tools & Techniques
      • Big Data & Analytics
      • Experimental Design for NPD
      • Innovative Thinking in Reliability and Durability
      • Inside and Beyond HALT
      • Inside FMEA
      • Institute of Quality & Reliability
      • Integral Concepts
      • Learning from Failures
      • Progress in Field Reliability?
      • R for Engineering
      • Reliability Engineering Using Python
      • Reliability Reflections
      • Statistical Methods for Failure-Time Data
      • Testing 1 2 3
      • The Manufacturing Academy
  • eBooks
  • Resources
    • Accendo Authors
    • FMEA Resources
    • Glossary
    • Feed Forward Publications
    • Openings
    • Books
    • Webinar Sources
    • Podcasts
  • Courses
    • Your Courses
    • Live Courses
      • Introduction to Reliability Engineering & Accelerated Testings Course Landing Page
      • Advanced Accelerated Testing Course Landing Page
    • Integral Concepts Courses
      • Reliability Analysis Methods Course Landing Page
      • Applied Reliability Analysis Course Landing Page
      • Statistics, Hypothesis Testing, & Regression Modeling Course Landing Page
      • Measurement System Assessment Course Landing Page
      • SPC & Process Capability Course Landing Page
      • Design of Experiments Course Landing Page
    • The Manufacturing Academy Courses
      • An Introduction to Reliability Engineering
      • Reliability Engineering Statistics
      • An Introduction to Quality Engineering
      • Quality Engineering Statistics
      • FMEA in Practice
      • Process Capability Analysis course
      • Root Cause Analysis and the 8D Corrective Action Process course
      • Return on Investment online course
    • Industrial Metallurgist Courses
    • FMEA courses Powered by The Luminous Group
    • Foundations of RCM online course
    • Reliability Engineering for Heavy Industry
    • How to be an Online Student
    • Quondam Courses
  • Calendar
    • Call for Papers Listing
    • Upcoming Webinars
    • Webinar Calendar
  • Login
    • Member Home
  • Barringer Process Reliability Introduction Course Landing Page
  • Upcoming Live Events
You are here: Home / Articles / Statement of Work Fundamentals

by Robert Allen Leave a Comment

Statement of Work Fundamentals

Statement of Work Fundamentals

In my last article, we reviewed a proposed Product Life Cycle process, which starts with a “Define” phase.  In the “Define” phase, we are defining the project as well as the product.

We previously discussed the ‘technical leg’ of this process with the market analysis, identifying customer needs, product requirements, verification and validation, etc.

Meanwhile, the Statement of Work (SOW) is often a companion document (usually provided to a vendor from a customer), which states project (non-technical) requirements.  To clarify the content/scope of the SOW, it’s worth revisiting our definition of a requirement and applying it to a project:

  • “What will the project provide (outputs/deliverables) in order to ensure the customer(s) the product is fully developed?  What work will be performed?
  • “What does the project need (inputs/deliverables) from the customer(s), in order to ensure optimum project performance?”

The use of the term “will” is usually reserved for work that will be done (as per the SOW), and product requirements are best stated as “shall”.  Also, the SOW defines what “done” means in an unambiguous way such that the customer (internal and external customer) could confidently declare it completed.

Note that compliance with the SOW (and/or project plan) represents good project quality in the eyes of the customer.

In an SOW, we might tend to focus on what we will provide to the customer (for example, product prototypes, a validation test report, etc.).  However, some inputs or work to be performed might be needed from the customer as well, and would be defined in the SOW accordingly.   An example of this is drawings that determine the envelope within which the product must fit.  (While the drawing dimensions are a technical requirement, the drawing itself is a SOW item that will be provided by the customer.)

Often a customer-provided SOW may contain a mix of project (non-technical) requirements, customer needs, product (technical) requirements, design constraints, etc.  Conversely, customer-provided requirements may contain SOW items.  An “internal” SOW and PRD (with traceability to the customer-provided document) can be written to ensure a healthy distinction and clarify the hand-off to project management and engineering.

The SOW is the project managers’ opportunity to clarify and establish a mutual understanding of the project work scope and deliverables, and to integrate them into the project plan, work breakdown structure and project schedule.  Following these simple guidelines can help reduce misunderstandings and achieve a successful product and a high quality project.

Filed Under: Articles, on Leadership & Career, Product Development and Process Improvement Tagged With: Requirements

About Robert Allen

Robert Allen has over 25 years of professional experience in the areas of product development, process improvement and project management. Rob was a key contributor to numerous deployments of lean sigma and project management organizations, most notably with Honeywell and TE Connectivity. Included in Rob’s experience are multiple certifications and over 25 years of practice in the development, teaching, execution, and leadership of product lifecycle, lean product development, DFSS, lean six sigma, project management, systems engineering and supply chain.

« Stages of Awakening
Cardboard and Duct Tape: Lessons in Engineering, Leadership and Life »

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Articles by Rob Allen
in the Product Development and Process Improvement series

Join Accendo

Receive information and updates about articles and many other resources offered by Accendo Reliability by becoming a member.

It’s free and only takes a minute.

Join Today

Join PD&PI

[display_form id=369] Your email is safe and the opt-in here provides your permission to send messages concerning the PD&PI article list plus special announcements. Privacy Policy

Recent Posts

  • Leadership Values in Maintenance and Operations
  • Today’s Gremlin – It’ll never work here
  • How a Mission Statement Drives Behavioral Change in Organizations
  • Gremlins today
  • The Power of Vision in Leadership and Organizational Success

© 2025 FMS Reliability · Privacy Policy · Terms of Service · Cookies Policy