Budget v1 0
Version 2 (Jeremy Wright, 03/06/2012 03:21 am)
| 1 | 1 | Jeremy Wright | h1. Budget v1.0 |
|---|---|---|---|
| 2 | 1 | Jeremy Wright | |
| 3 | 1 | Jeremy Wright | h3. Overview |
| 4 | 1 | Jeremy Wright | |
| 5 | 1 | Jeremy Wright | The budget is $200, firm. If there is a conflict between function and budget, for this iteration, budget should trump. Our goal is not to make the perfect test stand, it is to make the first prototype of a test stand and see what we can learn from that experience (both about test stands, and about our processes). We can always go back and do another iteration to meet the design requirements if needed. Holding to a firm budget minimizes the amount of time spent trying to make it perfect (once you are out of money, you have to wrap up the project, successful or not). Even a "unsuccessful" prototype will teach us important lessons to apply moving forward. This budget does not include "consumables" such as motors, nor tools, but the $200 cost for the stand itself keeps the basic project affordable if standard tools found in hackerspaces can be used. Any manufacturing that has to be hired out to a third party will be taken out of the $200 budget, and should be avoided to keep this project more practical for those same hackerspaces. |
| 6 | 1 | Jeremy Wright | |
| 7 | 2 | Jeremy Wright | h3. Detailed Budget |
| 8 | 1 | Jeremy Wright | |
| 9 | 1 | Jeremy Wright | TODO: Break the budget down into line items. |