Submit a Request

Submit requests through the self-service portal:

1. Sign into the self-service portal at https://service.stonybrook.edu/portal with your NetID and NetID password
2. Select Click to submit request or report incident
3. Select IT Professional Services
4. Select Projects
5. Select Request Project

Information You Will Need

We ask that all parties who have a request for a potential project submit a formal project proposal form. You will be asked for information regarding the proposed Project, such as the business case and benefits to the University.

You will have the ability to edit a completed form or continue an incomplete form under the following conditions:

• After filling out a complete or incomplete form click the SAVE icon (top left) and then click the SUBMIT button in the left pane of the screen.
• You will receive an e-mail indicating that you have made a submission. It will contain a ticket number that you can search to access your submission to edit/complete the form.

Request Process

Once you've submitted your request, you will be able to follow your request in the self-service portal by clicking on MY DoIT TICKETS near the top left and you will hear back from DoIT within 5 business days.

Your request will be reviewed by a dedicated analyst in the Division of Information Technology. Depending on the nature of the proposal, your request may be scheduled for implementation or submitted to the Project Prioritization Review Board for further review.

The Project Prioritization Review Board:

• sets the direction based on decisions and prioritization
• provides executive oversight and guidance on the Portfolio
• makes decisions on all project change requests that supersede the established thresholds
• ensures strategic alignment across all departments of Stony Brook University 

Each red circle is a Phase of the project, starting at the top of the circle with the project initiation being the first phase. 

• Waterfall project management is a sequential, linear process, it consists of several distinct phases. This model takes its name from the cascading “flow” of its life cycle, which moves downward (akin to a waterfall) through the stages of development. 
• In the Iterative model, iterative process starts with a simple implementation of a small set of the software requirements and iteratively enhances the evolving versions until the complete system is implemented and ready to be deployed. There may be multiple deployments throughout the process or one at the end of the Project.
• Agile project management is an approach based on delivering requirements iteratively and incrementally throughout the project life cycle. At the core of agile is the requirement to exhibit central values and behaviors of trust, flexibility, empowerment and collaboration.  In an Agile Project, there will be multiple deployments.
• This framework will support Waterfall, Iterative, and Agile methodologies.

Monitor and Control process oversees all the tasks and metrics necessary to ensure that the approved project is within scope, on time, and on budget so that the project proceeds with minimal risk. This process is continuously performed throughout the life of the project, we indicated it as the overall grey circle encompassing the Framework.

The arrow between Project Closure and Project Initiation is striped, this is intentional. If the methodology is a Waterfall, at Project Closure the project ends. Should the Project use Agile or Iterative, the cycle will start again.