Looking for Answers?
Browse our articles to find the answers you need
Process of doing product in WIX
thx for the heads up
00 - Kickoff
What is a kickoff?
The initial process, even before you start working on the new product. At this point, an opening call is made to talk about the product, its purpose, and who will work on the new product. At this point, the PM is sharing with the team before he (PM) started working on the spec, to make intentions and get opinions from others in the team.
The initial process, even before you start working on the new product. At this point, an opening call is made to talk about the product, its purpose, and who will work on the new product. At this point, the PM is sharing with the team before he (PM) started working on the spec, to make intentions and get opinions from others in the team.
Who
PM, UX, UI Designer, Support, BA, QA, Devs
Responsibility
PM to setup this meeting and inform about the new product
PM to setup this meeting and inform about the new product
Goals:
- Short meeting
- Understanding the goal
- Define high-level scope
- Describe the timeline
- Meet the planned and agreed upon release times
Outcomes:
- Everyone knows why we are doing this
- Everyone has an idea of what this product is about
- Everyone understands what is their responsibility in the product, and what should be their deliverables
- Rough time estimations by each members
01 - Research
Who
PM, UX, UI Designer, Support, BA, QA, Devs
Responsibility
PM & UX to collect all the feedbacks and make sure from each person what he need for working on this
Goals:
- Each member researches both general research and specific research for their domain. Understands what s/he needs to do and learn to meet the product goal according to the scope.
- Meet the planned and agreed upon release times
Outcomes:
- Each person presents his/her findings to the team. Insights and conclusions should be clear and accessibility to all band members.
- Link to the research
02 - Product Spec
Who
PM
Responsibility
PM / UX (if available to help)
Goals:
- Define why we do this and the scope.
- PM Draws and describes a rough product tractor, including features and all use cases.
- User flows.
- Some tractors can be broken down to first version and future version, if scope is too big.
- If this product includes integration, then PM should also create a flowchart
- BI data request and present data if exists.
- Meet the planned and agreed upon release times
Outcomes:
- All the members in the team see clearly the scope of the product and the requirements of the product.
- Each member define 85% estimation (how long it should take)
- Analyst can define KPIs and BI events
- Clear link to the spec.
03 - UX & Design
Who
UX
Responsibility
UX
Goals:
- UX draw the flow, layout, interaction and behaviors. Present how the user will achieve the product goal.
- Cover all cases (+edge) include all devices (Desktop, Mobile, etc.), and displays required capabilities for the dev. team
- Meet the planned and agreed upon release times
Outcomes:
- Link to UX spec & flow
- Each team member define 100% estimation (how long it should take now we can see the whole scope of the product )
- Dev team can start developing the infra and the fronted layout.
- Precise decision, who is developing the new component if needed.
- Jira tickets for the tasks.
04 - Ready for Development
Who
UX, PM
Responsibility:
UX Designers to define the Jira tickets with the relevant design spec.
Goals:
- Allow developers to access all information neatly, up-to-date, and describe responsibilities of the role owners to enable contact with any questions or clarifications.
- Meet the planned and agreed upon release times
Outcomes:
Epic Jira ticket should appear with all links to spec. (Product spec, UX Design, Zeplin, link to source files in drive and any source as needed. Also to subscribe to all team members who are working on it (Jira).
05 - Development
Who
Development
Responsibility:
Development
Development is our last part of the process of finishing the product. We must all enlist in tight communication at this stage to provide answers, solutions and most importantly to meet the quality of the product designed. It is the responsibility of the development to notify product and design teams of any issues that arise at this time. It is also the responsibility of the development to deliver to the product teams, design and QA any initial version that can be tested on it to reveal as many problems as possible at this time.
Goals:
- Develop the product and components according to product spec, design, performance and data.
- Reach the quality of the product/component defined along the way
- Meet the planned and agreed upon release times
Outcomes:
Feature protected link to our product, UX, QA teams to play with the product and test it before it’s going live. Give access to play with the product.
06 - User QA
All departments are responsible together for testing the product, each in its own field. The challenge is to combine forces with excellent communication to meet quality and product timelines.
Who
Who
QA, UX, PM, Devs
Responsibility:
QA, Development, PM, UX, UI, BI
Goals:
- Check the code and structure with our Design System parameters.
- Check API by the spec.
- Find bugs in the product
- Check performance
- Check this in a realistic way with real data
- Check product quality
- Experience the product in the user aspect with all use cases.
- Improve the product while testing
- Check the product on all the devices we have
- Check the product at all preset resolutions
- Try to interfere with the product in any way that users might do if intended or by chance
Outcomes:
List all problems and bugs and their prioritization before launching the product. Once the solutions have been agreed upon, assignments must be made.
Was this article helpful?
Yes
No
