James Lyneis

↑ 5 References

EM.411 meeting program management James Lyneis

→

James Lyneis

→

Worked with Jay Forrester

→

Project Dynamics

→

Dynamic

→

Strange loops

→

Something with reflexive changes

→

Dynamic systems are strange loops

→

System Dynamics

→

Might be possible to learn about this through software

→

A good software can teach as well as a good lesson

→

Expected staffing (effort) over time

→

Plan is a symmetric hump

→

Two seemingly common breaks from model

→

Hump moves to the right, maybe a second hump

→

Still attempting to finish on time

→

A long tail of burn down

→

Over shoots schedule

→

Dynamics driven be cause effect relationships

→

The physics is the system

→

Accumulation processes

→

Feedback processes

→

Balancing

→

Reinforcing

→

The rework cycle

→

Work done + undiscovered rework = work believed done correctly

→

Discovering undiscovered rework shows like zero productivity time

→

Seems like agile is meant to be structured in such a way to minimize and surface sooner rework

→

Causal loop diagrams

→

Reinforcing loops

→

Positive loop, virtuous circle

→

Negative loop, vicious circle

→

Balancing loop

→

Deaths and births balance population

→

Fred Brooks Brook’s Law Mythical man month

→

Adding people to a late software will make it later

→

System dynamics model produces a dynamic hypothesis

→

These deeply connected network models need to have core goal metrics

→

Like “value”

→

Would be a function of schedule cost morale etc

→

Direct vas indirect impacts

→

direct impacts

→

Something hits the plan

→

Indirect impacts

→

The internal looping ripple dynamic effects

→

James Lyneis

→

Adaptive resource control

→

EM.411 recitation meeting James Lyneis

→

Around 300 system dynamics projects across 50 companies

→

Channel tunnel was a system dynamics project, apparently

→

Agent-based modeling and system dynamics modeling are fundamentally different and incompatible ways of modeling

→

Which of agent-based modeling and system dynamics modeling is closer to the territory ?

→

Map and Territory

→

My guess is agent-based modeling, assuming it handles things as more atomic

→

Modeling is another way of saying coding

→

EM.413 meeting program management James Lyneis

→

project design for quality

→

Makes me think of zen and the art of motorcycle maintenance

→

Grade vs quality

→

Grade is determined by scope

→

What you’re building

→

Quality is determined by defects

→

How well you built

→

Quality dynamics

→

Rework as a function of quality

→

Change

→

Emergent change

→

A problem with meeting existing requirements

→

Not sure that “emergent” is the best descriptor here

→

Initiated change

→

Based off a change in requirements

→

Am important takeaway

→

Adding resources can increase delay

→

Brook’s Law

→

Asking a question is like drawing a vector

→

The answer extrapolates from the direction of the vector

→

This explains why asking a question often involves additional clauses to help fine tune the vector direction so it doesn’t set the respondent off in an unintended direction

→

Put a model diagram on your wall

→

Inspired by example from F-18 project

→

Truly novel projects are hard to predict what requirements are actually valuable

→

Excess work in models?

→

James Lyneis

→

Learning dynamics

→

How does individual and team effectiveness evolve?

Not much published data on this

→

Bruce Henderson

→

Boston consulting group

→

As experience doubles, efficiency improves around 20-30%

→

From 1936

→

Learning curve

→

Are there zero cost ways to transition tacit knowledge to explicit knowledge ?

→

Nonaka

→

Search Results

James Lyneis

↑ 5 References