Skip to end of metadata
Go to start of metadata

 

  • Project recommended for ECSS support from Allocations
    • Module 0: Overview of Project Management Suite
      • Overview of use of JIRA and Confluence, role of each component
      • In the context of the project management suite:
        • Roles and responsibilities of Project Manager
        • Roles and responsibilities of L3 managers
        • Roles and responsibilities of ECSS experts
        • Roles and responsibilities of L2 directors
      • Overview: lifecycle of a project
    • Module 1: Project Manager Project Setup
      • ECSS PM enters project information as JIRA Epic in ECSS project (Create new Epic in ECSS)
        • Assign to ECSS area (component)
        • ECSS PM creates project home page in confluence at the appropriate protected page for the correct area in ECSS - using the Project Home Page Macro
          • suggest naming the page consistent with Epic name (eg CTS17000045)
          • template has a suggested JQL query that can insert into the page for a project status display
        • ECSS PM initiates workplan from project home page - use button on project home page "Create Workplan"
          • save workplan with unique name such as "CTS1700045 Workplan"
          • Update JIRA macro to link to epic, using epic key (eg ECSS3-122) - note that you search before you save.
          • at this point the project is ready for the L3 to assign
        • ECSS PM transitions workflow to Project open, assigning to appropriate L3 on the way.
    • Module 1.5 Project Management Maintenance
      • Project Home page archive
    • Module 2: L3 Consultant Assignment or Project Rejection
      • L3 assigns project to appropriate lead ecss expert, additional experts can be added as "watchers" -
        • Transition workflow to "Consultant write workplan" and provide pointers to project home page and workplan in confluence, as well as indication of expected next action.
    • Module 3: ECSS Staff develop workplan and start work
      • ECSS experts draft workplan in confluence, note that the workplan can be exported as a PDF or word document for off-line consultation with the PI team. 
        • Once the table of milestones/tasks is created, the consultants should transition the workflow for the project epic back to the L3, for workplan review -
        • If the L3 approves the workplan, then the L3 can use the JIRA issue creation from table button in Confluence to turn the list of milestones/tasks into JIRA issues. Note: be sure to click "Create X(number of issues) issues from this table" so that JIRA will automatically create the issues from all of the tasks presented and not just the one you have presently highlighted. 
          • after this step the workflow should be transitioned to "Project in progress"
        • If the L3 needs to send the workplan back for further revision, then they can send the workflow back to "consultant write workplan" for further development, comments on what needs to be addressed can be sent in comments attached to the epic.
      • Once the project is "In progress", ECSS staff should work to figure out who should be assigned to each task as primary, and add secondary staff to the issue as "watchers" to facilitate collaboration.
        • Staff should put the tasks into the appropriate state as work progresses, and add comments as appropriate to help document project accomplishments
      • If tasks need to be added or modified, this can be done in JIRA (in the context of the epic) (show how), as well as added to the workplan.  two ways to add to the workplan - one would be to add a row to the table, and then to generate one issue from that row, alternatively, could add an issue within JIRA and then edit the table to include a link to this new issue. (need to document both ways).
        • modifying an existing task would require updating the table and the associated issue
        • at what point do changes need to be pushed back to the L3???
    • Module 4: Project Manager sends projects to quarterly report mode
      • At quarterly report time, ECSS PM can do a bulk state change of all in progress projects to quarterly report,
        • at this point, the ECSS experts can use the appropriate quarterly report button on the project home page to generate a blank template for the quarterly report
        • when the report is complete, the ECSS experts can change the state of the project back to "project in progress" - suggest including a link to the quarterly report in the comment field of the state transition.
    • Module 5: Extensions
      • Extension process - see meeting notes from ECSS Mgmt 11/21/2016
        • Jay - make slides based on workflow as exists today (12/1/2016)
    • Module 6: Project Final Report, PI Interview and Closeout
      • At the end of the project - any of (consultant/L3/PM) can transition the project into "final report" and use the final report button on the project home page to generate a blank template for the final report. 
        • does the final report need any L3 approval? right now we transition directly into project close
      • At project close, ECSS PM will make a PDF of the final report, and send to Nancy or Ralph for the PI Interview and move the workflow to "PI Interview"
      • When Nancy or Ralph communicate that the interview is complete and the results are appropriately recorded, then the ECSS PM can transition the project to "final closure".
    • Module 7: Basics of JIRA Query Language (JQL)
      • Basic JQL generation
      • Advanced JQL 
      • Embedding JQL in Confluence JIRA macros

 

  • No labels