Commit cc0f1a18 authored by Sid Sijbrandij's avatar Sid Sijbrandij

Not four tags.

parent 4448e959
Pipeline #23729614 failed with stages
in 7 minutes and 50 seconds
......@@ -18,28 +18,28 @@ that works for you and your team.
1. Give your agenda document two headers: 'Key Results' and 'Agenda' that each contain a numbered list.
1. The Key Results for that report [from the OKRs](/okrs/) are the top of the document. This is the first thing to indicate that this is the focus and priority. Because we're a remote company there will be many small items on the agenda that in other environments would be handled throughout the week. It is important to periodically tell the report that the agenda should not be confused with the priorities. The Key Results is the only things that represents the priorities. The first business subject of every conversation should be the status of the top three priorities (the manager key results relevant to the report).
1. Review the Key Results every two weeks (every other meeting), it is very important that people don't confuse the agenda with priorities.
1. Use the following tags for each item on the agenda:
* TIMING
* `ISO DATE` (example: 2017-05-21 or 2017-05) - indicating when this item will be discussed next
1. Every item on the agenda starts with exactly one tag, the tag can come from one of four categories:
1. Timing
* `ISO DATE` (example: 2017-05-21 or 2017-05) - indicating when this item will be discussed next
* `RELEASE NUMBER` (example: 9.4 or 9.5) - alternative to `ISO DATE` to indicate when this item will be discussed next
* ACTION
1. Action
* `TODO` - report needs to set date of when this will be completed or just do the task, if we should discuss them report changes them to `DISCUSS`
* `DOTO` - manager needs to do something (case sensitive search for '`DO`' finds all `DOTO`'s and `DONE`'s)
* `DISCUSS` - cover in the next 1-1 meeting
* `REVIEW` - there is a Merge Request (MR) or document that can be approved, the MR should not be a Work In Progress (WIP)
* `HELP` - if you need help with anything.
* INFORMATION
1. Information
* `FYI` - informational, can be removed outside of the meeting by the person why did not put it on the agenda.
* `DONE` - to be removed by the person who put it on the agenda, only set this if any MR has been merged
* `MOVE` - if you want to move it outside of the agenda, for example an issue tracker.
* `DUPLICATE` - An item that is an outdated duplicate of another item on the agenda. To be removed similar to items marked as `DONE`.
* `WONT` - if you think this is no longer something that should be done.
* `THINK` - if the person who did not put it on the agenda wants time to think about it and discuss it next meeting.
* PERSONAL
1. Personal
* `FEEDBACK` - this is feedback about your performance (also means that all the other items are not performance feedback)
* `THANKS` - mostly used by the manager to praise the report, these should not require a follow-up action. There is a tendency to focus on issues and challenges. Do not forget to recognize accomplishments and success.
* `SORRY` - if you want to say sorry for something.
1. It is recommended to provide a section to list frequently & useful tags that helps facilitate ideas and perception triggers when a direct report (or their manager) fills out the 1-1 agenda.
1. It is recommended to provide a section to list frequently & useful tags that helps facilitate ideas and perception triggers when a direct report (or their manager) fills out the 1-1 agenda.
- This helps reassure that all these topic tags are readily available and encouraged to be used. This is especially important for `THANKS`, `SORRY` and `HELP` tags.
1. As specified above items are removed after being set to `DONE`. The 1-1 is one list that is continually modified. It is not a meeting agenda that is duplicated every week under a new date.
1. Add items to the end of the agenda. This is easier to do when using a numbered list.
......@@ -57,12 +57,12 @@ that works for you and your team.
```
6. 2017-07 Sid: Kubernetes wishlist email => Spoke with Job, he'll create the issues =>
6. 2017-07 Sid: Kubernetes wishlist email => Spoke with Job, he'll create the issues =>
Eliran to stay involved
7. Sid: Do a webinar with all cloud partners, all container schedulers, all config management
systems. => Eliran: Dimitrie might be interested in helping. Get the webinar without doing a lot
of integration. => Eliran: Starting with Puppet, Dimitrie said he didn't do any dev work for the
i2p demo so I am not sure he will be able to do the dev work required here. => Sid: Goal is not
7. Sid: Do a webinar with all cloud partners, all container schedulers, all config management
systems. => Eliran: Dimitrie might be interested in helping. Get the webinar without doing a lot
of integration. => Eliran: Starting with Puppet, Dimitrie said he didn't do any dev work for the
i2p demo so I am not sure he will be able to do the dev work required here. => Sid: Goal is not
to have dev work. Just combine their demo with our i2p.
```
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment