|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
||||
|
||||
|
Re: Incorporating Less Frequently Available Team Members
Progress charts work well in these areas. If there is a graphic display in the workshop that shows what has been done, what needs to be done, when it needs to be done, and who to talk to for details on each sub-project, it helps the members be more self-sufficient and raises overall accountability.
|
|
#2
|
||||
|
||||
|
Re: Incorporating Less Frequently Available Team Members
Quote:
Whether via email blasts or team web page, if your team members can keep current even when they can't be 'in the shop', then they won't have to spend their precious shop time catching up. One could argue this is important enough to merit assigning some team members to be responsible for the maintenance of such information. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Incorporating Our Code Into the Framework | Patrick Levy | NI LabVIEW | 1 | 11-02-2010 11:48 |
| Incorporating Tank Drive | Sauce | Programming | 3 | 25-01-2010 20:11 |
| QUESTION: SubVI's, and incorporating camera files | xc4life | NI LabVIEW | 2 | 04-02-2009 16:01 |
| Members per team vs members who actually work | Armando Gonzalez | General Forum | 40 | 09-11-2007 01:00 |
| Frequently misspelled words | Greg Ross | Chit-Chat | 16 | 22-12-2002 12:53 |