# Product updates
## Alice

### App Store Reviews
- She didn’t do the comments part because Ebaneck said he’ll do it (her hands are no more there)
- Is Akwo aware that Ebaneck has taken off the work?
- YES
- So according to you, anything concerning reviews is no more your concern?
- YES
- She proposed the initial design and you accepted that she should implement it. But then when you reviewed it, you expected something else and spoke harshly. Felt it was undue.

### Banda
- Told Akwo to test banda reserves 2 weeks ago.
- Also reminded Akwo about it this morning
- Probably Akwo forgot
- If Akwo forgot, why didn’t you remind him to test again?
- Thought he had tested and was ready for deployment when ever we deploy the other features
- Also, I forgot about it as I was drowned with other work

### Group savings
- Delay from Ebaneck (about 1.5 weeks)
- Will finish this weekend and be ready for testing on Monday

### Flip
- Main feature is ready for testing since 2 weeks ago
- Notified testers (in the general group) to test
- Nobody but Alice has tested yet
- Waiting for others to test
- A feature flag was recently added (also available for testing)

## Muma
### Banda API
- 100% and integrated with front end (front end pending testing)

### Airtime
- Code for endpoints is ready and testing is going on
- Found bug in aitime purchase initialisation fixing. Hope to finish fixing by today

### Todo list reminders
- 0% done.
- Starts tomorrow
- Merge to master by Friday 9th June (Deploy to prod when Ebaneck is ready)

# Testing
It seems there is a misalignment in how testing should be done

- People forget to test
- Alice/Muma also forget to remind people to test because they are focusing on other things
- These cause delays in releasing that comes back to look bad the devs

**Resolution**
- We should have a better approach for managing the testing of features
- e.g use a ticketing system (maybe something that supports reminders)
- Review the testing tickets often
- Track who has tested what

# Release plan for Alice's features
- Finishing testing features that are ready for test (Everything except group savings)
- Akwo, Brenda, Ebaneck, etc..
- Should complete testing by Wednesday next week (7th June) and report bugs found
- Fix bugs if any (tentatively by Saturday 10th June) depending on the bugs (max 1 week)
- Push to prod (tentatively ~ 12th June)
- Depends on Ebaneck

# Dev plan
- Working on multiple features concurrently can be a dunting task
- Can we rearrange the resources at hand so they focus on 1 feature at a time (at most 2)
- This way, we can release to prod more frequently
- Will also spot bugs faster

# General problems
Overall, there is a lack of appreciation/encouragment and the heavy fines imposed on late coming and missed deadlines only add fuel to fire.

## Motivation
- Crazy startup culture (e.g deduction of salary when deadlines are not met) - Too strict
- All the salary deductions (upto even 40%) make people too stressed and the ask themselves why they even bother
- Feel not taken care of
- Disregard all other previous efforts only because a feature has not been deployed. Feeling unappreciated
- Too much pressure already (more pressure is not needed.)
- Feeling depressed and over stressed even though they are doing their best

#### ARE WE NOT SACRIFICING ENOUGH??
- Even though sometimes we don’t come at 9am, we always leave late. e.g 8pm, even 10pm and at 11pm even.
- On saturday work ends at 1pm but the usually leave at 4pm or 5pm.
- Is that not a sign of devotion?
- So what’s the point of deducting salary?
- We virtually spend all our time here

**Question: DO YOU PREFER A STRICT 9AM TO 5PM?**

## Lack of encouragment
- Nobody ever says thanks or good job
- We released the app last month and it was as if we had done nothing. We jumped to the next thing immediately as if the release didn't matter - It was a big release and we think we should have received some accolades. *I agree*

## Poor approach to communicate requests
- They feel management minimises the work they do. Want stuff to be done faster than possible.
- They are distracted by customer support and other stuff that previous people were doing. Which inevitably causes delays.
- For example, Alice says there was an issue on onboarding feature which was not her fault. But she felt hurt when Akwo said she hurried to do it because she has other jobs. Which was not the case
- It’s discouraging
- After doing all they do for the company, they do not feel appreciated.

Here's a short chat

> - Bill: Do you think if you gave a deadline of 1 month and released your work in that 1 month, people will not appreciate you?
> - Somebody: NO.
> - Somebody: They'll say I should have done it in 2 weeks.
> - Sombody: That I only said 1 month because I wanted to make time for my other side projects outside of Nkwa.

## Design issues
- Ebaneck complains too much about the design of screens when he is never there to validate them in the first place.
- So when they are done implementing, he comes and changes a lot of stuff and this further leads to delays

**Suggestion**
- We should implement a design review step before moving to implementation
- The design must be approved by the stakeholders
- e.g the designs for the upcoming airtime puchase feature

# The question of side hustle
- We are working fulltime and we are making sure this project turns out best.
- In the meantime, everyone needs to survive!

**I agree with the surving part :)**