fuel-dev team mailing list archive
-
fuel-dev team
-
Mailing list archive
-
Message #00033
Format of syncups and other activities
Hi,
we (FuelWeb team + me) have been thinking about our syncup format and how
we can achieve a few goals:
1. Make our syncups more meaningful (clear in understanding for other
team members)
2. Shorten syncup duration
3. Make information that we discuss publicly available.
With these goals in mind,
we want to do the following week as evaluation with the following (FuelWeb
team only):
1. Syncup time is not changed for FuelWeb team: 1pm MSK time
2. It should be done in #fuel-dev IRC channel. Everyone in the timeframe
1pm - 1.10pm starts providing status update in standard format:
- what I was doing yesterday
- plans for today
- obstacles
3. Everyone reviews other team members status update and is allowed to
ask questions in IRC.
4. If it is obvious that the discussion will take too long, then follow
up meeting should be created (in Hangout or other communication tool)
5. Working language is English.
One more topic has been discussed, namely micro-techtalks which would team
members do periodically, may be even once a week, with the following
purposes:
1. Daily syncups are not informative enough to keep everyone up to date
with other team member's activities, so this issue should be addressed
somehow
2. Self-training: present the work you do
To address this, we want to try the following for FuelWeb team initially
with possible expansion to other Fuel subprojects:
1. Dmitry Pyzhov will talk to team members and identify first few
topics/engineers who will do such micro-techtalks
2. Schedule techtalks to morning PST time so US team can participate
3. No need to spend a lot of time for preparation, slides can be very
simple. It is more to discuss than to prepare a great techtalk.
4. Working language is English.
Besides micro-techtalks, we will do full formal techtalks on areas of Fuel,
leads of Fuel subprojects will identify who will talk about what.
Anyone is welcome to provide your opinion on this.
Thank you,
--
Mike Scherbakov