- How does a project that one person starts impact the work of others?
- What are the best trouble shooting methods for various problems?
- Who is the proper person to contact
- How should progress on solving the problem be shared with all impacted people
- Do the people you're talking to know what you're talking about?
- With so many individuals, and so many different projects in progress, it's important to make sure everyone in a meeting/email chain/whatever is up to date on the issue at hand and any history behind it.
- How does one avoid getting buried in jargon? We all have technical roles to varying degrees, but different areas of expertise.
- How can we improve documentation of conversations, decisions, technical rules and requirements?
- Who are different audiences, within and outside of our group, that might need to know this info?
- Is documentation useful/useable to all of these various audiences?
- Assess worst case scenario documentation- if all of us are abducted by aliens, could a new group of people figure out what we were doing and pick up where we left off?
Monday, January 5, 2009
Communication & documentation
One day-to-day logistical issue that I think we should spend a little time talking about is how such a large, physically separated, diverse group of people can best communicate with one another.