This document discusses the evolution of various aspects of product development including nature, relations, management, requirements, architecture, and processes. It notes that understanding external forces like the wind and reducing unnecessary weight or inventory can help ensure prosperity. Evolution should have clear goals, react fast, say no to micromanagement, use appropriate detail in requirements, reduce the cost of mistakes, and keep processes and architecture simple.

1. Evolution Of Product

2. NatureLet’s see, what it teaches us

3. IT Have made mistakes

4. But result is a human

5. Not always more features ensure prosperity

6. Sometime all what we need is to understand which way the wind blows

7. An example from modern wolrd

8. Unnecessary weight can bring to extinction

9. Reed Queen EffectIt takes all the running you can do, to keep in the same place!

10. Evolution of RelationsTrust!Face-to-faceManagers among us

11. Evolution of ManagementClear goalReact fast and on the place.Say no to micromanagement!

12. Evolution of RequirementsClear goalScale of the requirementsAbsence of unnecessary detailsNobody can predict future, but we can reduce price of a mistakeReduce inventory

13. Evolution of ArchitectureGoal of architecture is to reduce cost of code modifying Architecture has not value to user, but it lighten values creation Reduce price of a mistakeReduce inventoryArchitecture can not fully control of code

14. Evolution of ProcessesNonlinear improvementAnalysis of effectiveness of business processesNo dogmasMaximum simplicity

15. THANK YOUR FOR LISTENING!Author – PavelAntonenko, Scrum Master at CS OdessaPresentation was inspired by Agileee 2009Any feedbacks you can send here – pasha.ant@gmail.com