53 lines
1.5 KiB
Markdown
53 lines
1.5 KiB
Markdown
## What Happened
|
|
|
|
### Projects
|
|
- 🟡 **Umami** - Dates need replanning
|
|
- 🟠 **Algolia** - Jalon 2 not validated, delivery due July 28
|
|
- 🟢 Hub - Going great but ads must be clarified as to what will be delivered
|
|
|
|
### Operations -
|
|
- ⚪ **Jira SLA health** - Visibility currently insufficient
|
|
- 🟠 **Habiba coverage** - Vacation Friday, coverage needs clarification
|
|
|
|
### Capacity
|
|
- 🟠 **QA** - Four projects approaching QA, freelancer not possible until January
|
|
|
|
### Upcoming
|
|
- 🟢 **VP September Review** - Projects + operations, team participating
|
|
|
|
## CTO 1-1
|
|
- Freelancer QA: CTO agrees with approach, January earliest
|
|
- Strategic KPI initiative: CTO agrees with direction
|
|
- VP wants team project review in September
|
|
|
|
|
|
## Notes
|
|
|
|
### September - VP Project Portfolio Review
|
|
|
|
CTO informed me that VP wants a review of the team's projects in September.
|
|
|
|
**Expected:**
|
|
- Projects currently being worked on
|
|
- Current status / progress
|
|
- Team members present
|
|
- Team participation in presenting/discussing their work
|
|
|
|
**Implication**
|
|
|
|
Monday needs to accurately reflect the project portfolio before this meeting.
|
|
|
|
Project owners need to be comfortable explaining:
|
|
- What are we trying to accomplish?
|
|
- Where are we?
|
|
- What is the next commitment?
|
|
- When will it be delivered?
|
|
- What is blocking us?
|
|
|
|
|
|
**Next steps**
|
|
- Clean up project portfolio in Monday.
|
|
- Establish regular project-owner updates.
|
|
- Determine September presentation format.
|
|
- Prepare team before VP review.
|