51 lines
1.4 KiB
Markdown
51 lines
1.4 KiB
Markdown
## Risks / Attention
|
|
|
|
### QA capacity - upcoming projects
|
|
**Status:** 🔴 High
|
|
|
|
Four major projects are expected to reach QA close together.
|
|
|
|
Current QA capacity: 1 person.
|
|
|
|
**Risk:** QA becomes a bottleneck, delaying project delivery even if development finishes on schedule.
|
|
|
|
**Proposed mitigation:** Temporary freelance QA support during the overlapping QA period.
|
|
|
|
**Discuss with CTO:** 2026-07-27
|
|
|
|
**Next step:**
|
|
- [ ] Determine how to manage QA capacity for September.
|
|
- [ ] Get everything ready for ideally November so that in January, freelancer is ready
|
|
|
|
Related
|
|
https://docs.google.com/presentation/d/1Eg588k87Bxsy_pTxxjc-xPuXfEiFMFJbqP3FD0FCvgg/edit?slide=id.g3db66fc5ba7_0_2#slide=id.g3db66fc5ba7_0_2
|
|
|
|
|
|
----
|
|
### 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. |