...
- daily vs weekly vs bi-weekly meetings
- rotating who has responsibility for the agenda
- IM
- Daptiv
- Jira
- RT
- Tech Time
- Phone
*Need to have some minimum standards of how and when we use these tools, expectations for basic structure and organization (Daptiv, Jira and Wiki). Pat wants this as an action item - to document recommendation.
Next step: We will apply this to the hypothetical below and see what works. We will also decide if we need to narrow the scope to vertical communication only.
- based on that discussion, we will put together a draft recommendation for the group to review and comment on
Next meeting: Friday June 20, 2008 at 2pm Downtown Crossing.
Hypothetical for Thought
Team X has been working on a login application and the big release coming up. Many of the company's applications will integrate with this service and be dependent on it. The Team makes the decision that the product needs to be "rock solid", because if it goes down, so do all the apps that are using it. The company as a whole does not do any standard quality assurance, and the Team believes that this is an issue. They feel that due diligence includes QA for this service as well as other products being developed across the organization. They want to begin investigating tools since testing would need to begin asap. How should their needs and concerns be communicated? How should the tool selection be conducted and a decision made?
...