I've solved this issue with a chat bot in the past, answering phrases such as,
"!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.
you realize that's exactly the info you're supposed to have on hand for a standup in scrum or any other Scrum-like agile methodology. What you accomplished yesterday, what you're going to be working on today, and what obstacles you need help with.
Absolutely accurate, but you did leave out the part about "when your boss asks you," which I think is what gave the OP a shudder.
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.
I wish I could get my management and team to even adopt so much as a weekly retrospective like this. I've been clamoring for it, begging for it, showing how a lack of a methodology to GSD is having a real impact.
The selling point in the readme is to share to people what you're working on and what you've been doing (like your boss), but this seems like just a mini Jira. I guess it works if there's no formal "stuff that needs to get done" list.
> If you're kind of nerd and you have no life. You would rather work over the weekend than hanging out with folks, so you should enable the hardcore mode which will stop skipping weekend for you.
"!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.