How do you save information about the status of the projects you are working on?

Question

Let me understand what the status of the project is:

• Any information that should be remembered or recorded, and then retrieved when resuming work on a project (for example, the next morning, when he comes to work, or in the evening, when he starts working on a side project).

• For example, when you open a project / solution, how, where and in what form you save information about what to do next, contextual information of the current task to resume work on it. Project / task management systems are not designed to handle things at this level of detail, so I cannot use some existing as a base for my projects. I tried to host software like FreeMind (mind mapping) or ThinkingRock (Getting Things Done), but it just doesn't work.

• What I need (and I think that many conscious developers will be happy with such a system) is what can be used to store information in a form similar to a magazine. I have read several articles on developer / programmer magazines and the general idea of ​​an engineering magazine, but since then I am still not able to implement what suits my needs.

• The system can be used not only for clean development, but also for more academic projects in which more R&D is involved, although there are commercial projects with even more R&D (reading and trying from several books, articles and articles).

• Information on the progress of the project must somehow be recorded in order to look for links, code, arguments for certain decisions, notes, etc.

Do you know any software that can do the job ... or should I start writing myself.

Answer 1

I use TiddlyWiki , which is a useful personal wiki. I use it as a big box of notecards, with cross-references and hyperlinks between sections.

As noted by several people, the most complex part of any of these systems maintains its relevance.

Answer 2

try Notepad.exe, one log file for each project. Or use Word. Or a wiki, or something else.

the key is not to find fantastic software, the key is self-discipline to keep the journal up to date!

Answer 3

I have the same requirements, and I switched from a text file to Google Docs. This gives me several advantages:

• I can access it from anywhere
• Easy formatting

I have one file named todo and other files for my notes, which are usually named according to the naming convention, for example:

• product.name.ideas
• product.name.todo
• product.name.questions

In my todo file, I group by date (when I need to work or finish something) and prefix them with a code of 3-4 characters to indicate who is “who”. For example:

. EXPECTATIONS
, PROD1: code view

.MONDAY
, HOME: Go to the bank
HOME: Send invoices
, PROD2: recording requirements

.TUESDAY
, PROD2: Overview with the team

I plan only one week, and also leave sections, such as "Later", "Much later", "I wish" at the end.

Answer 4

I just use MS Word as a journal and, if necessary, insert links to other files. Most of the time that with a laptop is enough to let me pick up a project by reading the last notes.

Answer 5

I find that a managed notebook and pen work great. I often comment on fields with pictograms indicating priority or notes for later observation. I think the main thing is to be consistent.

Answer 6

Depends on the project and whether notes should be shared. I save my personal notes with a pen and paper. Quickly and easily add illustrations and links.

General remarks and frequently asked questions about tribal knowledge I prefer to use a wiki or development blog. The blog format is great for providing historical and (tagged) links.

Answer 7

I usually try to complete a task before heading home. If I cannot do this, a good method to remember is to create a failed test for the next thing you should do.

The big things that I point out on a wiki project or install TODO comments in my code (and use tools that find them).

Answer 8

I agree with the general consensus so far: keep it simple and focus on your disciplined use. I like to use a stand-alone HTML file, because it is plain text, but allows you to use real links, various lists and trivial formatting. This is great for a ToDo list, ReadMe, a list of links, ideas, etc.

For an integrated team tool, I prefer a very lightweight wiki. I am targeting Trac ( http://trac.edgewall.org/ ), which is a free, free, open source project that integrates wiki, source management and problem tracking, perfect marriage.

Answer 9

I use TodoList for tracking during design and actual development. It is a simple hierarchical to-do list, but also offers basic project management features (i.e. setting deadlines, priorities, and categories and tracking progress for tasks). Files are XML and can be easily processed and versioned, and it includes some basic collaboration features (although I haven't used this yet).

When collecting a large amount of information, especially if it is primarily text, tables or images, before actual development or brainstorming or just recording thoughts, I actually use Microsoft OneNote, although I would not install it just for that. But since it is included in Office, which is installed on all computers in my company, I use it because I am quite comfortable with it. I use OneNote only for myself, although, like, well, a notebook.

Oh, and then, for information that is actually not for one project, but rather for reuse, we certainly have a Wiki, although it’s sometimes difficult to convince people that they really use it (“what, wiki? I just call you when I need this information! "). Sigh.

Answer 10

If you need to share information, the Wiki really works for this kind of “tribal knowledge” information that you want to remember.

If this is only for you, then the other answers given here work very well.