-
Notifications
You must be signed in to change notification settings - Fork 0
/
co-work-oct-25.qmd
117 lines (78 loc) · 3.08 KB
/
co-work-oct-25.qmd
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
---
title: "Agile Oct 25, 2023"
format:
revealjs:
theme: [serif, custom.scss]
footer: "[Home](index.html)"
---
## Today's theme
- Keep working together on Pathways
- Learn a little about "agile" methodologies
- Learn about GitHub project boards
- co-work
## What is agile?
A **lightweight** workflow **structure** for software development which is characterized by 4 key features.
Today agile methodologies are the norm in software development, and are widely used for other types of project management.
Term is traced back to the 2001 [Agile Manifesto](https://agilemanifesto.org/), but the ideas are much earlier and broader.
## 4 elements
{fig-align="center" width="80%"}
## Task cycles
A key element of agile methodologies is iterative cycles
{fig-align="center" width="80%"}
This was popularized by the work of William Edwards Deming.
::: footer
1 Leading thinker in statistical quality control and industrial engineering in the 1950s to 1980s. Plan-Do-Check-Act (PDCA) cycle.
:::
## Experiential learning
In "experiential learning" (David A Kolb, 1970s-1980s), the activity is the teacher via explicit periods of reflection and experimentation.
{fig-align="center" width="80%"}
##
{fig-align="center" width="80%"}
## Self-organizing workflows
A workflow or structure that naturally and organically improves team (or project) flow and efficiency.
::: columns
::: {.column width="50%"}
### Task boards
- visualize your workflow
- team awareness
- encourages cycles of work
:::
::: {.column width="50%"}
### Facetime
- short frequent synchronous check-ins, aka "stand-ups"
- co-working, group or often paired
:::
:::
## Task boards
{fig-align="center" width="100%"}
<!--
## Why use a task board?
Visualize the flow of work so that we can improve it incrementally and organically--meaning no fixed framework. Just seeing your workflow helps you see the problems.
- transparency -- visual representation of the team's workflow
- iterative and incremental
- helps define a "minimal workable product
- problems with task "flow" are addressed as they arise
::: footer
Atlassian Kanban video series: [intro](https://www.youtube.com/watch?v=iVaFVa7HYj4), [designing your Kanban board](https://www.youtube.com/watch?v=Bcid33tgq8A), [work in progress limits](https://www.youtube.com/watch?v=zEJn6eQO6FE), [writing kanban cards](https://www.youtube.com/watch?v=PxXdcQrPIUI)
:::
-->
## GitHub project boards
Let's start a project board with GitHub!
- Create a board
- Make some issues
- Add issues to a board
## 30 minutes of co-work time
::: columns
::: {.column width="50%"}
### Work on Pathways
- Ideas for things needed to move you towards a Pathway goals
- Identify some concrete tasks
:::
::: {.column width="50%"}
### GitHub Project Boards
- Play around
- Raise hand or post in chat for help
- Mentors/helpers can go in a breakout room with you
:::
:::
Super ok to jump in an out of break out rooms to see what folks are talking about!