![reviews of icircuit reviews of icircuit](https://www.electronics-lab.com/wp-content/uploads/2019/02/IMG_0039.jpg)
![reviews of icircuit reviews of icircuit](https://icircuit.net/wp-content/uploads/2016/04/AtomEditor.png)
My team was working on an application that uses indoor location which designed based on pozyx.
![reviews of icircuit reviews of icircuit](https://i.pinimg.com/originals/1f/2b/9d/1f2b9dff472ef7ef0a1c2bbd7cfdd9a7.png)
These assumptions need to be verified under conditions and modified accordingly. My second incident was bit different, which says making ground assumptions and moving ahead is also not right way. Assumptions may mislead, validate them before you make more assumptions based on previous once !! Then onward, I used to make very clear assumptions. Though making assumptions and documenting them seems to be rudimentary task, it is very critical part of proposal document. Because this specific condition was written we could get rid of bad named of delayed delivery. Timeline assumptions were proved vital later because ARC board of client team took considerable time to approve the design document. Then my Lead explained, unless you make those assumptions in writing, this would not be known to others. Also my plan did not include architects approval. I assumed that all the different environmental setups would be available. They taught me many good lessons.Įnvironment related assumptions were missed out by me. I got earful of shouts on that day during his review of proposal. Then supervisors were strict, blunt and straight forward. In this blog, I would like to quote two anecdote from my life Assumptions are importantġ2 years back, When I wrote my first proposal response document, My Lead introduced this word “assumptions”. In our (software) industry, “Assumptions” is common word and used extensively in all proposal documents.