The concept of the project as an engineering document - the basis of a successful project

Story plan

• What is the concept
• How does it work
  

Concept informally

1. Who wants what and why
2. Why now it does not work
3. How it should be arranged for everyone to like
4. What is the most important thing to do to achieve this?

Purpose of the concept

1. Tool for developing and harmonizing understanding:
2. Communication tool providing:
3. Basis for TK and decision making
   
   
4. Filter for project initiation (litmus test)

What is the concept different from TK

• Focus on the causes, objectives of the project and the key properties of the product (rather than detailed descriptions of the properties)
• Brevity (3-10 pages, against 30-80)
• Does not change during the project

Why it is often not written

1. " And so everything is clear ":
   the value of fixing and communication is incomprehensible
   
   
2. “ But the concept is in the letter of Fyodor Ivanovich! ":
   incomprehensible value of formalization
   
   
3. “ What to write, work is necessary! ":
   procrastination
   (preference to do interesting, but not necessary).

When to make a concept?

The risks of working without a concept

• Goal Creep + Scope Creep
• Loss of motivation
• The groundlessness of TK
• Conflicts
• The failure to achieve the goals of the project!

Concept creation process

1. Who wants what?
2. What now? Description of the current situation:
3. What then?
4. How to achieve?

Artistic text properties

• Freedom of presentation (unstructured)
• Fascination
• Emotional coloring

Engineering Document Properties

• Structuredness
• Interconnectedness
• Sequence (from the general to the particular)
• Traceability (traceability) statements

Concept structure

Goal setting

Development of a program to achieve goals

Sources

• RUP Vision Document
• GOST RD 50
• PMBOK Project Charter