3 ms·

I've been thinking of writing a script that pulls down commits from <yesterday>, formats it "properly" and pipe them to SAY. "Wednesday, 24 April Fixed bug #4

by seivan 14y ago

I've been thinking of writing a script that pulls down commits from <yesterday>, formats it "properly" and pipe them to SAY. "Wednesday, 24 April Fixed bug #434, added protocols between user and tasks. " And if they _really_ want to know what I am going to work on or what issues I have. Please check my tracker. There are bugs, features and chores. And each of them has comments that describe any issues I might have run into or will. Problem solved.

vpeters25 14y ago
Actually in a well ran agile team, you should not need that as you should be focused working on only one user story. If you are fixing bugs then the story should be "x bugs related to foo feature" and your daily standup report should be "I fixed x bugs on foo, I have y to go, should be done today, no blockers"
- seivan 14y ago
  But there are a lot of things on the tracker that is in the icebox but assigned to me. Doesn't mean I am doing all at once :P
  - vpeters25 14y ago
    First, in agile teams, there is no assigning of tasks, each member takes the ones they feel like tackling. Agile in not optimal for maintenance or emergency production issues. These are dealt immediately and only mention in the daily stand up as a blocker stopping you from finish the task you actually intended to complete. They are not even added to the product/sprint backlogs. As a rule of thumb all user stories added to a sprint should take between half and 2 days to complete. If you have a whole bunch of small bug fixes, group them together so they fit in that time-frame (i.e. all UI bugs in page foo). Otherwise you end up polluting the backlog with hundredths of little things and turning your planning meetings into overwhelming nightmares. Just think about it: if everybody in the team is working on only one or two tasks every day, the daily stand up will take each member about 30 seconds and the whole meeting less than 5.
nahname 14y ago
Enjoy! standup = log --graph --decorate --oneline --author="YOURNAMEHERE" --since="yesterday"

by seivan 14y ago

vpeters25 14y ago

Actually in a well ran agile team, you should not need that as you should be focused working on only one user story. If you are fixing bugs then the story should be "x bugs related to foo feature" and your daily standup report should be "I fixed x bugs on foo, I have y to go, should be done today, no blockers"

seivan 14y ago
But there are a lot of things on the tracker that is in the icebox but assigned to me. Doesn't mean I am doing all at once :P
- vpeters25 14y ago
  First, in agile teams, there is no assigning of tasks, each member takes the ones they feel like tackling. Agile in not optimal for maintenance or emergency production issues. These are dealt immediately and only mention in the daily stand up as a blocker stopping you from finish the task you actually intended to complete. They are not even added to the product/sprint backlogs. As a rule of thumb all user stories added to a sprint should take between half and 2 days to complete. If you have a whole bunch of small bug fixes, group them together so they fit in that time-frame (i.e. all UI bugs in page foo). Otherwise you end up polluting the backlog with hundredths of little things and turning your planning meetings into overwhelming nightmares. Just think about it: if everybody in the team is working on only one or two tasks every day, the daily stand up will take each member about 30 seconds and the whole meeting less than 5.

nahname 14y ago

Enjoy! standup = log --graph --decorate --oneline --author="YOURNAMEHERE" --since="yesterday"