Weekly report on staff activities
Tom, Andrei, and Jörg (and cc: to l.t.n.maildev),
On the Thunderbird Council, we've had discussions on how we should be
managing technical staff and related technical work. One issue is
visibility of the work that staff are doing. Although you (the three
staff receiving this message directly) have been updating a status in
the bi-weekly meeting notes, that has a fairly narrow distribution, and
bi-weekly is not really often enough.
What we would like to see is a weekly email sent to
maildev@lists.thunderbird.net, that answers these three questions
(typical of a daily report in a Scrum management system):
- What did I accomplish in the last week?
- What do I plan to work on during the next week?
- What are the obstacles or impediments that are preventing me from
making progress?
As with a daily Scrum update, the goal is something fairly short that
will let others get a sense for what you are up to. You are welcome to
copy and paste the text that you might prepare for the bi-weekly meeting
notes (though we would like this weekly to maildev). There is no need
for a comprehensive list of each bug or patch you are working on, just a
general sense of where your efforts have been and are going.
One of the goals of the l.t.n.maildev list is to try to get technical
discussions and decisions away from the by-default private Thunderbird
Council list, and onto this public l.t.n.maildev list. That also means
that the general task of managing what work should be done should fall
to this list. BenB helpfully worded this division as follows: "the TB
council sets overall goals for the project. That may include tasks for
employees, and these tasks would be high priority. But in day to day
work, eng council would set most practical tasks."
We're still trying to figure out the best way to manage all of this with
our mix of volunteers and staff. Hopefully this improve things without
introducing excessive process effort, but we'll probably have to do more
tweaking as we learn what works or not.
R Kent James
I think this is fine, and I'm happy about it. I realize that the status
meeting is not attended by many people who should get updates, but it's
unpleasant to do multiple status updates to multiple people/lists/venues
at the same time, and it seemed like the most public venue we had available.
Since maildev is public, I can just make my reports there and then for
the status meeting simply link to them directly, and the same for anyone
else who asks questions about it!
On 2017-07-26 2:14 PM, R Kent James wrote:
Tom, Andrei, and Jörg (and cc: to l.t.n.maildev),
On the Thunderbird Council, we've had discussions on how we should be
managing technical staff and related technical work. One issue is
visibility of the work that staff are doing. Although you (the three
staff receiving this message directly) have been updating a status in
the bi-weekly meeting notes, that has a fairly narrow distribution,
and bi-weekly is not really often enough.
What we would like to see is a weekly email sent to
maildev@lists.thunderbird.net, that answers these three questions
(typical of a daily report in a Scrum management system):
- What did I accomplish in the last week?
- What do I plan to work on during the next week?
- What are the obstacles or impediments that are preventing me from
making progress?
As with a daily Scrum update, the goal is something fairly short that
will let others get a sense for what you are up to. You are welcome to
copy and paste the text that you might prepare for the bi-weekly
meeting notes (though we would like this weekly to maildev). There is
no need for a comprehensive list of each bug or patch you are working
on, just a general sense of where your efforts have been and are going.
One of the goals of the l.t.n.maildev list is to try to get technical
discussions and decisions away from the by-default private Thunderbird
Council list, and onto this public l.t.n.maildev list. That also means
that the general task of managing what work should be done should fall
to this list. BenB helpfully worded this division as follows: "the TB
council sets overall goals for the project. That may include tasks for
employees, and these tasks would be high priority. But in day to day
work, eng council would set most practical tasks."
We're still trying to figure out the best way to manage all of this
with our mix of volunteers and staff. Hopefully this improve things
without introducing excessive process effort, but we'll probably have
to do more tweaking as we learn what works or not.
R Kent James
+1
Just to emphasize this part :
There is no need for a comprehensive list of each bug or patch you are working on, just a general sense of where your efforts have been and are going.
A mere lost of all bugs is not going to be helpful, it will have too much noise. Please include only the tasks that you spent most time on (and roughly how much, in ~2h increments), and those that have a big impact on others, even if they were fast. Please also include tasks that are not bug fixes.
Ben
Am 26. Juli 2017 23:14:49 MESZ schrieb R Kent James via Maildev maildev@lists.thunderbird.net:
Tom, Andrei, and Jörg (and cc: to l.t.n.maildev),
On the Thunderbird Council, we've had discussions on how we should be
managing technical staff and related technical work. One issue is
visibility of the work that staff are doing. Although you (the three
staff receiving this message directly) have been updating a status in
the bi-weekly meeting notes, that has a fairly narrow distribution, and
bi-weekly is not really often enough.
What we would like to see is a weekly email sent to
maildev@lists.thunderbird.net, that answers these three questions
(typical of a daily report in a Scrum management system):
- What did I accomplish in the last week?
- What do I plan to work on during the next week?
- What are the obstacles or impediments that are preventing me from
making progress?
As with a daily Scrum update, the goal is something fairly short that
will let others get a sense for what you are up to. You are welcome to
copy and paste the text that you might prepare for the bi-weekly
meeting
notes (though we would like this weekly to maildev). There is no need
for a comprehensive list of each bug or patch you are working on, just
a
general sense of where your efforts have been and are going.
One of the goals of the l.t.n.maildev list is to try to get technical
discussions and decisions away from the by-default private Thunderbird
Council list, and onto this public l.t.n.maildev list. That also means
that the general task of managing what work should be done should fall
to this list. BenB helpfully worded this division as follows: "the TB
council sets overall goals for the project. That may include tasks for
employees, and these tasks would be high priority. But in day to day
work, eng council would set most practical tasks."
We're still trying to figure out the best way to manage all of this
with
our mix of volunteers and staff. Hopefully this improve things without
introducing excessive process effort, but we'll probably have to do
more
tweaking as we learn what works or not.
R Kent James
Maildev mailing list
Maildev@lists.thunderbird.net
http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net
--
This email was sent from my phone. Please excuse the brevity
Makes sense
Am 26. Juli 2017 23:24:26 MESZ schrieb Andrei Hajdukewycz via Maildev maildev@lists.thunderbird.net:
I think this is fine, and I'm happy about it. I realize that the status
meeting is not attended by many people who should get updates, but it's
unpleasant to do multiple status updates to multiple
people/lists/venues
at the same time, and it seemed like the most public venue we had
available.
Since maildev is public, I can just make my reports there and then for
the status meeting simply link to them directly, and the same for
anyone
else who asks questions about it!
On 2017-07-26 2:14 PM, R Kent James wrote:
Tom, Andrei, and Jörg (and cc: to l.t.n.maildev),
On the Thunderbird Council, we've had discussions on how we should be
managing technical staff and related technical work. One issue is
visibility of the work that staff are doing. Although you (the three
staff receiving this message directly) have been updating a status in
the bi-weekly meeting notes, that has a fairly narrow distribution,
and bi-weekly is not really often enough.
What we would like to see is a weekly email sent to
maildev@lists.thunderbird.net, that answers these three questions
(typical of a daily report in a Scrum management system):
- What did I accomplish in the last week?
- What do I plan to work on during the next week?
- What are the obstacles or impediments that are preventing me from
making progress?
As with a daily Scrum update, the goal is something fairly short that
will let others get a sense for what you are up to. You are welcome
to
copy and paste the text that you might prepare for the bi-weekly
meeting notes (though we would like this weekly to maildev). There is
no need for a comprehensive list of each bug or patch you are working
on, just a general sense of where your efforts have been and are
going.
One of the goals of the l.t.n.maildev list is to try to get technical
discussions and decisions away from the by-default private
Thunderbird
Council list, and onto this public l.t.n.maildev list. That also
means
that the general task of managing what work should be done should
fall
to this list. BenB helpfully worded this division as follows: "the TB
council sets overall goals for the project. That may include tasks
for
employees, and these tasks would be high priority. But in day to day
work, eng council would set most practical tasks."
We're still trying to figure out the best way to manage all of this
with our mix of volunteers and staff. Hopefully this improve things
without introducing excessive process effort, but we'll probably have
to do more tweaking as we learn what works or not.
R Kent James
--
This email was sent from my phone. Please excuse the brevity
Also, the second question is just as important: what are you going to do next? Please compose it with those same criteria: a) most effort, and b) most effect and c) unusual tasks
All 3 questions are important and the thought you put in them are well worth the time, e.g. 15 min per day.
Am 27. Juli 2017 01:00:59 MESZ schrieb Ben Bucksch via Maildev maildev@lists.thunderbird.net:
+1
Just to emphasize this part :
There is no need for a comprehensive list of each bug or patch you
are working on, just a general sense of where your efforts have been
and are going.
A mere lost of all bugs is not going to be helpful, it will have too
much noise. Please include only the tasks that you spent most time on
(and roughly how much, in ~2h increments), and those that have a big
impact on others, even if they were fast. Please also include tasks
that are not bug fixes.
Ben
Am 26. Juli 2017 23:14:49 MESZ schrieb R Kent James via Maildev
maildev@lists.thunderbird.net:
Tom, Andrei, and Jörg (and cc: to l.t.n.maildev),
On the Thunderbird Council, we've had discussions on how we should be
managing technical staff and related technical work. One issue is
visibility of the work that staff are doing. Although you (the three
staff receiving this message directly) have been updating a status in
the bi-weekly meeting notes, that has a fairly narrow distribution,
and
bi-weekly is not really often enough.
What we would like to see is a weekly email sent to
maildev@lists.thunderbird.net, that answers these three questions
(typical of a daily report in a Scrum management system):
- What did I accomplish in the last week?
- What do I plan to work on during the next week?
- What are the obstacles or impediments that are preventing me from
making progress?
As with a daily Scrum update, the goal is something fairly short that
will let others get a sense for what you are up to. You are welcome to
copy and paste the text that you might prepare for the bi-weekly
meeting
notes (though we would like this weekly to maildev). There is no need
for a comprehensive list of each bug or patch you are working on, just
a
general sense of where your efforts have been and are going.
One of the goals of the l.t.n.maildev list is to try to get technical
discussions and decisions away from the by-default private Thunderbird
Council list, and onto this public l.t.n.maildev list. That also means
that the general task of managing what work should be done should fall
to this list. BenB helpfully worded this division as follows: "the TB
council sets overall goals for the project. That may include tasks for
employees, and these tasks would be high priority. But in day to day
work, eng council would set most practical tasks."
We're still trying to figure out the best way to manage all of this
with
our mix of volunteers and staff. Hopefully this improve things without
introducing excessive process effort, but we'll probably have to do
more
tweaking as we learn what works or not.
R Kent James
Maildev mailing list
Maildev@lists.thunderbird.net
http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net
--
This email was sent from my phone. Please excuse the brevity
--
This email was sent from my phone. Please excuse the brevity