The document discusses developing a testing strategy and provides suggestions for how to approach it. It recommends establishing a shared vision and goals for the test team, considering the team's makeup and skills, and assessing the current and desired states of testing. It also suggests creating a plan to transition from the current to the desired state, implementing the plan, reviewing progress, and adjusting as needed.

1. Strategy ThoughtsWe’ll get started soon….. Alan Page Microsoft Lync

2. Before we Begin Thanks for hanging out with me Feel free to “play” with the product (web client or attendee console) during the presentation Depending on attendance rate, I’ll probably start with everyone muted, but keep an eye on the chat window for questions The presentation will be recorded (but dunno if I’ll share it)

3. A little more background

4. General thoughts on strategy Shared vision of role and objective of test team Manage test process Manage risk Set goals for the team

5. Consider Context Team Makeup Team Size Current Skills Desired Skills Other Goals

7. Assess What does testing look like now? What will be different? What else will change? Can the team change?

8. Getting From Here to There Current State Significant false positives in test code Conflicting ideas on what’s most important Tester “toolbox” missing “foo” Something else Desired State Completely trustworthy tests Complete alignment on what is important (and what is not important) Tester “toolbox” includes full usage of “foo” Something else better

9. Here There

10. Next Steps Just do it™ Monitor Review Adjust Show results

11. Questions / Discussion

12. Photo Credits Jscreationzs Salvatore Vuono luigidiamanti freedigitalphotos.net