<commit_before># Planning and Time Management

**[<= Back](../01-communication/communication.md)**		*	*	*	**[Next =>](../03-few-simple-principles/few-simple-principles.md)**

## Table of Contents

### Theory

#### Planning

1. Before planning, trainees should create their issues according to `Issues Guide`
1. During planing team discus issues, corner cases and prepare plan for next iteration

##### Issues Guide

1. Provide meaningful, descriptive  name for the issue
    * NO any 'Exercise 1' or 'My article'
1. Issue shouldn't have empty description, at least link to the 'source' of the issue
    * usually 'sources' of the issue somewhere in our content, for example you always can make a link to any exercise or theory subsection
    * put whatever useful information you may found to solve the issue
1. Provide proper `label` for the issue
1. Provide proper `milestone`, usually they like `trainee-bootcamp`, `trainee-syntax` etc
1. Provide your `estimation` in some imaginary points, I call them `elephants`
1. Don't hesitate to start discussion in comments section
    * for example it could be a question to mentor or some information to yourself

###### Labels
 
| Label         | Description    |
| --------------|:-------------:|
| `theory`      | Some media content which you have to read, watch or listen, usually they are items from `Theory` or `Addition` section |
| `exercise`    | Any exercise from `Practice` section |
| `workshop`    | Any cource or workshop which involves not only `passive consuming of information` but some actions from your side, like replicating of some actions. For example NodeSchool workshops|
| `question`    | Questions for some topic|
| `project`     | It's a special type of `Practise`, when you have to plan your project and split it into small sub-tasks|
| `bug`         | Defects in your exercise or project|
| `tech-dept`   | Bad design, `code smells` in your project|


###### Estimation

>My subjective recommendations

| Points         | Description    |
| --------------|:-------------:|
| 1     | Something trivial, it could takes you around one hour to make it done|<commit_msg>Update planing-and-time-management.md<commit_after># Planning and Time Management

**[<= Back](../01-communication/communication.md)**		*	*	*	**[Next =>](../03-few-simple-principles/few-simple-principles.md)**

## Table of Contents

### Theory

#### Planning

1. Before planning, trainees should create their issues according to `Issues Guide`
1. During planing team discus issues, corner cases and prepare plan for next iteration

##### Issues Guide

1. Provide meaningful, descriptive  name for the issue
    * NO any 'Exercise 1' or 'My article'
1. Issue shouldn't have empty description, at least link to the 'source' of the issue
    * usually 'sources' of the issue somewhere in our content, for example you always can make a link to any exercise or theory subsection
    * put whatever useful information you may found to solve the issue
1. Provide proper `label` for the issue
1. Provide proper `milestone`, usually they like `trainee-bootcamp`, `trainee-syntax` etc
1. Provide your `estimation` in some imaginary points, I call them `elephants`
1. Don't hesitate to start discussion in comments section
    * for example it could be a question to mentor or some information to yourself

###### Labels
 
| Label         | Description    |
| --------------|:-------------:|
| `theory`      | Some media content which you have to read, watch or listen, usually they are items from `Theory` or `Addition` section |
| `exercise`    | Any exercise from `Practice` section |
| `workshop`    | Any cource or workshop which involves not only `passive consuming of information` but some actions from your side, like replicating of some actions. For example NodeSchool workshops|
| `question`    | Questions for some topic|
| `project`     | It's a special type of `Practise`, when you have to plan your project and split it into small sub-tasks|
| `bug`         | Defects in your exercise or project|
| `tech-dept`   | Bad design, `code smells` in your project|
| `setup`       | Installation or configuration of some software, tool etc|


###### Estimation

>My subjective recommendations

| Points         | Description    |
| --------------|:-------------:|
| 1     | Something trivial, it could takes you around one hour to make it done|
{'fraction_non_alphanumeric': 0.11461187214611872, 'fraction_numerical': 0.006392694063926941, 'mean_word_length': 3.4118831822759317, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 7, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 1, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '260377', 'n_tokens_mistral': 1199, 'n_tokens_neox': 1121, 'n_words': 559}