|
|
browse.develop.com
Browse.develop.com is a community that was established to collect and
organize valuable web information. Our technical staff have selected and
indexed information and courses that they feel will help you stay
current on best practices across the SDLC.
|
6 Articles match "2009","Systems Thinking"
|
The Latest from DevelopMentor
|
MORE
|
|
A tale of two conferences (Lean & BA)
His alternative is systems thinking. Personally I think the two approaches are complementary. am always keen to relate Agile and Lean back or organizational learning, and I believe that system thinking is an essential element of such learning. John introduced me to a new term: “Failure demand” - that is the demand created on a organization or system because of earlier failure. I spent the first part of the week attending the UK Lean conference swiftly followed by the IRM BA conference. Heres a rough cut at some thoughts from the two conferences.
Allan Kelly's Blog
- Sunday, October 4, 2009
Basic In and Out of Black Boxes
Once the boundaries for your system / software / business unit are defined as a black box, do not worry about what is inside the box. Tags: Systems Development Black Box Requirements Systems Thinking Focus on what goes in, what comes out, when this happens, and rules the box must follow. So just what can go into our come out of this box? [.].
Jim Schardt's Blog
- Thursday, March 19, 2009
Agile and Lean - the same but different
Perhaps someone else who was in the room can help me with the exact quotes but this is how I remember him putting it: • When Dan, Jim Womack and Daniel Roos wrote did the research that resulted in The Machine that Changed the World they had to think of a term to describe what they found. Toyota Production System was too Toyota specific. That said I think there is a subtle distinction, its actually a distinction that can be helpful on some context. Agile is more general, Agile is more of a value system, a philosophy. And in his view there is no difference.
Allan Kelly's Blog
- Thursday, February 12, 2009
|
-
|
The Best from DevelopMentor
|
MORE
|
-
Systems Thinking: Requirements?
The definition seems to depend on what role you play in relationship to requirements definition – Customer, Business Analyst, Systems Analyst, Designer, Architect, [.]. Tags: Systems Development Requirements Systems So how do you define requirement? was working with a large hospitality corporation when I was asked this question. The problem is that the notion of requirement comes in many forms.
Jim Schardt's Blog
- Tuesday, January 6, 2009
-
Avoiding Requirements Confusion with Black Boxes
By clearly understanding the boundary of your system you can easily distinguish between requirement and design statements. Tags: Software Development Black Box Requirements Systems Thinking
Jim Schardt's Blog
- Monday, January 19, 2009
-
Basic In and Out of Black Boxes
Once the boundaries for your system / software / business unit are defined as a black box, do not worry about what is inside the box. Tags: Systems Development Black Box Requirements Systems Thinking Focus on what goes in, what comes out, when this happens, and rules the box must follow. So just what can go into our come out of this box? [.].
Jim Schardt's Blog
- Thursday, March 19, 2009
-
Requirements and Black Boxes
For requirements, I think of any system as if it were a black box. Tags: Systems Development Black Box Requirements Systems Thinking After dealing with requirements in all sorts of shapes and sizes over the years I find the “black box&# approach works well. can “see” or experience the outside of the box. can experience the contours of the box. can [.].
Jim Schardt's Blog
- Monday, January 12, 2009
-
Agile and Lean - the same but different
Perhaps someone else who was in the room can help me with the exact quotes but this is how I remember him putting it: • When Dan, Jim Womack and Daniel Roos wrote did the research that resulted in The Machine that Changed the World they had to think of a term to describe what they found. Toyota Production System was too Toyota specific. That said I think there is a subtle distinction, its actually a distinction that can be helpful on some context. Agile is more general, Agile is more of a value system, a philosophy. And in his view there is no difference.
Allan Kelly's Blog
- Thursday, February 12, 2009
-
A tale of two conferences (Lean & BA)
His alternative is systems thinking. Personally I think the two approaches are complementary. am always keen to relate Agile and Lean back or organizational learning, and I believe that system thinking is an essential element of such learning. John introduced me to a new term: “Failure demand” - that is the demand created on a organization or system because of earlier failure. I spent the first part of the week attending the UK Lean conference swiftly followed by the IRM BA conference. Heres a rough cut at some thoughts from the two conferences.
Allan Kelly's Blog
- Sunday, October 4, 2009
|
|
|
