Phase 2: Ideation and Proposal
Project Initiation Document, Selection for Development and Testing
Building upon the Project Justification Document(s), the project proposal or Project Initiation Document is a request for the Enactus team to devote resources toward the focused development and testing of the proposed project in preparation for full implementation. The document should provide a full report of development to-date and include research and other supporting elements. While every project is different, and projects of greater complexity will often require more documentation, there are several elements which will be required of all project proposals.
Often, it is useful to first map out the project onto a logic model before beginning the full Project Initiation Document. A Logic Model provides a means of viewing the project inputs, outputs, and goals as a series of if-->then statements (i.e. inputs → activities → outputs → outcomes → impact.) If we input certain resources, certain activities can be implemented, or vice-versa, if we wish to engage in certain activities in the project, certain inputs are required. See Figure 1a for an example.
The need (i.e. high unemployment in Riverside County.
Resources needed to implement the project (Funds, R&D, Team Members, Equipment, Materials)
What we do in the project. Specific tasks. (i.e. skills training, resume workshops, campaign to attract new businesses to Riverside)
Measurable evidence of implementation. The product or result of project activities. (i.e. 500 people trained)
The specific objectives achieved for the target audience (i.e. 500 jobs created and filled, 200% increase in annual income for participants)
2% decrease in county unemployment rates
While the Project Justification Document focuses primarily on the “What?” and “Why?” of the potential project, the Project Initiation Document focuses on the whole picture, adding the “Who, How, and When?” of the project. The following section outlines the common elements of a Project Initiation Document in this manner.
Project Initiation Document
Section 1: What?
This section describes the main objective of the project, what it is intended to achieve. It includes a full situation analysis and clearly defines the project. Generally, this section will include the following:
Discuss the situation, why the proposed project is a viable solution, and highlight the development thus far.
Section 2: Why?
In the previous section, you identified why the project was needed by the target area/audience, but from a Enactus standpoint, why should we devote time and resources to this particular project? How does it align with the overall vision and objectives of the Enactus team? Here you make the business case as to why your proposed project should be selected by the team over alternatives.
Section 3: Who?
Even a perfect solution to an identified need can completely fail when not properly organized and managed. In any project, particularly long-term ones, creating specific roles within the team allows for increased efficiency and accountability and decreases the issues and confusion arising from duplication of roles. This is both the case for work within teams as well as with external partners.
Section 4: How and When?
This section describes how the project will be implemented. It will later be used as a guide for implementation in the project. Think of it as your initial plan which could be used to begin immediate implementation of the project if needed. So again, design this section as necessary for a different project manager to still be able to implement the project. You may wish to organize this plan into stages or phases for longer-term projects. This section will commonly include:
Section 5: Supporting Documents
As appendices, include any supporting documents or additional information relevant to the development and/or implementation of the project. For example, if you utilized the strategic tools of SWOT Analysis, and Porter’s Five Forces to assess a situation during the initial research phase, include such documentation. If you have a letter from a potential partner expressing interest in supporting the potential project, include it as an appendix. As the Project Justification and Initiation Documents will be build upon into an entire portfolio in the future, any supporting documents or artifacts are valuable.
Selection for Development and Testing
Upon its completion, the Project Initiation Document will be reviewed to determine if Enactus resources will be tasked to support further planning and development of the project in preparation for its potential implementation. As each project is different, funded development and testing may be needed to more accurately complete the information needed in the Project Initiation Document itself. For this reason, projects selected based upon the Project Initiation Document will still undergo this additional development before full implementation. Additionally for this reason, not all Project Initiation Documents can be completed as fully as described in the previous section. This will be taken into consideration during the selection process.
When submitted, the project initiation document will be viewable by all Enactus members for a reasonable period, allowing for feedback on the project and testing on its attractiveness to potential recruits. The document will also be reviewed for potential selection based primarily upon the following criteria:
Upon selection for development and testing of the proposed project, funds will be allocated to support continued progress. A core project team will need to be established if not previously as well as a project partner/sponsor (as applicable). Results of testing and analysis will be used to improve the existing project proposal to provide the most accurate picture of needed resources and potential impact. The project will then enter into implementation.
 Based on a set of guidelines on Project Initation Documents at http://www.mindtools.com/pages/article/newPPM_85.htm