1. Mapping Your Business into Jira
- Importance of business analysis before configuration
- Goals: reduce rework, improve efficiency, encourage adoption
- Approach: Discover → Map → Implement
- Stakeholder engagement: interviews, MoSCoW prioritization, process diagrams
- Case study: Teams in Space – cleanup and standardization of messy Jira instance
Lab 1 – Mapping Business Requirements into Jira
- Cloud: View Teams in Space requirements (5 min)
- Data Center: Start lab VM & view requirements (5 min)
2. Assigning Project Roles & Sharing Schemes
- Identifying Scrum vs. business team roles
- Jira roles: Administrators, Project Lead, Default Assignee, Board Administrators
- Mapping team roles to Jira roles & permissions
- Teams in Space case: restricting developer admin rights, designating Scrum Master as Lead
- Shared schemes: benefits (consistency, reduced admin overhead, performance) vs. drawbacks (less flexibility, stakeholder involvement)
Lab 2 – Assigning Roles & Sharing Schemes
- Assign project roles (40–50 min)
- Create a standard project as a baseline
- Share schemes across projects
3. Configuring Work/Issue Types, Fields & Screens
- Creating work/issue types and custom fields
- Best practices: reuse fields, avoid unnecessary customization
- Screen schemes and field configurations
- Mapping screens to operations (Create/Edit/View)
- Case study application: aligning Teams in Space work types to new schemes
Lab 3 – Configuring Work/Issue Types, Fields & Screens
- Cloud: 1h 20m
- Data Center: 2h 10m
- Create fields, configure screen schemes, apply field configurations
4. Configuring Screens & Schemes (Cloud only)
- Field configuration schemes
- Workflow schemes
- Notification & permission schemes
- Work item/issue security schemes
Lab 4 – Configuring Screens & Schemes (1h, Cloud only)
5. Creating & Configuring Workflows
- Workflow elements: statuses, transitions, conditions, validators, post functions
- Workflow schemes: associating workflows with work/issue types
- Best practices: keep workflows simple, avoid over-engineering, encourage reuse
Lab 5 – Creating & Configuring Workflows
- Cloud: 1h 15m
- Data Center: 1h 25m
- Build workflows for bugs, stories, and other issue types; implement workflow schemes
6. Configuring Board & Sprint Permissions
- Role of board administrators
- Configuring permissions for Scrum Masters vs. team members
- Aligning permissions with Teams in Space governance model
Lab 6 – Configuring Board & Sprint Permissions
- Cloud: 40 min
- Data Center: 1h
7. Configuring Email Notifications (Cloud only)
- Notification schemes overview
- Mapping project roles to notifications
- Balancing notification overload vs. missing key updates
Lab 7 – Configuring Email Notifications (25 min, Cloud only)
8. Applying New Configurations to Projects
- Applying schemes to new projects
- Migrating existing projects to new standardized schemes
- Cleaning up unused schemes
- Teams in Space: enforcing standardization going forward
Lab 8 – Applying New Configurations to Projects
- Cloud: 1h
- Data Center: 55 min