Feature development Workflow

### Feature development Planning Workflow<sup>Functional approach</sup>

In FP, impurity (aka Effects), is handled in a Monadic approach.
This approach enables developers to focus on pure logic implementation and testing, keeping the "Side Effects" on the envelope.

I would like to give a shot to this approach to development planning and time estimations.

The software we are developing is ususlly not self contained. We need to integrate with other software, APIs, Operating Systems, etc...
All those "effectful" aspects, in practice, take an *unknown* amount of time to complete.
This makes our estimation prone to errors, too "flexible" or unprecise, or in some cases "way off".

I will try to identify these effectful aspects of my design, remove it from my estimation and as a start estimate only my "pure functionality development" time.
Then, I will try to scope and estimate my "effectful development" time and effort and see if this helps me become better at estimation time.

Make sure to :: the most naive and fast working solution