|
|
|
|
|
|
by shrimp_emoji
2252 days ago
|
|
|
From my professor: >Consider this. What if the repository in which we craft our products is configured with cost estimates in mind? At the moment our logged hours reaches the total we projected, the repo would freeze and we grade the work. How would this affect our work? >Do you have confidence in your plan? Would you bet your course grade on the quality of a project frozen at that point? |
|
|
This reminds me of the appetites and bets that Basecamp's "Shape Up" describes. https://basecamp.com/shapeup
Instead of keeping scope and time 'fixed' and sacrificing quality, instead try and keep quality and time 'fixed' but be willing to sacrifice scope.
Having an 'apetite' in mind for how much you want a particular feature then mitigates: if you fail to achieve what you want in the fixed time period, do you want to try again later or is it more effort than it's worth to you.