This document discusses several key principles of agile development including valuing technical excellence, testing from day one, failing fast, transparency, and full utilization of team members. It seeks to dispel myths about agile such as the ideas that working is unnecessary, deadlines don't exist, or that agile is only for special people. The document emphasizes focusing on delivering value, making plans flexible, using prototypes, building quality in from the start, and allowing people to work without being at full capacity at all times.

1. Agile valuesStanislav VasilyevAgile Estoniastanislav.vasilyev@agile.ee

2. Myths about AgileWorking is not necessaryDeadlines do not existIt is really hardAgile is a hypeIt is meant for special peopleThere is no slackNo one is responsible

3. Early startup days

4. Maturing organizationSupport and maintenanceRules and policiesDepartments /TeamsInfrastructureCompetitorsBudget

5. Floating in deep waters

6. To be fast, you have to be agile…

7. Going fast means…There are no defectsThere are good engineering practices – code is clean and easy to maintainPeople are in touch with the business and can make fast decisionsNo extra work is done

8. Focus on valuePlans are nothing; planning is everything. Dwight D. EisenhowerDo only things that make your product and business betterDo not think too much of a future, it is really unpredictablePrototypes!

9. Testing from day oneFinding problems early is cheaperWe believe in test automationBuild quality inYou can build quality product, but it is hard to add quality later

10. Fail fastFail tolerant attitudeThe faster you will know that it is a dead-end – the betterLet’s try 3-4 different solutions during a month instead of squeezing everything from a single idea

11. Involvement and transparencyPeople should see how they work affects businessClear decisions and rules apply to everyoneCommon goal and common purposeProvokes self-organizationPeople become a part of something big, instead of just another department

12. Technical excellenceWe expect people to know what they are doingConstant improvementGood people lead to good resultsPeople develop your product, not processes and tools

13. Full utilizationPeople should have time to do the workNo one is able to work on full utilization all the timeInstead of thinking how to get full utilization from the people, think how to automate process and prioritize wisely

14. Person able to…speakexpress opinion in a logical manner, speak up when needed. Being silent is an answer toolistento others, to ideas, find compromises, let other express opinionsthinkbeing able to make decision, use common sense, constantly improve, adjust

15. Questions?Thank You!