Sign up to FuseBase for free
Save to FuseBase
Meeting
Print
Full screen
Share

Weekly Meetings

 
Outline

πŸ† Meeting topic:

Weekly updates

πŸ“† Date/time/location:

04.25.2025 11:00 AM
Meeting Room

🦁 Meeting attendees:

ο»ΏBruce Loo(Inactive member)ο»Ώ
ο»ΏConan Barbarianο»Ώ
ο»ΏBob Dylanο»Ώ

πŸ”Ž Retrospective

πŸ‘πŸ» Liked

 
1
Server build pipeline.
2
We deal with seatbacks by trying stuff rather than stagnating (e.g. full implementation with 3 different HTTP clients).
3
PoolMan re-uses our learning and code (healthchecks, finagle, AWS).
4
Devs asking for input from QA.
5
Informal retrospectives (free-form discussions).
6
Story time.
7
We're helping to bring devs up to speed with Scala (including on other teams).
8
Focus on quality code.
9
Helping apps on the way to multi-tenancy.
10
Solved a lot of problems with solutions that should be re-usable.
11
We've built a multi-tenant, highly available, scalable microservice.
12
Low touch practice/process.
All:
12

πŸ‘ŽπŸ» Lacked

 
1
More Attlassians working on Blobstore
2
"Formal" retrospective
3
Structure and process in JIRA
4
Documentations of lessons learned and remaining unknowns for memory issues.
5
JIRA developers
Calculate

❓ Questions

 
1
Questions About the Project in General
2
Are you proud of our finished work? If yes, what made it great? If no, what was wrong or missing?
3
Did we get the results we wanted and did it make an impact?
4
Which tools or techniques proved to be useful? Which not?
5
What did you learn about working with this client?
6
What important decisions were made during this project?
7
What compromises were made? (Things that might look like a mistake but were done for a reason.)
8
Questions About What Worked
9
What was the most gratifying or professionally satisfying part of the project?
10
What did we do well, that if we don’t discuss we might forget?
11
What helps us to be successful as a team?
12
Which of our methods or processes worked particularly well?
13
Where did we get lucky? What can we do to ensure we succeed if we aren’t so lucky next time?
14
Questions About Challenges
15
What was the biggest impediment?
16
Which of our methods or processes were difficult or frustrating to use?
17
What was painful but necessary?
18
What’s still keeping you awake at night? What did we leave unresolved?
19
What still puzzles us?
20
Questions About Take-Aways
21
What advice would you give yourself if you were to go back to the start of the project?
22
What should we have learned from this project a year from now?
23
Are there any lessons for you personally?
24
What else could we do better next time?
25
Question Sets
26
Use columns or a grid to organize answers in categories.
27
Liked, Learned, Lacked, and Longed For
28
Drop, Add, Keep, and Improve
29
Stop, Start, and Continue
30
Enjoyable, Frustrating, Puzzling
Calculate

βœ”οΈ Longed For

 
1
More minds thinking broadly about end-to-end architecture (more architectural safety nets for our deсisions).
2
Certainty around security and durability characteristics of Blobstore.
3
A JIRA that is easy to develop for (experience with JIRA dev speed is poor).
4
A compelling narrative for why Blobstore is important, especially for Atlassian customers.
5
An easy-to-use JIRA Agile.
6
A couch.
Calculate