Use a predefined survey as an easy way to capture and assess pilot results the survey design should be based on the scenarios and features in your test plan. Ensure that you have an open feedback channel to track progress and measure outcomes. Your organization might choose to pilot all functionality at once, or use a gradual approach-for example, pilot collaboration first, then meetings, then chat and calling. Let the use cases you defined in Assess organizational change readiness guide your test plan. Group tasks together to offer real-world scenarios to your users, demonstrating relevancy to their daily activities. Design your test plan and feedback surveyįor a successful pilot experience, give your participants clearly defined tasks to complete along with a way for them to share their feedback. Check with those users to understand how they use Skype for Business today, then build out a test plan to verify that Teams can meet their current needs. When selecting your Teams pilot group participants, be sure to include top users of Skype for Business. Whichever scenarios you select, the pilot should extend to key people in IT, training, and your helpdesk, so you can thoroughly validate the solution while fully optimizing project management resources. An example of project-based work might be coordinating a product launch event with the marketing, training, public relations, and event planning teams. An example of a role-based project might be to use Teams with your sales organization to ensure that field reps can easily access the resources they need and share insights with other field members. A great place to start is asking your stakeholders and department managers for real projects that you can validate in Teams. Remember that Teams is optimized for teamwork, so be sure to select pilot participants not solely based on roles or personas but also based on their project and cross-team work. One of the most important tasks of pilot planning is thoughtful participant selection. Select your pilot participants and test scenarios You might even opt to run subsequent pilots as new Teams features are released per the roadmap. Start small, and add to your pilot as appropriate-whether by adding workloads or features, or additional users-making time to assess results and adjust your pilot as you iterate. You'll want to be sure to allow enough time to run the pilot and assess its impact: we recommend a minimum of 30 days. You should also ensure that you've included the right stakeholders for the duration of the project.
These goals should align with the scope of your broader project, as you documented when you defined your project scope, and will be used to inform your path forward after your pilot is over. Outline pilot logisticsĪ successful pilot has defined start and end dates, and clearly defined goals for measuring success. Use the sample pilot resources to help design your communications, test plan, and feedback survey.
#MAIL PILOT PATCH#
Just like you'd paint a small patch of color on a wall before painting the whole room, you'd test a broad rollout on a smaller scale by conducting a pilot to validate technical and user readiness, identify and mitigate issues, and help ensure a successful organization-wide implementation. Before enabling new technology across your organization, conduct a formal user pilot.
#MAIL PILOT UPGRADE#
This article is part of Deployment and Implementation stage of your upgrade journey, and shares insights for running an effective pilot.
0 kommentar(er)
