projectdoc Toolbox

Provides doctypes to organize the developer's work by the employment of a diary. Take you personal planning and professional records to the next level!

Overview

The Doctypes for Developer Diaries help software developers to plan their working days and weeks besides the work they do with their team using Confluence and the projectdoc Toolbox.

A diary is typically created in the developer's personal space. The diary is organized in years and days. Once per week the developer may run a personal retrospective.

After you created you diary on a page within a space, add a page for a single year. You may add some strategic plans on this page. For every day of your working life, add a new page. On this page you'll add notes on what you did and especially why you did it and your results and insights. The day of a diary is recorded as a flow of events. While the page create with a Confluence blueprint wizard may seem like a form to fill out, it is not. Typically you add text to the description and links to references or resources section. Adding tags to support finding the information is also optional, but often very handy.

At the end of each day, you may run a retrospective to find things that run well (and therefore should be repeated) and things that run wild (and therefore should be considered as possibility for improvement.

After a work week you may run a retrospective for this week.

Please note that every information you add to the diary is optional. This is not meant as a collection of forms to be filled out and passed to your boss.

Instead, this is a personal diary where you note valuable information you want to refer to later:

Found some interesting information about a subject? Paste some links and add some notes so that you can come back later and continue!
Lost in day-to-day work and lost the whole picture? Try to plan the important topics of your week and then check at the end how far you have come. Try to investigate the problems you have encountered to get your things done. Find a solution: ask yourself, your team members, your agile master!
Value your work and get a tool to help you be more business focussed. Make your achievements visible to yourself and let your team mates benefit from you insights and results!

The developer diary is for developers. If you are looking for a basic structure for your team space, please refer to Doctypes for Agile Planning.

English and German by Default

All doctype add-ons are available in English and German language (except for the V-Modell XT add-on for which only German is supported).

For more information on this topic please refer to Localization.

Install Developer Diary for projectdoc!

Install the Developer Diary for projectdoc now and for free via

Get started with your developer diary:

Create a Diary in a Personal Space!

Developer Diaries

Fork the projectdoc Developer Diaries on Bitbucket!

Install additional Doctypes!

Install additional Doctype Add-ons now and for free via

Here is an example how the page for a diary year looks like:

Events are organized in day segments. An event is created with a blueprint wizard and is typically the child page of the day page.

The properties demand only a name and a short description.

Add more information to the description section, links go to references or resources.

Attached child documents will automatically show up in "Subordinate Events" or "Attachments".

To get started with your developer diary quickly, please refer to Create a Diary in a Personal Space!

Prerequisites

The projectdoc Developer Diaries requires the projectdoc Toolbox to be installed. The projectdoc Toolbox has a commercial license.

The add-on also uses blueprints from the Core Doctypes for projectdoc (like Role or Stakeholder). This add-on is available on the Atlassian Marketplace for free.

Please install the following add-ons on your Atlassian Confluence server:

1. Install projectdoc Toolbox

Install the projectdoc Toolbox now

2. Install Core Doctypes!

Install the Core doctype add-on now and for free

List of Doctypes for Software Development

The following doctypes help to run your developer diary.

#	Name	Short Description	Categories
1	Annual Vision	Describe your vision for one year. You plan will help you stay focussed to accomplish your goals.	/ Work / Strategy
2	Annual Vision Type	Categories for annual visions.	/ Work / Reference
3	Asset	Explain an asset of your work. Add this document to a day in your diary.	/ Work / Unit
4	Asset Type	Categories for assets.	/ Work / Reference
5	Cheat	A brief solution to a problem.	/ Work / Reference
6	Cheat Type	Categories for cheats.	/ Work / Reference
7	Day	Store relevant information discovered today in your developer diary.	/ Work / Journal
8	Day Type	Categories for days.	/ Work / Reference
9	Diary	The homepage of a developer's daily diary pages. Consider to add your diary to your personal space!	/ Work / Journal
10	Diary Type	Categories for diaries.	/ Work / Reference
11	Event	Associated an event with a day. A event is a collection of associated information for your later reference. Information may further be organized by subject, tags, categories, and audience.	/ Work / Journal
12	Event Type	Categories for events.	/ Work / Reference
13	Month	Plan and run a retrospective for your month of work.	/ Work / Journal
14	Month Type	Categories for months.	/ Work / Reference
15	Todo	Add a todo note to your developer diary.	/ Work / Unit
16	Todo Type	Categories for todos.	/ Work / Reference
17	Vision	Describe your vision for your career.	/ Work / Strategy
18	Vision Type	Categories for visions.	/ Work / Reference
19	Week	Plan and run a retrospective for your week of work.	/ Work / Journal
20	Week Type	Categories for weeks.	/ Work / Reference
21	Year	Create a year in your Diary.	/ Work / Journal
22	Year Type	Categories for years.	/ Work / Reference

Related Macros

The following macros are provided by this add-on.

Day Rating: Allows a user to select a rating for a day.

Resources

Doctypes for Agile Planning: Provides doctypes to collborate with your team. Run iterations and record discoveries that may be of interest at the end of the iteration or for even later reference. Quick notes are more easily added as records to the team's space than to the official documentation tree. Defer the talk to the documentation architect to the end of the iteration (if the discovery is still of interest).
Doctypes for Teamwork: Provides doctypes to define the checklists, processes, patterns, tools, and rules your team agrees upon. Writing them down makes them accessible for anyone - especially for new team members. Keep these documents short and to the point!
Doctypes: Doctypes define properties and sections for documents. They are essentially Confluence Blueprints that help to create pages in your wiki based on templates.
Macros: List of macros provided by the projectdoc Toolbox.

Space shortcuts

Page tree

Docs

Support

Free Blueprints

Tooling for Blueprints

Free Extensions

Spaces

Plugins for Maven

Incubator

Libraries for Java

Incubator

Add-ons for Confluence

Tools

Support

Team

Legal

Overview

Prerequisites

List of Doctypes for Software Development

Related Macros

Related Topics

Resources

About

Keep up-to-date!

Powered by