Get Started. It's Free
or sign up with your email address
Devops by Mind Map: Devops

1. BI: Deliver High Quality Online Courses

1.1. EPIC: Provide Secure and Performant IT Infrastructure

1.1.1. FEATURE: Add Application Framework CORE 2.0

1.1.1.1. PBI: Install CORE 2.0 on uoev-appP1

1.1.1.2. PBI: Install CORE 2.0 on uoev-appP2

1.1.2. FEATURE: Update Security Framework to TLS 1.2

1.1.3. FEATURE: Standup New Database Server

1.1.4. FEATURE: Remove Deffects from Infrastructure

1.1.4.1. BUG: Server does not restart after patch applied

1.1.4.2. BUG: Performance on DB server is very poor

1.2. EPIC: Provide Secure and Performant Administrative Tools

1.2.1. FEATURE: Create an Automated Enrollment Tool

1.2.2. FEATURE: Add a Daily Errors Report to Courselink Tool

1.2.3. FEATURE: Remove Defects from Administrative Tools

1.2.3.1. Bug: Autoenrol tool not parsing hyphenated names

1.3. EPIC: Provide Secure and Performant T&L Tools

1.3.1. FEATURE: Create Courselink Application Platform

1.3.2. FEATURE: Add Reporting to Courselink Application Platform

1.3.3. FEATURE: Add Additional Reporting Feature to Courselink Application Platform

1.3.4. FEATURE: Add a Dashboard to PEAR2

2. BI: Provide High Quality Registration

2.1. EPIC:Provide Robust Registration System

2.1.1. Feature: Create New form elements to the registration form

2.1.1.1. PBI: Get Form Element details from Marketing

2.1.1.2. PBI: create mockup of new form

2.1.1.3. PBI: Develop the form and deploy to testing

2.1.1.4. PBI: Ensure form performs as needed

2.1.1.5. PBI: Release to Prod

2.2. EPIC: Provide Simple and Quick Registration Workflow

3. Structure

3.1. BI

3.1.1. Definition: Department level business initiative focusing on our Strategic Mandate

3.1.2. Fields

3.1.2.1. Description

3.1.2.2. Success Criteria

3.1.2.3. Additional Notes

3.1.2.4. Discussion

3.2. Epic

3.2.1. Definition:Unit level Initiative or Service in Response to Departmental BI

3.2.2. Fields

3.2.2.1. Iteration

3.2.2.2. Assigned to:

3.2.2.3. Area

3.2.2.4. State

3.2.2.4.1. *New

3.2.2.4.2. *Approved

3.2.2.4.3. *Committed

3.2.2.4.4. *Done

3.2.2.4.5. *Removed

3.2.2.5. Description

3.2.2.6. Success Criteria

3.2.2.7. Discussion

3.2.2.8. Start Date

3.2.2.9. Target Date

3.2.2.10. Priority

3.2.2.11. Effort

3.2.2.12. Value area

3.2.2.13. Time Criticality

3.2.2.14. Value Area

3.2.2.15. Discussion

3.3. Project / Feature

3.3.1. Definition: Standalone Deliverable Element in support of an Epic

3.3.2. Fields

3.3.2.1. Iteration

3.3.2.2. Assigned to:

3.3.2.3. Area

3.3.2.4. State

3.3.2.4.1. *New

3.3.2.4.2. *Approved

3.3.2.4.3. *Committed

3.3.2.4.4. *Done

3.3.2.4.5. *Removed

3.3.2.5. Description

3.3.2.6. Acceptance Criteria

3.3.2.7. Risks and Obstacles

3.3.2.8. Discussion

3.3.2.9. Dependencies

3.3.2.10. Start Date

3.3.2.11. EndDate

3.3.2.12. Priority

3.3.2.13. Time Criticality

3.3.2.14. Value Area

3.3.2.15. Discussion

3.4. PBI

3.4.1. Definition: List of Necessary Elements needed to deliver a Feature

3.4.2. Fields

3.4.2.1. Iteration

3.4.2.2. Assigned to:

3.4.2.3. Area

3.4.2.4. State

3.4.2.4.1. *New

3.4.2.4.2. *Approved

3.4.2.4.3. *Committed

3.4.2.4.4. *Done

3.4.2.4.5. *Removed

3.4.2.5. Description

3.4.2.6. Acceptance Criteria

3.4.2.7. Dependencies

3.4.2.8. Priority

3.4.2.9. Effort

3.4.2.10. Value Area

3.4.2.11. Discussion

3.5. Bug

3.5.1. Definition: Defect in code, configuration or hardware affecting delivery of service

3.5.2. Fields

3.5.2.1. Iteration

3.5.2.2. Assigned to:

3.5.2.3. Area

3.5.2.4. State

3.5.2.4.1. *New

3.5.2.4.2. *Approved

3.5.2.4.3. *Committed

3.5.2.4.4. *Done

3.5.2.4.5. *Removed

3.5.2.5. Description

3.5.2.6. Reason

3.5.2.6.1. *New Defect

3.5.2.6.2. *Build Failure

3.5.2.7. Repro Steps

3.5.2.8. System Info

3.5.2.9. Acceptance Criteria

3.5.2.10. Priority

3.5.2.11. Severity

3.5.2.12. Remaining work

3.5.2.13. Activity

3.5.2.13.1. *Requirements

3.5.2.13.2. *Design

3.5.2.13.3. *Development

3.5.2.13.4. *Deployment

3.5.2.13.5. *Documentation

3.5.2.13.6. *Testing

3.5.2.14. Found in Build

3.5.2.15. Integrated in Build

3.5.2.16. Discussion

3.6. Task

3.6.1. Definition: Work items needed to complete a Product Backlog Item

3.6.2. Fields

3.6.2.1. Iteration

3.6.2.2. Assigned to:

3.6.2.3. Area

3.6.2.4. State

3.6.2.5. Description

3.6.2.6. Discussion

3.6.2.7. Priority

3.6.2.8. Remaining work

3.6.2.9. Activity

3.6.2.9.1. *Requirements

3.6.2.9.2. *Design

3.6.2.9.3. *Development

3.6.2.9.4. *Deployment

3.6.2.9.5. *Documentation

3.6.2.9.6. *Testing

3.6.2.10. Original Teime Estimate

3.6.2.11. Actual Time

4. Teams

4.1. App Dev Team

4.2. Multimedia Dev Team

4.3. Systems Team

5. Areas

5.1. OpenEd2

5.1.1. Course and Program Delivery

5.1.1.1. Tools

5.1.1.1.1. Pear1

5.1.1.1.2. Pear2

5.1.1.1.3. Courselink

5.1.1.1.4. InFront

5.1.2. Marketing and Enrollment

5.1.2.1. Tools

5.1.2.1.1. Destiny

5.1.2.1.2. Maestro

5.1.3. Infrastructure

5.1.3.1. Server

5.1.3.2. Networking

5.1.3.3. Database

5.1.3.4. Storage

5.1.4. Classroom Technical

5.1.4.1. Tools

5.1.4.1.1. Crestron

6. Tags

6.1. Product Affected

6.1.1. Speechelo

6.1.2. REV

6.1.3. Pear1

6.1.4. SFQLink

6.1.5. PEAR2

6.2. Unit

6.2.1. DE

6.2.2. CE

6.2.3. Reg

6.2.4. Fin

6.2.5. Sup

6.2.6. ELP

6.2.7. Mkt

6.2.8. Sup

6.2.9. ITS

6.2.10. CTS

6.3. Course (not section)

6.3.1. Econ1100

6.3.2. Phys2210

6.3.3. 10021100

6.4. Function

6.4.1. Administrative

6.4.2. Teaching and Learning

6.4.3. Compliance

7. Workflows

7.1. App Dev Team

7.1.1. Feature Level

7.1.1.1. Proposed

7.1.1.2. Requirements / Sizing

7.1.1.3. Pending

7.1.1.4. Committed

7.1.1.5. Build

7.1.1.6. Test

7.1.1.7. Release

7.1.2. PBI Level

7.1.2.1. To Do

7.1.2.2. In Progress

7.1.2.3. Done

7.1.2.4. Blocked

7.1.2.5. Closed