Skip to content

Commit 5e72a17

Browse files
Mouse933Mouse933
authored
Adding Archive Files to SDO documentation (#317)
1 parent 5ad111c commit 5e72a17

File tree

70 files changed

+4559
-0
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

70 files changed

+4559
-0
lines changed

‎docs/cybersecurity/SecDevOps Team/Archived Files/Azure Boards Project Management/Azure DevOps Comparative Assessment.md‎

Lines changed: 211 additions & 0 deletions
Large diffs are not rendered by default.

‎docs/cybersecurity/SecDevOps Team/Archived Files/Azure Boards Project Management/Azure DevOps Quick Start Guide.md‎

Lines changed: 173 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,173 @@
1+
---
2+
sidebar_position: 10
3+
---
4+
# Azure DevOps Quick Start Guide
5+
6+
:::info
7+
**Document Creation:** December 15, 2024. **Last Edited:** December 15, 2024. **Authors:** Candice Smith.
8+
**Document Code:** ADO-QUIK-001. **Effective Date:** December 15, 2024. **Expiry Date:** December 15, 2025.
9+
:::
10+
11+
Following an assessment of Jira and Azure we underwent configuration of Azure DevOps. We identified that there are two big risks we can ultimately mitigate with the migration:
12+
13+
- Publishing of all Redback content to our public GitHub repos exposes us to inadvertently publishing sensitive information such as credentials, API Keys, and personal and health information
14+
- Planner not being a comprehensive enough project management tool to handle the dynamic and evolving nature of a Capstone company.
15+
This trimester we focused on creating a minimum viable product which would facilitate initial migration and allow future teams to make iterative improvements to the environment. We created a project space for all teams, sprints for T1 2025 and boards for project management, then migrated all content from Planner to Boards. Wikis and dashboards have been set up where possible and testing of these tools has been conducted.
16+
17+
This guide will give you an overview of how to get started using Azure DevOps in place of Planner boards.
18+
19+
## Current Configuration Progress by Team
20+
21+
- Done CS - Candice Smith Completed
22+
- Done Other - Completed by another team member
23+
- OOS - Out of scope T3 2024
24+
### Project 1
25+
26+
- Done CS - Set up project
27+
- Done CS - Allocated Ben Stephens as admin
28+
- Done CS - Set up Areas – IoT, VR, Web
29+
- Done CS - Added sprints for T1 2025
30+
- Done CS - Set Up Boards columns
31+
- Done CS - Added “perpetual informational planner items” as Wikis
32+
- Done CS - Added VR Team Work Details Handbook into Wiki
33+
- Done CS - Added Welcome Wiki
34+
- Done CS - Planner Migration (add planner tasks as user stories with checklist as tasks)
35+
- Done CS - Embed Boards into Teams for T1 2025 instead of Planner.
36+
- Not Started: GitHub Integration
37+
- Not Started: Set up Dashboard
38+
- Not Started: GitHub to Azure Repos migration
39+
### Project 2
40+
41+
- Done CS - Set up project
42+
- Done CS - Allocated Ben Stephens as admin
43+
- Done CS - Added sprints for T1 2025
44+
- Done CS - Set Up Boards columns
45+
- Done CS - Added Welcome Wiki
46+
- Done CS - Added Closed Tasks
47+
- Done CS - Planner Migration (add planner tasks as user stories with checklist as tasks)
48+
- Done CS - Embed Boards into Teams for T1 2025 instead of Planner.
49+
- Not Started: GitHub Integration
50+
- Not Started: Set up Dashboard
51+
- Not Started: GitHub to Azure Repos migration
52+
### Project 3
53+
54+
- Done CS - Set up project
55+
- Done CS - Allocated Ben Stephens as admin
56+
- Done CS - Added sprints for T1 2025
57+
- Done CS - Set Up Boards columns
58+
- Done CS - Added “perpetual informational planner items” as Wikis
59+
- Done CS - Planner Migration (add planner tasks as user stories with checklist as tasks)
60+
- Done CS - Embed Boards into Teams for T1 2025 instead of Planner.
61+
- Not Started: GitHub Integration
62+
- Not Started: Set up Dashboard
63+
- Not Started: GitHub to Azure Repos migration
64+
### Project 4
65+
66+
- Done CS - Set up project
67+
- Done CS - Allocated Ben Stephens as admin
68+
- Done CS - Added sprints for T1 2025
69+
- Done CS - Set Up Boards columns
70+
- Done CS - Added “perpetual informational planner items” as Wikis
71+
- Done CS - Planner Migration (add planner tasks as user stories with checklist as tasks)
72+
- Done CS - Embed Boards into Teams for T1 2025 instead of Planner.
73+
- Not Started: GitHub Integration
74+
- Not Started: Set up Dashboard
75+
- Not Started: GitHub to Azure Repos migration
76+
### Project 5
77+
78+
- Done CS - Set up project
79+
- Done CS - Allocated Ben Stephens as admin
80+
- Done CS - Added sprints for T1 2025
81+
- Done CS - Set Up Boards columns
82+
- Done CS - Added “perpetual informational planner items” as Wikis
83+
- Done CS - Planner Migration (add planner tasks as user stories with checklist as tasks)
84+
- Done CS - Embed Boards into Teams for T1 2025 instead of Planner.
85+
- Not Started: GitHub Integration
86+
- Not Started: Set up Dashboard
87+
- Not Started: GitHub to Azure Repos migration
88+
### Data Warehouse - Jesse
89+
90+
- Done Other - Set up project
91+
- Done Other - Allocated Ben Stephens as admin
92+
- OOS - Added sprints for T1 2025 – Jesse would prefer no sprints so all items can be seen in a unified task view
93+
- Done CS - Set Up Boards columns
94+
- OOS - Planner Migration (complete - The DW team's planner board is from T2 and can be deleted/wiped. All the required information or tasks that carried over to this trimester have been moved to azure boards.)
95+
- Done CS - Embed Boards into Teams for T1 2025 instead of Planner.
96+
- Not Started: GitHub Integration
97+
- Not Started: Set up Dashboard
98+
- Not Started: GitHub to Azure Repos migration
99+
### Cyber Security - Tristan
100+
101+
- Done Other - Set up project - Done
102+
- Done Other - Allocated Ben Stephens as admin - Done
103+
- Done Other - Added sprints for T1 2025 - Done
104+
- Done CS - Set Up Boards columns
105+
- Codey to complete: Added “perpetual informational planner items” as Wikis
106+
- Codey to complete: Planner Migration (add planner tasks as user stories with checklist as tasks)
107+
- Codey to complete: Embed Boards into Teams for T1 2025 instead of Planner.
108+
- Not Started: GitHub Integration
109+
- Not Started: Set up Dashboard
110+
- Not Started: GitHub to Azure Repos migration
111+
### Web and Mobile Dev
112+
113+
- Done CS - Set up project
114+
- Done CS - Allocated Ben Stephens as admin
115+
- Done CS - Added sprints for T1 2025
116+
- Done CS - Set Up Boards columns
117+
- Done CS - Planner Migration (add planner tasks as user stories with checklist as tasks)
118+
- Done CS - Embed Boards into Teams for T1 2025 instead of Planner.
119+
- Not Started: Set up Dashboard
120+
### Company Leaders
121+
122+
- Done CS - Set up project
123+
- Done CS - Allocated Ben Stephens as admin
124+
- Done CS - Added sprints for T1 2025
125+
- Done CS - Set Up Boards columns
126+
- Done CS – Used Board
127+
## Start of Trimester 1, 2025
128+
129+
### For Mentors and Team Leaders
130+
131+
- Mentors must be assigned to their Project Teams with at least Basic access.
132+
- They must assign at least 1 leader in their team with Basic access.
133+
- View the Welcome Wiki found in “Overview” > “Wiki”.
134+
- Mentors/Student Leaders must consider whether you want 1 unified team, or separate sub-teams.
135+
- Go to:
136+
137+
![](img/Picture1.png)
138+
139+
![](img/Picture2.png)
140+
141+
- Then assign all Redback Operations students to their respective teams with Stakeholder access. Do this by clicking on the team’s name, then when you are in the team view click “Add”:
142+
143+
![](img/Picture3.png)
144+
145+
*If any of the student leaders need to make changes to project teams, they will need to seek approval from their mentor for basic access.
146+
147+
Area paths have been set up, so team members should only see their own boards.
148+
149+
Any perpetual informational tasks housed within the previous planner have been added to the Team Wiki which can be found within the Project space > Overview > Wiki.
150+
151+
### For Team Members
152+
153+
- Once you have been granted Stakeholder access to Azure DevOps login and navigate to your team Wiki. This can be found in the left-hand menu under Overview > Wiki.
154+
- Read the Welcome Wiki understanding that some of this will already have been taken care of by your mentor or team leader.
155+
- Once you have read through the welcome wiki go to Boards in the Boards menu in the left-hand pane. It's a good idea to review what was completed last trimester and any item sitting open or in the backlog. This may give you an idea of the direction that you may want to take your individual contribution in.
156+
### For Everyone
157+
158+
At the start of the trimester once the team have looked over the information from the previous trimester it is a good idea to move any complete items you no longer need to reference into the completed previous trimesters column.
159+
160+
## During T1 2025
161+
162+
Here are some items you may want to consider moving into Azure DevOps in T1 2025, they were considered out of scope in T3 2024:
163+
164+
- Move the OnBoarding process into Azure DevOps.
165+
- Set up Power BI Integration so teaching team can audit activity utilising BI reports
166+
- Set up integration with current GitHub repos so teams can start working natively within Azure DevOps.
167+
- Consider full migration of your team’s GitHub repo into Azure Repos, this will create much better security around our dev pipelines.
168+
## At the end of T1 2025
169+
170+
- You may want to set up sprints for the trimester ahead so they can get started quickly.
171+
- Ensure your board is updated and items are moved through the swim lanes accurately reflecting progress.
172+
- Update Welcome Wiki with any knew information that may be required following your own contribution to Azure DevOps.
173+
- You may even want to update this quick start guide for the next cohort to get started quickly in the platform.

‎docs/cybersecurity/SecDevOps Team/Archived Files/Azure Boards Project Management/Best Practice & Usage Guidelines.mdx‎

Lines changed: 112 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,112 @@
1+
---
2+
sidebar_position: 4
3+
sidebar_label: Best Practice & Usage Guidelines
4+
title: Best Practice & Usage Guidelines
5+
description: Azure Boards Design & Usage Guidelines for Redback Operations
6+
---
7+
<div style={{ width: '100%' }}>
8+
<table style={{ width: '100%', borderCollapse: 'collapse' }}>
9+
<thead>
10+
<tr>
11+
<th style={{ width: '20%', textAlign: 'center' }}>Version</th>
12+
<th style={{ width: '20%', textAlign: 'center' }}>Modified By</th>
13+
<th style={{ width: '20%', textAlign: 'center' }}>Approver</th>
14+
<th style={{ width: '20%', textAlign: 'center' }}>Date</th>
15+
<th style={{ width: '20%', textAlign: 'center' }}>Changes made</th>
16+
</tr>
17+
</thead>
18+
<tbody>
19+
<tr>
20+
<td style={{ textAlign: 'center' }}>V1.0</td>
21+
<td style={{ textAlign: 'center' }}>Daniel McAulay</td>
22+
<td style={{ textAlign: 'center' }}>Daniel McAulay</td>
23+
<td style={{ textAlign: 'center' }}>17/09/2024</td>
24+
<td style={{ textAlign: 'center' }}>Document Creation</td>
25+
</tr>
26+
<tr>
27+
<td style={{ textAlign: 'center' }}></td>
28+
<td style={{ textAlign: 'center' }}></td>
29+
<td style={{ textAlign: 'center' }}></td>
30+
<td style={{ textAlign: 'center' }}></td>
31+
<td style={{ textAlign: 'center' }}></td>
32+
</tr>
33+
<tr>
34+
<td style={{ textAlign: 'center' }}></td>
35+
<td style={{ textAlign: 'center' }}></td>
36+
<td style={{ textAlign: 'center' }}></td>
37+
<td style={{ textAlign: 'center' }}></td>
38+
<td style={{ textAlign: 'center' }}></td>
39+
</tr>
40+
<tr>
41+
<td style={{ textAlign: 'center' }}></td>
42+
<td style={{ textAlign: 'center' }}></td>
43+
<td style={{ textAlign: 'center' }}></td>
44+
<td style={{ textAlign: 'center' }}></td>
45+
<td style={{ textAlign: 'center' }}></td>
46+
</tr>
47+
<tr>
48+
<td style={{ textAlign: 'center' }}></td>
49+
<td style={{ textAlign: 'center' }}></td>
50+
<td style={{ textAlign: 'center' }}></td>
51+
<td style={{ textAlign: 'center' }}></td>
52+
<td style={{ textAlign: 'center' }}></td>
53+
</tr>
54+
</tbody>
55+
</table>
56+
</div>
57+
58+
<div style={{height: '4px', width: '100%', background: '#FFA500', margin: '20px 0'}}></div>
59+
60+
## 6. Best Practices for Using Azure Boards
61+
62+
To ensure the successful implementation and ongoing use of Azure Boards within the Redback Operations Cyber Security Team, it is essential to follow established best practices. These practices will help each team manage their tasks efficiently, maintain clear communication, and ensure that all projects are completed on time and to a high standard.
63+
64+
<div style={{height: '4px', width: '100%', background: '#FFA500', margin: '20px 0'}}></div>
65+
66+
### 6.1 Structuring Work Items
67+
68+
Work items are the building blocks of Azure Boards, representing tasks, user stories, bugs, and other units of work that need to be tracked and managed. Properly structuring these work items is crucial for maintaining organization and clarity.
69+
70+
![Work Items](/img/azure-boards-images/6-1-image.png)
71+
72+
<div style={{height: '4px', width: '100%', background: '#FFA500', margin: '20px 0'}}></div>
73+
74+
### 6.2 Task Assignment and Management
75+
76+
Efficient task assignment ensures that work is distributed evenly across the team and that each task is handled by the most qualified team member. Proper management of these tasks is essential for maintaining momentum and avoiding bottlenecks.
77+
78+
![Task Assignments](/img/azure-boards-images/6-2-image.png)
79+
80+
<div style={{height: '4px', width: '100%', background: '#FFA500', margin: '20px 0'}}></div>
81+
82+
### 6.3 Using Boards and Views Effectively
83+
84+
Boards in Azure Boards provide a visual representation of the team's workflow, making it easy to track the progress of tasks and identify any bottlenecks. Configuring these boards to reflect the team's processes is essential for efficient management.
85+
86+
![Boards and Views](/img/azure-boards-images/6-3-image.png)
87+
88+
<div style={{height: '4px', width: '100%', background: '#FFA500', margin: '20px 0'}}></div>
89+
90+
### 6.4 Managing Backlogs
91+
92+
The backlog is a key component of Azure Boards, representing a prioritized list of work items that need to be addressed. Effective backlog management ensures that the most important tasks are completed first and that the team is always working on the highest-value activities.
93+
94+
![Backlogs](/img/azure-boards-images/6-4-image.png)
95+
96+
<div style={{height: '4px', width: '100%', background: '#FFA500', margin: '20px 0'}}></div>
97+
98+
### 6.5 Sprint Planning and Execution
99+
100+
Sprints are time-boxed periods during which specific tasks are completed. Effective sprint planning and execution ensure that the team is focused on achieving clear goals and that progress is made consistently.
101+
102+
![Sprint Planning](/img/azure-boards-images/6-5-image.png)
103+
104+
<div style={{height: '4px', width: '100%', background: '#FFA500', margin: '20px 0'}}></div>
105+
106+
### 6.6 Utilizing Queries and Dashboards
107+
108+
Queries and dashboards in Azure Boards provide tools for monitoring team performance, tracking key metrics, and gaining insights into project progress. Proper use of these tools ensures that the team can make informed decisions and identify areas for improvement.
109+
110+
![Queries and Dashboards](/img/azure-boards-images/6-6-image.png)
111+
112+
<div style={{height: '4px', width: '100%', background: '#FFA500', margin: '20px 0'}}></div>

‎docs/cybersecurity/SecDevOps Team/Archived Files/Azure Boards Project Management/Conclusion.mdx‎

Lines changed: 68 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,68 @@
1+
---
2+
sidebar_position: 9
3+
sidebar_label: Conclusion
4+
title: Conclusion
5+
description: Azure Boards Design & Usage Guidelines for Redback Operations
6+
---
7+
<div style={{ width: '100%' }}>
8+
<table style={{ width: '100%', borderCollapse: 'collapse' }}>
9+
<thead>
10+
<tr>
11+
<th style={{ width: '20%', textAlign: 'center' }}>Version</th>
12+
<th style={{ width: '20%', textAlign: 'center' }}>Modified By</th>
13+
<th style={{ width: '20%', textAlign: 'center' }}>Approver</th>
14+
<th style={{ width: '20%', textAlign: 'center' }}>Date</th>
15+
<th style={{ width: '20%', textAlign: 'center' }}>Changes made</th>
16+
</tr>
17+
</thead>
18+
<tbody>
19+
<tr>
20+
<td style={{ textAlign: 'center' }}>V1.0</td>
21+
<td style={{ textAlign: 'center' }}>Daniel McAulay</td>
22+
<td style={{ textAlign: 'center' }}>Daniel McAulay</td>
23+
<td style={{ textAlign: 'center' }}>17/09/2024</td>
24+
<td style={{ textAlign: 'center' }}>Document Creation</td>
25+
</tr>
26+
<tr>
27+
<td style={{ textAlign: 'center' }}></td>
28+
<td style={{ textAlign: 'center' }}></td>
29+
<td style={{ textAlign: 'center' }}></td>
30+
<td style={{ textAlign: 'center' }}></td>
31+
<td style={{ textAlign: 'center' }}></td>
32+
</tr>
33+
<tr>
34+
<td style={{ textAlign: 'center' }}></td>
35+
<td style={{ textAlign: 'center' }}></td>
36+
<td style={{ textAlign: 'center' }}></td>
37+
<td style={{ textAlign: 'center' }}></td>
38+
<td style={{ textAlign: 'center' }}></td>
39+
</tr>
40+
<tr>
41+
<td style={{ textAlign: 'center' }}></td>
42+
<td style={{ textAlign: 'center' }}></td>
43+
<td style={{ textAlign: 'center' }}></td>
44+
<td style={{ textAlign: 'center' }}></td>
45+
<td style={{ textAlign: 'center' }}></td>
46+
</tr>
47+
<tr>
48+
<td style={{ textAlign: 'center' }}></td>
49+
<td style={{ textAlign: 'center' }}></td>
50+
<td style={{ textAlign: 'center' }}></td>
51+
<td style={{ textAlign: 'center' }}></td>
52+
<td style={{ textAlign: 'center' }}></td>
53+
</tr>
54+
</tbody>
55+
</table>
56+
</div>
57+
58+
<div style={{height: '4px', width: '100%', background: '#FFA500', margin: '20px 0'}}></div>
59+
60+
## 9. Conclusion
61+
62+
The implementation of Azure Boards within the Redback Operations Cyber Security Team represents a critical step in optimizing project management, enhancing collaboration, and improving task visibility across the organization. By configuring Azure Boards to meet the specific needs of each sub-team, this solution provides a tailored platform for managing workflows, tracking progress, and ensuring alignment with the company\'s broader cybersecurity goals.
63+
64+
With features like custom boards, sprints, work item templates, and integrations with essential tools such as GitHub, SonarQube, Nagios, and SIEM systems, Azure Boards empowers each team to efficiently manage their tasks, streamline their workflows, and automate critical processes. The platform\'s ability to track incidents, code reviews, compliance audits, and infrastructure maintenance ensures that all aspects of Redback Operations\' cyber security efforts are properly managed and aligned with organizational priorities.
65+
66+
By integrating best practices in task management, reporting, and sprint execution, this solution is expected to lead to increased efficiency, reduced operational risk, and improved collaboration between teams. The successful deployment of this design ensures that the Redback's Cyber Security Team is equipped to handle its responsibilities while maintaining the flexibility to evolve alongside the organization's needs.
67+
68+
<div style={{height: '4px', width: '100%', background: '#FFA500', margin: '20px 0'}}></div>

0 commit comments

Comments
 (0)