Quote:
Originally Posted by BigBen
[snip]
I think they shouldn't release all of their info within the first week of build when everyone should be brainstorming. That takes SO much away from the actual design aspect
[snip]
|
While we are on the topic of design process and brainstorming, I will add a few of my thoughts. There is a great read out there
Product Design and Development by Ulrich and Eppinger that provides a lot of insight into the design process. They list the Concept Generation, or brainstorming, portion of the design process as a five-step methofology:
- Clarify the Problem
- Search Externally
- Search Internally
- Explore Systematically
- Reflect on the Solutions and the Process
A brief description of searching externally
Quote:
|
External search is aimed at finding existing solutions to both the overall problem and to the subproblems identified during the problem clarification step.
|
One of the last subtopics in external search section is "Benchmark Related Products".
I do agree that it is important for teams to go through the proper steps before starting the brainstorming process (how are you going to play the game, what is the team's goal for
what the robot has to do, prioritizing, etc.).
I am a fan of the 72 hour builds. I learned a lot by watching them, I can't say that we took what any of them did and placed it on our robot; but we did have some inspiration along the way.