2023/10/11 →
#
>

11:06

→
#
>

EM.411 meeting System Engineering

→
#
>

Is number of parts a good surrogate for complexity ?

→
#
>

What about size of team required?

→
#
>

Couldn’t parts be chunked groupings of more granular parts?

→
#
>

Iteration and recursion are inherent to System Engineering

→
#
>

progress from simple to detailed, approximate to precise, risky to acceptable

→
#
>

Feels like Agile development will follow naturally from this

→
#
>

The diagram looks like the workflows I built on jira

→
#
>

Maybe SDM should have a joint lecture from the professors to transition between the phases, might make for a very useful way to get aligned on how the different phases interface.

→
#
>

Product development process

→
#
>

Four “primary enterprise processes” for systems

→
#
>

Customer acquisition

→
#
>

Product development

→
#
>

Product realization (fulfillment, sales)

→
#
>

Customer support

→
#
>

Goals

→
#
>

Market fit

→
#
>

Business case

→
#
>

make money

→
#
>

Risk

→
#
>

balance

→
#
>

Resources

→
#
>

prioritize and allocate

→
#
>

Visibility

→
#
>

on status of development

→
#
>

Phases

→
#
>

Think about n+3 at the concept phase

→
#
>

Not today’s product, but the product three iterations out

→
#
>

Think about n+2 at the specify phase

→
#
>

Seems like Agile development sits in contrast to this

→
#
>

The difference between one-off vs iterative product development seems like it will determine how you want to hybridize between Product development process and Agile development

→
#
>

speaking specifically about more waterfall versions of Product development process I think

→