1) At my job we have a Word Template to fill in and send to our boss every Friday. At a previous job we just created an email answering: What did you work on this week? What are you planning on working on next week.
Yep, daily, and then we recite the same thing at our daily morning standup.
Don't think I'll share a real one, they're probably proprietary and no upside for me in that. But I can give you a fake one.
Below is the top of my file. The last entry, the dated one, gets pushed down every day under a fresh one, and I update it as I go during the day.
The markup syntax is vimwiki http://www.vim.org/scripts/script.php?script_id=2226, but it could be any markup. Years ago I used to use markup something like this without transforming it, before there was anything like markdown or reST.
At the end of the day I run Vimwiki2HTML from within vim, and my daily status html page is updated; it's just a local page, I don't serve it. I copy today's entry from that and email my boss. Ten years ago I would have just copied the plain text from the vim file.
Every once in awhile I email the ever growing file to myself at home.
Scripts that generate the daily template after the example.
=Status=
==Long term ToDo==
* Some long term thing that currently doesn't have any tasks:
* Some slightly more interesting long term thing:
* practice elocution
* study needed inventions
* study electricity
==Immediate ToDo==
* Follow up on that thing by end of the week.
* See if that other thing is ready.
==2013.03.22 Friday==
===Today===
* Wrote test ABC.
* Reviewed test BCD.
* Passed test CDE.
* Failed test DEF.
* Wrote bug ticket 234 describing test DEF failure.
* Cleared ticket 345.
===Tomorrow===
* Write test XYZ
* Run tests MNO, PQR.
===Roadblocks===
* My cube mate keeps looking at me.
1) We make "progress reports" by updating our own tasks assigned to us within the Sprint. The "boss/manager" just takes a peek at burn-down and other charts. For more details he just takes a peek at the latest updates on the comments.
2) Daily, I take 5 minutes to write a simple comment on the task assigned to me. Daily updates are better than weekly ones, weekly comments and paragraph type progress reports tend to be too abstract for it to have actual meaning. Sometimes paragraph-type reports are too verbose for a decision maker to make decisions upon. We let the charts speak for themselves in terms of weekly overviews.
If a software development team uses docs and text files to submit reports, 1) the development process is still in its infancy or 2) no budget is alotted for project management tools because quality software development is not a priority for the company.
11 comments
[ 180 ms ] story [ 624 ms ] thread2) We had to submit these reports weekly.
Don't think I'll share a real one, they're probably proprietary and no upside for me in that. But I can give you a fake one.
Below is the top of my file. The last entry, the dated one, gets pushed down every day under a fresh one, and I update it as I go during the day.
The markup syntax is vimwiki http://www.vim.org/scripts/script.php?script_id=2226, but it could be any markup. Years ago I used to use markup something like this without transforming it, before there was anything like markdown or reST.
At the end of the day I run Vimwiki2HTML from within vim, and my daily status html page is updated; it's just a local page, I don't serve it. I copy today's entry from that and email my boss. Ten years ago I would have just copied the plain text from the vim file.
Every once in awhile I email the ever growing file to myself at home.
Scripts that generate the daily template after the example.
This generates a date: And this generates a daily entry skeleton: Then in vim, put your cursor above the previous day's entry, and: which creates a new blank entry with one empty bullet per section.I do this maybe once a week if he's not at the office and maybe 2-3 times a week if he is at the office. (It really just depends on his mood.)
In person it's usually a 2-minute meeting where we clarify which projects are done, which are priorities, etc.
...and sometimes the 2-minute update meetings turn into 2-hour planning meetings.
1) We make "progress reports" by updating our own tasks assigned to us within the Sprint. The "boss/manager" just takes a peek at burn-down and other charts. For more details he just takes a peek at the latest updates on the comments.
2) Daily, I take 5 minutes to write a simple comment on the task assigned to me. Daily updates are better than weekly ones, weekly comments and paragraph type progress reports tend to be too abstract for it to have actual meaning. Sometimes paragraph-type reports are too verbose for a decision maker to make decisions upon. We let the charts speak for themselves in terms of weekly overviews.
If a software development team uses docs and text files to submit reports, 1) the development process is still in its infancy or 2) no budget is alotted for project management tools because quality software development is not a priority for the company.