ACP-620 Day 3: Managing Projects Lab

Owned by Frank Lapa
Last updated: Nov 03, 2023
4 min read

 

Lab Exercise 1: Project Setup and Permission Configuration
(Beginner Level - 6 months of experience)

Objective: Configure a new project in Jira with custom permissions for different team roles.

Steps:

  1. Create a New Project:

    • Go to “Projects” and select “Create Project”.

    • Choose a project template that best suits your team's workflow (e.g., Scrum).

    • Set up the project with a unique key and name relevant to your team.

  2. Configure Permissions:

    • Navigate to “Project settings” and then to “Permissions”.

    • Create three new roles: “Viewer”, “Developer”, and “Project Manager”.

    • Assign the “Browse Projects” permission to the “Viewer” role, the “Browse Projects”, “Edit Issues”, “Create Issues” permissions to the “Developer” role, and all permissions to the “Project Manager” role.

  3. Map Users to Roles:

    • Under “Project settings”, go to “Users and roles”.

    • Add team members to the roles according to their responsibilities.

  4. Verify Permissions:

    • Ensure that users in the “Viewer” role can only view issues, “Developers” can create and edit issues, and “Project Managers” have full control over the project.

Deliverable: A screenshot of the project roles with the assigned permissions and a list of users for each role. Include evidence of testing the permission setup by showing the different access levels of at least one user in each role.

 

 

Lab Exercise 2: Workflow Customization and Transition Rules
(Intermediate Level - 1 year of experience)

Objective: Customize a workflow for a Software Development project including conditions, validators, and post-functions on transitions.

Steps:

  1. Edit an Existing Workflow:

    • Go to “Issues” and select “Workflows”.

    • Choose an existing workflow or create a new one and click “Edit”.

  2. Customize Transitions:

    • Add a new status “Code Review” between “In Progress” and “Done”.

    • On the “Start Progress” transition, add a condition that only users in the “Developer” role can execute this transition.

    • For the “Code Review” transition, add a validator that requires a pull request link in a custom field.

    • Configure a post-function on the “Done” transition that automatically updates the issue's resolution to “Fixed”.

  3. Publish Workflow:

    • After making the changes, publish the workflow and associate it with the relevant project.

  4. Test the Workflow:

    • Create a new issue and move it through the workflow to ensure all conditions, validators, and post-functions work as expected.

Deliverable: A diagram of the customized workflow, screenshots of the transition rules configuration, and a demonstration of the workflow in action by progressing an issue from creation to completion.

 

 

Lab Exercise 3: Advanced Issue Types and Field Configurations
(Advanced Level - 2 years of experience)

Objective: Create advanced issue types with specific field configurations for an IT Service Desk project.

Steps:

  1. Create Custom Issue Types:

    • Navigate to “Issues” and select “Issue types”.

    • Create two new issue types: “Service Request” and “Incident”.

  2. Configure Fields:

    • Go to “Custom fields” and create a new field “Impact” with options “Low”, “Medium”, “High”.

    • Associate the “Impact” field only with the “Incident” issue type.

  3. Design a Screen Scheme:

    • Create a new screen scheme that includes the “Impact” field for the “Incident” issue type and excludes it for “Service Request”.

  4. Apply the Screen Scheme:

    • Link the screen scheme to the IT Service Desk project for the appropriate issue types.

  5. Test Issue Creation:

    • Create new issues for each type and verify the “Impact” field appears only for “Incident” issues.

Deliverable: Screenshots of the issue type configurations, the custom field setup, and the screen scheme assignments. Provide examples of creating each issue type with the correct fields displayed.

 

 

Lab Exercise 4: Performance Metrics and Dashboard Reporting
(Expert Level - 3 years of experience)

Objective: Develop a dashboard that provides real-time performance metrics for project stakeholders.

Steps:

  1. Identify Key Metrics:

    • Determine which metrics are most valuable for stakeholders, such as lead time, velocity, or issue resolution time.

  2. Create Custom Gadgets:

    • Navigate to “Dashboards” and select “Create a new dashboard”.

    • Add custom gadgets that track the identified metrics, such as the “Average Age Chart”

for lead time or “Sprint Burndown” for velocity.

  1. Configure Access:

    • Set the dashboard’s sharing settings to allow access to the appropriate stakeholders.

  2. Validate Metrics:

    • Confirm that the data displayed is accurate and updates in real-time.

Deliverable: A screenshot of the completed dashboard with descriptions of each gadget and how it provides value to the stakeholders. Include evidence of real-time data updates.

 

 

Lab Exercise 5: Data Retention and Project Archiving
(Master Level - 3+ years of experience)

Objective: Implement a process to identify and archive completed projects according to the organization's data retention policy.

Steps:

  1. Identify Completed Projects:

    • Use JQL to find projects that have been inactive for the period specified in the data policy (e.g., no issues updated in the last 6 months).

  2. Archive Projects:

    • Go to “Project settings” for each completed project and select “Archive project”.

  3. Communicate with Stakeholders:

    • Before archiving, communicate with project leads and stakeholders to confirm that the project can be archived.

  4. Test Access:

    • After archiving, ensure that the data is still accessible according to the organization’s requirements but does not appear in active searches.

Deliverable: A report that includes the criteria used for identifying projects for archiving, a list of archived projects, and a description of how to access archived project data if needed.