Team Purpose   

• Engaging Stakeholders
• Teaming Up
• Appreciating Values
• Modeling Development
• Planning Responsibilities
• Empowering Co-workers
• Adapting in Turbulence
• Delivering Value

 Know-how Perspective

• Business

•  Systems

•  Kaizen

•  Design

•  Plan-driven 

•  Agile

Project Constructs

 In these playlists, each post sets out a video on one project construct. When the word “construct” is used as a noun, as here, its first syllable is accented, and it means an idea or concept that is created for some purpose by some person(s). So, a construct is an idea that has been constructed by some person(s), typically so that some person(s) can do or construct something better or more easily.    

Consistent with this, Cogent Language uses the phrase “project construct” (or just “construct”) to mean any process, technique, method, artifact, model, or ceremony that project teams use to actually build things.  Example “constructs” are “product backlog”, “work breakdown structure”, and “daily scrum”.  More constructs appear in the blue tag cloud on the home page of the blog, pictured here. 

Since project constructs as we define them are actionable, the actions – and the inputs, outputs, and benefits that they involve – can be seen/ So, they are very usefully demonstrated by the medium of video.  Thus, we call our video log on project methods, processes, and so forth, “Project Constructs”.

 While a construct is a mental model, here, it is a model that is actionable by a group, as is a map, a recipe, or a blueprint.  In this way, it differs from, say, a “value”, “principle”, “theory”, or “worldview”. These have more abstract meanings and are much less actionable by a group. Note that our “construct”  also differs from a “tool”, “machine”, “technology” or (technical) "system”. These are terms for concrete objects or categories of objects, rather than recipe-like mental models actionable by a group.