Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "WTP Requirements Lead"
m |
|||
| Line 1: | Line 1: | ||
| − | The | + | === The Requirements Lead provides strategic input to the Project Leads and facilitates the creation and maintenance of the WTP Release Planning document. === |
| + | |||
| + | |||
| + | This includes: | ||
| + | *Network with the Eclipse/WTP ecosystem to gather strategic inputs on strengths, weakness, opportunities and trends for the WTP Project | ||
| + | *Define the Themes and Priorities of the release | ||
| + | *Engage the Project Leads to define the features for the release | ||
| + | *Maintain the WTP Release Planning document through the release so that it gives an accurate view of the work being done in the release | ||
| − | |||
For example, see [[WTP_Requirements_Main]]. | For example, see [[WTP_Requirements_Main]]. | ||
[[Category:WTP Roles| ]] | [[Category:WTP Roles| ]] | ||
Latest revision as of 20:27, 19 November 2007
The Requirements Lead provides strategic input to the Project Leads and facilitates the creation and maintenance of the WTP Release Planning document.
This includes:
- Network with the Eclipse/WTP ecosystem to gather strategic inputs on strengths, weakness, opportunities and trends for the WTP Project
- Define the Themes and Priorities of the release
- Engage the Project Leads to define the features for the release
- Maintain the WTP Release Planning document through the release so that it gives an accurate view of the work being done in the release
For example, see WTP_Requirements_Main.