Documentation is necessary, but it's usually not sufficient for training your customers. Actually, it's usually sufficient for training only some of your customers. On our project, we had a few options. We could send a team member to train the customers at their site. We could hold online training sessions. We could develop some training materials and let the customers learn on their own. We could hope that they would learn from the User 's Guide or from each other. We chose to let one of our team members train the end users for the initial release. The obvious team member was Russell. Yes, he was the customer, but he was an integral part of our team from the beginning. He had been using the product. He had access to all of the material that the other team members had, and he knew the end users better than anyone else on the team. Russell was willing to do the training as long as someone was on call to help with any questions that he couldn't answer. He never had to use the lifeline, but he was reassured to have the option of using it. He spent about an hour training his team on how to set up a PSP Tools database and use the product. During the session they also decided to use individual databases (one per user), rather than one single group database. They wanted the database to be portable so they could use it on different computers. For version 1, users need to copy the database. In addition to this overhead, they need to keep the database contents consistent across computers. Gary uses PSP Tools on three different computers and when he forgets to copy the database, he needs to manually re-enter data. The feedback we got from the training session and our customers' subsequent product use resulted in more requirements for the next release. One of the high-priority changes we plan to implement in version 2 will give database access over the Internet, which will eliminate the need to maintain multiple copies of a database. There was an additional benefit to having Russell conduct the training. Adopting PSP Tools meant that the engineers' process was going to change. Russell was part of the organization ”in fact he managed the organization ”so he was able to use the session to get buy-in from the engineers about how they were going to adapt to the changes. This made the changed process their process, not one that was imposed on them. Training a Larger Group of CustomersWe admit that the circumstances of our project are rare. It is fair to ask how you can help your customers learn your product. In a more typical situation, a representative from the customer's organization isn't available to help train users, or more than one small, co-located set of customers need to learn your software. You need to balance the benefits of developing training materials and programs against the costs of not developing them. Consider the following points:
The size of the development project isn't a major issue here. The software you deliver, its complexity, and the value of training your customers are the major drivers when you consider the type and amount of training you will deliver. |