Concepts and terminology

The aim of this text is to formalize terminology and use it when adapting Redmine to our purposes. Terminology consists of concepts. Ideally, the terminology of project funding agencies, our common sense experience from past projects and Redmine concepts should be non-overlapping to minimize possible confusions. We consider also terminology of European Commission and particularly its FP7 IST STREP projects vocabulary.

Concepts/terms used in EC projects

The terminology has been used in FP7 proposals, descriptions of work (DoWs), e.g. in the c-gfacp-strep-201107_en.pdf

  • Activity = {RTD (research and technology development), MNG (management), demonstration, other}
  • Work plan (in Czech - plán práce)
  • Work package (in Czech - pracovní balíček)
  • Task (in Czech - úkol)
  • Deliverable (in Czech - předmět dodávky, výstup)
  • Milestone (in Czech - milník)

Additional concepts/terms used in our projects

"Our" in the title means projects conducted in V. Hlavac's group at CTU in Prague.

  • Scenario (in Czech - scénář)
  • Demonstrator (in Czech - demonstrátor)
  • Experimental testbed (in Czech - zkušební zařízení)

Redmine-related terminology

Redmine uses several terms which relate to work planning/reporting. We introduce two terms briefly because we assume that the reader has not been familiar with Redmine yet. Let start with a few of them to bootstrap the whole process.

  • Activity (in Czech - činnost?) - is the name of Redmine top-level page containing a short summary of the latest project actions. Users may subscribe to action of their interest too.
  • Issue (in Czech - událost?) - is the key Redmine concepts allowing establishing factual and time relation among project "entities". The issue can be tracked in time, it is recorded if someone works on the issue, it can be tracked. The issue has a start and finish, etc. The Redmine issue has attributes. We will mention only to of them the (a) Tracker name and (b) the Issue category. Both attributes can be modified in order to help adapting Redmine for the project management purposes.

The concepts mentioned above should be avoided while extending Redmine concepts suiting for our managerial and work planning/reporting purposes. The implicit duplication of the term "activity" exists between EC projects and Redmine vocabularies. However, the semantics of both is rather distinct. There is a little danger of confusion here.

Adjusting Redmine to serve specific project needs

Our adaptation starts with extending the principal Redmine tool, the Issue Tracking Module. We deal with two attributes of the issue mentioned above. The first attribute is the Tracker which specifies the type of the issue. We extended the three predefined Trackers (Bug, Feature, Support) by two additional Trackers (Assignment, Job) according to our managerial needs.

The second attribute named the Issue category serves for the additional narrowing of the Tracker scope. The Issue category is selected from a predefined list when the Issue is created. The list of issue categories can be created/modified according to project needs. We do not list issue categories here for simplicity.

Concepts/terms needed for the project management

The intention is to use unique concepts for such Redmine adaptation which do not overlap with both the managerial terminology used in European Commission funded projects and the Redmine terminology. The concepts/terms specific to our extension of Redmine are the following:

  • Team's role (in Czech - role týmu), e.g. a team responsible for the robot collision avoidance module
  • Person's role (in Czech - role osoby), e.g. a designer of the robot collision avoidance module
  • Assignment (in Czech - úloha)
  • Job (in Czech - dílčí úkol)

Go to the next section Principles of work planning and reporting.


Responsible Vasek Hlavac (c),

c-gfacp-strep-201107_en.pdf - EC STREP Guide for applicants 2011-07 (287 KB) Vasek Hlavac, 01/05/2014 04:42