forked from openstax/cnx-recipes
-
Notifications
You must be signed in to change notification settings - Fork 0
/
TeamFlow
73 lines (44 loc) · 3.09 KB
/
TeamFlow
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
# Here is some general info about the Books team:
Product Manager: Alina Slavik - @alina - alinams@rice.edu
Project Manager: Britt Weinstein - @britt - brw5@rice.edu
Engineering Manager: Helene McCarron - @helene - hm12@rice.edu
Textbook Developer: Brittany Johnson - @brittanyj - bj20@rice.edu
Textbook Developer: Thomas Williamson - @thomas - tomjw64@rice.edu
QA Analyst: Alan Cooke - @acooke - atc4@rice.edu
# What does the Textbook Developers team do?
-Generate and maintain content for PDF, iBooks, epubs, ancillaries and webview/Tutor content as well as print books.
-Work with Katalyst group on Assignable Webview and BakedPDF.
# What is the Books team culture like?
-Some would describe us as "crazy", "fun", "loud", or "food-motivated".
# Does the textbook development team sprint?
Yes. The textbook developers sprint at a two week cadence.
# What ceremonies does this team have?
- Weekly Monday trouble management meeting (card scrum)
- Quarterly Planning
- Sprint Retrospective and Planning Meeting
- Weekly check-in with the Katalyst developers
- Bi-weekly check-in with the Katalyst managers
- TBD Roundtable (Weekly)
# What Github repos do we use?
-oer.exports
-cnx-recipes
-webview
-easy-bake
# Where can I find information on creating an issue/PR/commit?
https://github.com/openstax/cnx-recipes/blob/master/CONTRIBUTING.md
# What is your release management workflow like?
- The team sprints at a two week cadence. Once items move from the backlog to In Progress, they must have story points attached.
- When coding is complete on a card, the card moves to Code Review with an attached PR(s) and assigned reviewers.
- When code has been reviewed, it moves to QA testing where Alan tests on QA and staging (after Britt requests code to staging from DevOps).
- On code release (production) day, Britt requests code deploys to production and content servers. Alan verifies that the code is on Production.
# How does the team work with a crit-sit?
- When a crit-sit occurs, Alina creates a crit-sit in Slack and notifies the entire Books team.
- Britt takes this information to the CNX team as it is possible that there could be overlap.
- The Books team works together to identify the root of the crit-sit.
- From there, Books Developers work together to resolve the crit-sit.
- When the crit-sit is resolved, Alina will announce this to the org. The team will hold a retrospective on the crit-sit as soon as possible.
# What are the TBDs doing to prevent crit-sits from occurring more often?
- Identify "snowflake" cases in code, infrastructure, or elsewhere to find ways to standardize to prevent points of failure in one off cases.
- The team will work to cross-polinate information with other teams when their is an active crit-sit.
- Polish recipe will be merged into the cn-recipe repo (with drop down added, some kind of oer.exports as-is template will be added to support the dropdown) - this is to prevent a "snowflake" case.
- Figure out ways to to communicate between teams when code changes might affect them, beyond the regular cross-polination of info.