Farmacy Family is an enhancement of the existing Farmacy Foods system and was created with the spirit of making healthy food widely accessible and affordable by guiding a tighter engagement with customers and offering an AI-Based solution that drives personalized nutrition choices and recommendations.
- We aim at developing relationships between engaged customers and nurture those relationships
- We work hardly on converting transactional customers to engaged customers
- We generate analytical data from medical information to demonstrate the benefits of Farmacy Foods
We want to spread happiness, promote equal opportunities of approaching healthy nutrition, enhance social experience, and contribute to spreading awareness.
In order to assess Market Opportunity, primary and secondary research were conducted. Initial investigations suggest high profitability could be achieved by
- Resegmenting the existing market
- Driving a successful model in another region.
A Continuous Delivery Agile Life Cycle together with a well-established customer feedback loop will provide reasonable input to enhance initial market estimates. mainly: TAM, SAM, and SOM. [
image source ]
In order to visualize and understand various forces that drive our system, a Business Model Canvas was established.
Motivated by the above diagram, and with the goal of understanding customers' pain and engaging their wishes, an initial lean version was constructed. it is to be continuously enhanced and updated based on feedback recieved. [ See MVP below ]
For a clear identification of measurements that lead to valuable insignts and Key Performance indication KPI, Vanity metrics were avoided and was replaced with Actionable metrics
Use customer feedback to develop/improve the product
To establish sound bonds with various stakeholders, to encourage feedback and to understand customer needs, an Exploratory Life Cycle was constructed. Once completed, a Continuous Delivery Lean Life Cycle is to be followed for deploying the final solution.
Details on the below processes are to be updated as the project progresses.
The goal is to get things running in the right direction. The process include:
1. Exploring Scoep
2. Identifying Architecture Strategy
3. Planning the Release
4. Developing a Test Strategy
The goal is to incrementally build a consumable solution and includ the following:
1. Proving Architecute Early
2. Addressing Changing Stakeholder Needs
3. Improving Quality
4. Accelerating Value Delivery
The final goal is to release the solution into production and include:
1. Ensuring Production Rediness
2. Deploying the Solution
Various stakeholders are to be listed. Their Power, Interest and Influence is then to be analyzed to prepare a suitable engagement plan. The final objective is to maintain supportive and less resistive stakeholders
The plan is to be updated shortly based on received feedback. Here are some samples:
High power, high interested stakeholder -->
Manage Closely.
- Fully engage in the development.
- Exert the greatest efforts to satisfy their requirements
High power, less interested stakeholder -->
Keep Satisfied
Low power, interested stakeholder -->
Keep Informed
Low power, less interested stakeholder -->
Monitor
Underdevelopment. Include frequency of communication, way of communication ... etc
To understand the needs and without loss of generality, the following represent a sample usage of our system. User stories are listed under Functional Requirements. Check the next section
