civilinfrastructureplatform:ciptestingmanagementjournal
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
civilinfrastructureplatform:ciptestingmanagementjournal [2017/08/24 16:22] Agustin Benito Bethencourt [Thursday 2017/08/24] |
— (current) | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== CIP Testing Project Journal 2017 ====== | ||
| - | ===== August ===== | ||
| - | |||
| - | ==== Thursday 2017/08/24 ==== | ||
| - | |||
| - | === [[agustin.benito@codethink.co.uk|Agustin Benito Bethencourt]] === | ||
| - | * Reverse ordering | ||
| - | * Initial entry | ||
| - | |||
| - | ====== Journal Ground Rules ====== | ||
| - | |||
| - | Project journal ground rules: | ||
| - | * In this case the entries will be structured first by month, then by date and finally by contributor. | ||
| - | * You decide what kind of information you should publish. | ||
| - | * Assuming that it is public, add what you think is : | ||
| - | * Relevant to you. | ||
| - | * Relevant to your peers. | ||
| - | * Relevant to those you interact with like, managers, other teams, Members, etc. | ||
| - | * The latest entries should be on top (ascending order). | ||
| - | * Be concise. | ||
| - | * Use links to tasks, commits, web pages, etc. as much as you can. This is not about duplicating the information but about providing context. | ||
| - | * Read the journal every day (ideally). Does it reflect the most relevant work you have done today? | ||
| - | * As guidance, include an entry every couple of hours of work and every time you accomplished something or a relevant event has taking place. | ||
| - | * Assume that your colleagues read the journal regularly. Add information of potential interest for them but remember that the main focus of the journal is the answer to the question: what am I doing? Write for yourself first. | ||
| - | * Agree with your colleagues on the tags to be used to provide further context to entries. Examples: | ||
| - | * Escalations: Green to solved or stalled issues, Amber for topics that require attention and Red for critical issues. | ||
| - | * User ID to call the attention of a colleague. | ||
| - | * #milestone to structure the information based on delivery timeline. | ||
| - | * Activity reports should be extracted from the journal so, ideally, no need to ping colleagues to create a report should be required. This is a sign of the correct usage of the journal. | ||
| - | * Standup meetings should not be any more about what I did (reporting) but about discussions. The time that a distributed team gets together is precious, do not waste it talking about something you can read ahead of the meeting. | ||
| - | * Do not add anything that you would not like others to know. Use common sense. | ||
| - | * The journal is not designed to substitute 1:1's, private reporting nor conversations. | ||
| - | |||
| - | --- //[[agustin.benito@codethink.co.uk|Agustin Benito Bethencourt]] 2017/08/24 | ||
civilinfrastructureplatform/ciptestingmanagementjournal.1503591722.txt.gz ยท Last modified: 2017/08/24 16:22 by Agustin Benito Bethencourt
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
