...
Next meeting: June 13, 2008 3pm 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 so 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?
Ideas on what to include in a communication strategy:
- objectives
- target audience or stakeholders
- message you want to convey
- tools (existing or new)
- resources you need
- time line
- lessons learned