@Frank Eory: to add a little more, in the teams I managed/led, the project manager was also the scribe and didn't miss any design review or concept meetings. We made efficient use of mind maps that captured all ideas, comments, inputs in a clear and structured way.
Concerning the uplink antenna, if you saw it in person you'd see that it is a very robust design. We are still trying to figure it out. Personally, I don't think we'll ever know what happened to the antenna. Thankfully the uplink works.
Steve did cover this pretty well in response to my questions in an earlier entry:
But I would agree such an early battery failure is not good.
Steve, any comments on the antenna failure pre-deployment? Would you do anything differently there? That said, I have worked with the type of antenna you describe and they are usually pretty rugged.
Hi Steve, thank you for sharing the lessons learned. Surely it helps us in getting wiser :).
Documenting the minutes of every meeting is a tough job but if it is done, surely it helps a lot later, saves lot of time for not re-doing the same discussions.
Any lessons learned from: ARISat-I worked fine even after one antenna was found broken? :)
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 ...