Race for Space
contest that will send one lucky reader into space. Throughout the series, Bubbles often talks about his love for space and his lifelong desire to become a spaceman someday, but his poor eyesight has always prevented him from even owning a drivers license. Its a fictional show obviously, but Bubbles desire to go to space on the show was actually born out of my love of space and rocketry. It has been a hobby of mine since I was 5 years old. If I win this chance to go to space, I intend to shoot a documentary of the entire process leading up to the flight, in hopes of inspiring a new generation of young people to become involved in space exploration."
1) Break the project into features/stories/usecases (whatever you want to call them). Features should be as small as possible but large enough to still offer business value. The customer would say with this deployed, I can now solve a problem or acheive a goal with the system that I that I couldn't before.
2) Only give estimates in terms of complexity points: 1 point - I've done this before, its a fairly simple thing. I'm confident it won't grow in scope 3 points - Not too much unknown, a bit of new thinking involved, more than a trivial feature but not something you'd lose sleep over 5 points - pretty big chunk of work, fairly complex, fair amount of unknowns 8 points - too big to estimate or even make an educated guess about, try to break these into separate features
3) Do a couple of months of work and see how many points you get Done. Done means the users have tried it out and would sign off on the features being ready for production. In production is an even better point to measure done at.
4) Calculate how many points you can now commit to for the next given period based on read data. At this point, you are probably ready to provide fairly decent estimates. You will find that your notion of what is complex or not won't change much over time. That's why this this method works.
5) Get your customers to define what it will take to sign off on the feature up front. Don't talk in terms of solutions, but in terms of solved business problems or achievable business goals. The how and the details are to be worked out durring development and with the end users and especially the developers creativitity.
At some point in the next X years this will happen:
E-Vehicle Monthly Lease Rate + Charging Cost + Lower EV Maintenance Rates
will be less than or equal too
Monthly fuel cost + higher maintenance costs of current gas powered vehicles
I think when this happens, it will trigger a lot of people to walk away from gas powered vehicles.
I've already taken the plunge and ride an electric bike to work every day. Its a 60km round trip and faster than car or transit. I get some exercise on it too when I feel like pedalling. I drool at the thought of a battery that would give my bike 600km range!
At the end of the article he sums it up in his own words:
"Here's the thing. I learned that I did my best. I mean, I really tried my best. How many people can say that? I worked hard, and I mean really hard. I worked seven days a week from 8 am until 3 am. Every day. We drilled and drilled all winter when it was dark and the windchill was 80 below. Everyone thought I was crazy. But most people just never do their best, hey. And I did."
Sad that society today would classify this kind of individual as a "rogue".