2. Analysis - odoo-ps/pshk-process GitHub Wiki

Responsible: TC
Responsibility: Give technical analysis, push back any non-sense requests, give time and L.O.C estimation, ask for peer review on analysis.
Next: Client Validation
Objective: Giving a backend/technical analysis that is implementable during development.

General

TC looks at the functional details listed by FC and digs deeper into the problem from a backend perspective.
Use Ps Tools to write the analysis.

Setting Task Details

https://github.com/odoo-ps/pshk-process/blob/master/img/Analysis/analysis_assigned.png Set the reviewer to TC

Writing Tech Analysis

Paste the task's ID to Task ID, the details will be filled in afterward.

  1. Keep note of whether the database's platform, SaaS or SH.
    If it's Saas, don't think of overriding functions, add automations or scripts on top of the business flow.
    If it's SH, as much as possible try to override existing functions (and calling the super function itself).

  2. Try finding similar previous developments that may help this development to be easier.

After writing

  1. Reviewer ask for review from FJA and/or others. Peers should be making inputs and try to see if it's simiilar to any previous development they did. This may help a lot.

  2. Once it has passed review, copy the Analysis and put it on task under "Technical Analysis" Section. Move the analysis itself to "Posted" stage.

  3. Add timesheet and reliability under the task. Then, move task to stage: "Waiting for Client Go" https://github.com/odoo-ps/pshk-process/blob/master/img/Analysis/copy_analysis.png

Analysis Estimation Breakdown

• Dev Time: this is the time estimation to develop the feature
• Reliability: the % of confidence we will be able to stick to this estimation. For example, if we estimated the dev time to be 11h15 with 70% reliability,there is 30% probability that we will need “11h15 / 70% = 16h” of development due the potential complexity
• The analysis time is the amount of time it took for estimating the development
• The platform indicates if the development can be done on the Saas (if less than 10h) or if it requires SH.
• Project Time: this is the total time it might take to complete the development and go live with it. It is composed of:
55% of the development estimation including the reliability ratio + the analysis time 45% of the Business analysis and Project Management time (analyzing the development, writing down the analysis and specification, testing the development, training the SPOC, PM tasks…)
• Customer testing or migration time is the amount of time the customer should spend to test the development before going live with it or everytime he needs to test it during an upgrade. This gives an idea about the internal cost of the development for the customer.
• L.O.C. estimation: this is an estimation of the number of lines linked to the development (=Lines of Codes). It gives the possibility to provide a general idea about the recurring cost of the development.

Once you have those numbers, it is up to you and the sales to communicate with the client. Bump up the numbers as high as we can to a reasonable point.