Auto saved by Logseq
This commit is contained in:
parent
a90622d603
commit
ded335c376
|
@ -2237,13 +2237,26 @@
|
|||
- **Integration**: to ensure that components
|
||||
and subsystems of the product **work together** as
|
||||
expected
|
||||
- **Milestones**
|
||||
- **Milestones**: Provide goals for the development team’s
|
||||
schedule
|
||||
- Choose the **timing** of prototype cycles
|
||||
- Many early models are used validate concepts
|
||||
- Relatively few comprehensive models are necessary to test integration
|
||||
- Plan time to **learn** from prototype cycles
|
||||
- Avoid hardware swamp :-> where you keep building different ways out of a problem without stopping to think
|
||||
id:: 648ad0cb-1e77-4481-aac5-15be286baaad
|
||||
- Strategies: #flashcard
|
||||
- Use prototypes to reduce uncertainty
|
||||
Make models with a defined purpose
|
||||
- Consider multiple forms of prototypes
|
||||
- Choose the timing of prototype cycles
|
||||
l Many early models are used to validate concepts
|
||||
l Relatively few comprehensive models are
|
||||
necessary to test integration
|
||||
¡ Plan time to learn from prototype cycles
|
||||
l Avoid the “hardware swamp” - where you keep
|
||||
building different ways out of a problem without
|
||||
stopping to think
|
||||
- DONE Week4
|
||||
deck:: 2023t1/product/w4
|
||||
- ## Topic 18 初创企业和企业家精神
|
||||
|
|
Loading…
Reference in a new issue