"!open jira issues assigned to jquast" or "!github issues closed by jquast since yesterday"
Expand or integrate as necessary for whichever systems your team manages with.
Although some of my teammates found it intimidating to have only 0 or 1 results where others might have much more, it presses home the idea that your task progress should be made visible in these external systems.
As a team, storing your progress in a local notes file is anti-team. We should strive to allow any other team member to continue your work using only the information published to these systems.
"Ever stunned when your boss suddenly asked what you've done yesterday?"
workque todo --for=yesterday
# ~/notes/checklist-2016-07-18.md
# This will jump back to Friday's note if it's Monday today!
> worque todo --for yesterday --no-skip-weekend
Show HN guidelines: https://news.ycombinator.com/showhn.html
This is the big area where scrum goes awry. Defenders of scrum object, reasonably enough, to the claim that scrum leads to micromanagement of developers. The daily standup specifically isn't supposed to be a daily status report to your boss, complete with renewed application of deadline pressure. In fact, I remember reading once that in a scrum meeting, only those who are producing are even supposed to speak. It is specifically not supposed to take the form of a status update.
My main criticism of this defense of scrum is that I think scrum is somewhat prone to this kind of corruption. It may not be what is supposed to happen, but it's not a corruption out of left field either, it does seem to be an inherent risk. The presence of a daily standup, where developers can be put under a microscope and micromanaged under the guise of a developer friendly methodology, is just too tempting for bosses or other stakeholders who want to micromanage.
Hasn't come close to happening.