|
eXtreme businessveryard projects > component-based business > eXtreme business |
| we offer | question | material | links | ||
| consultancy
management briefings and technical education independent advice on tools and methods |
Can the principles of eXtreme Programming be applied to lean business? |
[principles] [challenges]
|
|
|
Principles of eXtreme Businessveryard projects > component-based business > eXtreme business > principles |
 |
Don't waste energy anticipating or controlling the future. |
|
Build structures and processes that will satisfy the current requirements. |
|
Just enough complexity / flexibility. (Keep it simple, stupid.) |
|
Refactor periodically to maintain proper balance between simplicity, efficiency and flexibility. |
|
Focus on responding authentically to the immediate demand. |
|
Challenges of eXtreme Businessveryard projects > component-based business > eXtreme business > challenges |
|
eXtreme Programming works best inside a container - an external or wrapping system to provide regular feeds of requirements and resources. Where is the container or wrapper for an eXtreme Business? |
|
eXtreme Programming assumes the knowledge and skill to reflect and intervene on emerging structures and processes. This knowledge and skill belongs to a single discipline - software engineering. By contrast, an eXtreme Business has multiple conflicting professional disciplines - accountancy, legal, marketing, risk management, and others - all attempting to reflect and intervene on emerging structures. This entails a higher level of management - apparently not required in XP - to knock professional heads together. |
|
An eXtreme business is likely to be radically delayered - on the grounds that middle management are primarily concerned with longer-term strategic issues, which the eXtreme Business explicitly disregards. |
|
 |
