Task | St. | Effort | Done | Resource | Start | End | Tags | 03.02.2020 Mon | 04.02.2020 Tue | 05.02.2020 Wed | 06.02.2020 Thu | 07.02.2020 Fri | 08.02.2020 Sat | 09.02.2020 Sun | 10.02.2020 Mon | 11.02.2020 Tue | 12.02.2020 Wed | 13.02.2020 Thu | 14.02.2020 Fri | 15.02.2020 Sat | 16.02.2020 Sun | 17.02.2020 Mon | 18.02.2020 Tue | 19.02.2020 Wed | 20.02.2020 Thu | 21.02.2020 Fri | 22.02.2020 Sat | 23.02.2020 Sun | 24.02.2020 Mon | 25.02.2020 Tue | 26.02.2020 Wed | Comment
--- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | ---
requirements |  | 8 | 4 | peter | 03.02.2020 | 03.02.2020 |  | peter requirements (day 1) | . | . | . | . | . | . | . | . | . | . | . | . | . | . | . | . | . | . | . | . | . | . | . |
specification |  | 8 | 4 | peter | 04.02.2020 | 05.02.2020 |  | . | peter specification (day 2) | . | . | . | . | . | . | . | . | . | . | . | . | . | . | . | . | . | . | . | . | . |
module‑one

• implementation

48
peter
06.02.2020
13.02.2020
.
.
.
peter
module‑one

• implementation

(day 4)
.
.
.
.
.
.
.
.
.
.
.
.
.
module‑two

• implementation

72
peter
14.02.2020
26.02.2020
.
.
.
.
.
.
.
.
.
.
.
peter
module‑two

• implementation

(day 12)
all |  |  |  |  | 26.02.2020 | 26.02.2020 |  | . | . | . | . | . | . | . | . | . | . | . | . | . | . | . | . | . | . | . | . | . | . | . | all (day 24) |
1. requirements |  | 8 | 4 | peter | 03.02.2020 | 03.02.2020 |  | 1. requirements | . | . | . | . | . | . | . | . | . | . | . | . | . | . | . | . | . | . | . | . | . | . | . |
2. specification |  | 8 | 4 | peter | 04.02.2020 | 05.02.2020 |  | 2 | 2. specification | . | . | . | . | . | . | . | . | . | . | . | . | . | . | . | . | . | . | . | . | . |
3. module‑one |  | 48 |  | peter | 06.02.2020 | 13.02.2020 |  | 3 | 3 | 3 | 3. module‑one | . | . | . | . | . | . | . | . | . | . | . | . | . |
4. module‑two |  | 72 |  | peter | 14.02.2020 | 26.02.2020 |  | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4. module‑two |
5. all (MS) |  |  |  |  | 26.02.2020 | 26.02.2020 |  | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5. all (MS) |

# 1 Introduction

This text will be converted to markdown, and then be appended to the exported HTML project plan document.
Info nodes, i.e. all `INFO` (`!`) nodes that occur before the first task node, can be used to outline a project (project goals etc).
The text in the task nodes can be used to describe each task, so the resulting document becomes a mixture between a project plan and a technical proposal.
For highly detailed task descriptions it is recommended to link to additional, external documents.

# 2 Project goals

The goal of this project is to serve as a debugging test case.

# 3 Requirements

Identify the requirements in detail and subdivide existing tasks into smaller, more manageable tasks.

# 4 Specification

Once the requirements are known, devise a technical approach and specify the implementation details (architectural overview, block diagrams, ..).
This includes updates to the `.org` files, and possibly the creation of additional technical documents.

# 5 Implementation

## 5.1 Module One

Implement the first module.

### 5.1.1 spec

Here's more info about this in `markdown` format.

### 5.1.2 implement

### 5.1.3 test

## 5.2 Module Two

Implement the second module.
Here's a markdown list:

- item 1
  - sub item 1.1
- item 2
  - sub item 2.1
  - sub item 2.2

### 5.2.1 spec

### 5.2.2 implement

### 5.2.3 test

Document created on 12-Feb-2020 20:04:31