Schedule
Mon 04-15 | Tues 4-16 | Wed 04-17 | Thur 04-18 | Fri 04-19 | |
|---|---|---|---|---|---|
| AM | Sam Im (Deactivated) & Wesley Brown in Gdynia Review agenda, prioritize, schedule meetings |
3.7 priorities Release Candidate 1 Start testing Noon lunch | Gdansk Continue testing Noon lunch | Continue Testing | Continue testing OR Release RC1 if testing is complete 11:00am Angola requirements meeting (Sebastian, Wes & Sam) | Continue testing OR Release RC1 if testing is complete 10.30am Configuration Guide updates and review Wes leaves Gdynia |
PM |
1pm Angola workflow and working with core 2pm Angola priorities and potential features to contribute 3pm Bug triage 3:30pm Discuss 3.7 Priorities 4pm Tech Committee | 3pm Bug triage 4pm 3.7 priorities ticket writing | 1:30pm Angola check-in 3pm Bug triage 3.30pm Releasing faster, trunk based development, feature flags, brainstorms | 1.30pm Reporting stack knowledge transfer topics 2.00pm 3.7 priorities ticket review/writing 3pm Bug Triage if needed Sam leaves Gdynia | ||
| Evening | board games? | beers? |
Suggested Topics
Features/Requirements
...
Tech Design
TBD agenda items
...
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
...
...
Process
Interested in all process topics:
- QA Meeting
- Required:
- Performance Testing
- Retrospective 3.6 Retrospective or Gap project retrospective
- Discuss how having multiple teams has been (everyone)
- Improvements for OpenLMIS (Top3 voting game)
...
- Reporting tickets - what is next high priority?
- Translations
- Batch Approval ticket (this needs more information to understand what to design)
- Someone who is responsible for approving a large number of requisitions for many facilities
- Select multiple requisitions to review and approve - might not be the same requirements as Malawi batch approval.
- Possible workflow changes to allow approval of requisition then move to next requisition to approve
- Aggregate summary of requisitions (this needs more information and requirements before design)
- Third party supplier - can we talk high-level design options?
- Reports that pull data from Stock Management
For Wes and Sebastian (Core OLMIS Team Topics):
- Team organization
- Keep a single team? Yes
- Continue with the same dev agile process? Yes
- Are there aspects of our dev process that we might want to change given that almost all of the dev will be done by SD for the next phase of our work?
- Improve meetings that we already have:
- No specific issues with current meetings
- How would we do the showcase given that we have a single dev group?
- Keep the same time
- Focus more on getting feedback for user-facing features
- In what way can I best support the team?
- Stop team lead meeting, no one-on-one with Sebastian
- Just have daily update from SD team members and specifically call out people if blocked
- Having feature discussions during planning is very helpful
- What about the other stewards, are there things that we can be doing better?
- Ensuring that questions to stewards are answered quickly
- How can we best stay involved with the Angola work?
- Does the team have any input on feature priorities for 3.7 and beyond?
- Would it be helpful to do a v3.6 retrospective?
- How can we best provide support for both MW and Angola (once it moves to the maintenance phase)?
Social
- social time?
- board games?