The document discusses several key principles of agile in different environments: 1) The objective of agile is to continuously deliver the most value for clients by reducing inventory, shortening feedback loops on functionality used in production and documented deliverables. 2) When using agile, teams should not get caught up in their own beliefs about what defines value and instead focus on what the client considers valuable, even if that means additional documentation or processes. 3) Customizing agile processes to suit different environments and client needs is not "bastardizing" agile but rather discovering better ways of working, and teams should avoid following agile practices blindly without consideration of situational factors.

1. Agile in Different
Environments
its a good thing

2. Topics
Objective of Agile
Don’t sub-optimize Value
“Better ways” versus “bastardizaton”
Beware of the Fundamentalists

3. Objective of Agile
To continuously deliver the most value for
our client
This is done primarily by:
Reducing Inventory
Shortening Feedback loops

4. Reduce Inventory
Documents
Completed Functionality
time spent on processes not resulting in
functionality

5. Shorten Feedback Loops
Shorten Feedback on functionality
Used in Production
documented
Deliver Value frequently

6. Agile vs Non-Agile
adversarial
elitist
change the discussion to just getting better
often you have to make small changes

7. Don’t sub-optimize value
sometimes in Agile we get caught up in what
we believe value is
Value starts and ends with the client
sometimes additional documentation and
process are needed by the client
More Agile processes can deliver less value
for some clients!!!

8. Value in Estimating
Good example of who defines value is the
discussion on Estimating
Much discussion proposes not to estimate
because it delivers no value
from whose perspective?
Perhaps Car Mechanics would also propose
giving estimates on car repairs have no
value?

9. “better ways” versus
“bastardization”
There is some discussion about customizing
Agile being equivalent to bastardizing Agile
We are discovering better ways

10. Beware of the
fundamentalists
Following Agile without situational awareness
is just as bad as blindly following waterfall
Customize to return the most value
Agile Physics vs. Agile Math

11. Agile Application Hints
Start with Kan Ban
Don’t call it Agile, we are just finding better
ways
Listen to what you client defines as value
and help to deliver that more efficiently

12. questions?