Skip to end of metadata
Go to start of metadata


     The PSS Approval Process begins after a PSS page has been created in Confluence and a Project Scope Statement Issue has been created in JIRA. Those steps are outlined here: Creating a PSS

     Once this process begins, a notification scheme is enabled that emails Approval Groups (sponsoring workgroups, co-sponsoring workgroups, management groups, steering divisions, TSC) at appropriate times through the approval process.

     It is important to note that upon receiving a notification that your group's approval is requested, that you understand how the Project Scope Statement in JIRA is setup. 

     The PSS Approval process is composed from two workflows: that of the PSS itself and that of the reviewing groups. The relationship between these two workflows are parent to sub-task respectively.

     All of the group approvals, minus the final Technical Steering Committee (TSC) review/approval, happen as sub-tasks of the Parent Issue. 

     The approval process is automated in that, after you cast your group's approval, no further action is required to further the process. 




  1. Follow link in email to parent issue in JIRA. NOTE: If you are a part of multiple work groups, make sure to note what group is being requested to review.  

  2. Review the issue

  3. Review the PSS on Confluence using link.

  4. Navigate to the "Sub-Tasks" section of the PSS issue. 

  5. Select your Group

  6. While at the Sub-Task for your group's approval you may make comments, add attachments, and approve or reject. 

    1. Approve: This choice will be reflected in the Parent Issue and the approval process will carry on. 
    2. Reject: This choice will be reflected in the Parent Issue and the approval process will be paused. A reason for rejection will be required and a notification will be sent to the Sponsoring WorkGroup. 
      1. If you are a Sponsoring WorkGroup, you will be emailed a name of the rejecting group and a link to the Issue. 
      2. Once the noted changes for rejections have been corrected, you will transition the sub-task back to "Review" using the transition button on the applicable sub-task. 
      3. The original group which rejected will be notified and provided a link. 
      4. They will navigate back and review. If sufficient changes have been made, they will approve this sub-task and the approval process will carry on. 
      5. This process can happen multiple times until it is finally approved. 
    3. If you are a Co-Sponsoring group you will have an Opt-Out option as well. Should your group feel it doesn't need to take part in the approval, select this option. No further action required; approval process will carry on. 

  7. Once Sponsoring WorkGroups, Co-Sponsoring WorkGroups, Us Realm, Management Groups, and Steering Divisions have approved the Parent issue will be transitioned to TSC Review. 
    1. At TSC Review, the TSC will be notified via email just like the other groups, however they will be interacting with the parent issue rather than sub-task type. 
    2. Options for the TSC Review include:
      1. Approve: PSS is considered Approved. Email is sent to Sponsoring WorkGroup
      2. Send to Steering Division: Parent issue is transitioned back to the Steering Division Review state and applicable steering Division is notified. Reason required by TSC
      3. Reject: PSS is considered Not Valid and will not become a project. (Rare)

  • No labels