The proof-of-concept of a method should be done using the implementation environment you plan to use to author the actual method. That way you can test the technical feasibility of your architectural ideas in the actual implementation environment.

The following are some things that you may want to test out:

• Your proposed library structure, including the types of plug-ins you are considering creating, their relationships and the types of configurations you are considering creating.
• Strategy for defining navigation views, identifying any common navigation elements that you may want to share between views and configurations
• Strategy for handling copyrights and release information
• and so on.

As you develop the proof-of-concept, it is important to document any issues and risks that you encounter so that these can be addressed when more formally defining the method.

When developing an proof-of-concept for a Practice Framework, be sure to include a set of Practices, some interfaces between those practices (e.g., Work Product Slots), as well as some configurations representing the Practice Configurations those practices will be included in. You may also want to take into consideration any defined plug-in types and/or configuration types. For more information, see Concept: Practice Library Plug-In Types and Concept: Practice Library Configuration Types.