Create a new Plan Approved template

process/PlanApprovedTemplate.md

@@ -0,0 +1,122 @@
+# OpenHW  Plan Approved Template: Instructions
+
+
+*This template is for the OpenHW Group Plan Approved (PA) gate. The PA gate follows the PL gate in the OpenHW project gate sequence. To recap, the gate sequence is:*
+
+- *Project Concept (PC)*
+- *Project Launch (PL)*
+- *Plan Approved (PA)*
+- *Project Freeze (PF)*
+
+
+*The Project Concept and Project Launch document templates are described [here](https://github.com/openhwgroup/programs/blob/master/process/PC_PL_Template_Markdown.md)*
+
+*At the PA gate a full feature list and project plan is presented by the OpenHW project team to the TWG for review and comment.*
+
+*Most CORE-V software projects have a single Project Concept/Project Launch covering a family of cores or platforms.  The PA will normally provide the project plan for a specific CORE-V target within that family.* 
+
+*Copy and modify the template below*
+
+<hr/>
+
+
+
+## Title of Project 
+
+
+## Date of proposal
+
+## Author(s)
+
+
+## (*For SW Projects*) Target Platform
+*Specify the specific target platform for this project. The general target family is specified in the PC/PL document. For example, the PC/PL might address CV32E4 family of embedded processors. The PA might target the CV32E40P MCU.*
+
+
+
+## Project deliverables 
+
+
+*The high level project deliverables (e.g. code, verification, user document, and other deliverables) should be listed. I.e. what are the open-source deliverables? Don't list detailed features here.*
+*The following table is provided as an example*
+
+| Deliverable		    | Description			| Leader				|      
+| --------------------- | --------------------- | ---------------------	|
+| Item1	    			| RTL code				|						|
+| Item2	    			| Verification of RTL	|						|
+| Item3	    			| User Manual			|						|
+
+
+
+## Feature List 
+
+
+*This section provides the detailed feature list of the project.*
+*If the features are outlined in detail in the PL, or within a User Manual or other document, refer to that document. If not, the feature list should be provided here*
+
+
+
+## Resources
+*Members (organizations) and individuals committed to work on the project should be listed in this section*
+*The following table is provided as an example*
+
+| Organization					| Person							| Area of focus							|      
+| --------------------    		| --------------------    			| -------------------- 					|
+| Organization1	    			| Person1					  		|	RTL									|
+| Organization2	    			| Person2					  		|	RTL									|
+| Organization2	    			| Person3					  		|	Verification									|
+
+*The person or persons responsible for project planning/ management should be listed* 
+ - *Project Manager(s)*
+ - *Technical Project Leader(s)*
+
+
+
+
+
+
+
+
+## Work Breakdown Structure
+
+
+*The project work is broken down starting from high level to low level.*
+- *At high level, work can be broken down by technical component, project phase, area of focus or other method.*
+- *At low level, specific tasks are enumerated with estimated time durations (e.g. 1 person for 2 weeks)* 
+- *If appropriate, tasks are assigned to individuals*
+- *For agile projects, tasks can be assigned to individuals during project execution. If so, initial task backlog without assignment to individual can be created.*
+- *Format of the WBS can be github project board, spreadsheet, or other*.
+
+
+
+
+## Schedule
+*A timeline view is created by considering the WBS breakdown, dependencies among tasks, resource availability, and schedule requirements. The format of the timeline view can be github project board with milestones, a spreadsheet, or gantt chart.*
+
+- *The schedule should indicate the planned date of major milestones and the first release for the project*
+- *Remaining uncertainties or issues to be resolved should be described*
+- *How the schedule will be maintained following PA should be described*
+
+
+
+
+## Checklists to pass the Project Finished/Project Release Gate
+*The checklists which will be used to gate the completion of the project should be listed. The checklists don’t need to be presented at the PA gate. Steps to create them should be described.*
+
+| Checklist						| Description						| Plan to Develop Checklist					|      
+| --------------------    		| --------------------    			| -------------------- 					|
+| RTL Freeze	    			| 					  				|										|
+| Verification Complete	    	| 					  				|										|
+| Documentation Complete    	| 					  				!										|
+| IP Checklist complete    	    | 					  				!										|
+
+## Risk Register
+*Risks towards completion of the project for the given target should be listed and risk mitigation plan should be stated*
+
+
+| Risk							| Description						| Plan to Mitigate Risk					|      
+| --------------------    		| --------------------    			| -------------------- 					|
+| Risk1	    					| 					  				|										|
+| Risk2	    					| 					  				|										|
+| Risk3	    					| 					  				!										|
+