What a great wrap up of the back story for the project! Thanks for insight and personal stories behind the effort. It always boils down to the team and the fun learning that makes any project rewarding..
Hi Sanjib, weekend and holidays and evenings :-) At work we would talk over lunch. We would stay late. We would also meet up at each others homes to work together.
We'd divide up the work so that one person can work on it alone until it was time to hand it off to the person. If a task required multiple people, then it would be handed back and forth until done.
The weekend work sessions were for integrating all the subsystems into one. Making sure they worked, interfaced with other subsystems, etc.
Hi Steve, congratulations for overcoming the challenges to have the mission accomplished successfully. The biggest challenge of all as I see from what you've described is: this is done by a group of volunteers, who are not co-located at a site for the duration of the project. As you have mentioned, many of the cases, the volunteers kick-off the projects with great enthusiasm, but over time, it dies down because of the other priorities, family priorities or diversion of interest etc. I think it is a great achievement for the team to have a sustained determination over the entire duration. Just curious to know: did your team work only on the weekends and holidays to do this?
My Mom the Radio Star Max MaxfieldPost a comment I've said it before and I'll say it again -- it's a funny old world when you come to think about it. Last Friday lunchtime, for example, I received an email from Tim Levell, the editor for ...
A Book For All Reasons Bernard Cole1 Comment Robert Oshana's recent book "Software Engineering for Embedded Systems (Newnes/Elsevier)," written and edited with Mark Kraeling, is a 'book for all reasons.' At almost 1,200 pages, it ...