Agile Demystified

  • 196 views
Uploaded on

Many companies have created a proper noun titled "Agile". But that word doesn't exist as a proper noun. The goal isn't to achieve some mythical ethos of "Agile" but instead to have organizational …

Many companies have created a proper noun titled "Agile". But that word doesn't exist as a proper noun. The goal isn't to achieve some mythical ethos of "Agile" but instead to have organizational agility. This presentation covers the principles of Organizational Agility and how to make your organization get to the goal of agility.

More in: Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
196
On Slideshare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
4
Comments
0
Likes
2

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. AgileDemystifiedCory Foy@cory_foyfoyc@coryfoy.comwww.coryfoy.comhttp://www.flickr.com/photos/ittybittiesforyou/4667430094/
  • 2. AgileAgile
  • 3. Agilehaswon
  • 4. Agilityhaswon
  • 5. neverAgilityhaswonnot
  • 6. http://www.flickr.com/photos/fortherock/3934041489
  • 7. http://www.flickr.com/photos/fortherock/3934041489
  • 8. http://www.flickr.com/photos/fortherock/3934041489
  • 9. http://www.flickr.com/photos/fortherock/3934041489
  • 10. Agile
  • 11. http://www.flickr.com/photos/49330484@N04/7681784466AProperNoun
  • 12. Agile Manifestohttp://agilemanifesto.org/A
  • 13. Agile ManifestoExtremeProgrammingScrumCrystal(Clear,Red,etc)AgileUPWaterfall
  • 14. f(x,Waterfall) = Agilityf(x, Scrum) = Agilityf(x, Extreme Programming) = Agilityf(x,Waterfall) != Agilityf(x, Scrum) != Agilityf(x, Extreme Programming) != Agilityf(x) = Agilityf(Process) != Agilityx
  • 15. f(x) = Agilityx = Organizational Mindset
  • 16. Distributed LeadershipFocus onValueHigh Impact CommunicationAbhor Delays Continuous LearningExperiment FrequentlyEmbrace Changex = Organizational Mindset
  • 17. Embrace Change
  • 18. Courtesy of Net Objectives (www.netobjectives.com)
  • 19. Distributed Leadership
  • 20. Focus onValue
  • 21. Courtesy of Net Objectives (www.netobjectives.com)
  • 22. Experiment Frequently
  • 23. Courtesy of Net Objectives (www.netobjectives.com)
  • 24. High Impact Communication
  • 25. 5 Biggest Problems inBusiness• Communication
  • 26. Abhor Delays
  • 27. Courtesy of Net Objectives (www.netobjectives.com)
  • 28. Continuous Learning
  • 29. Distributed LeadershipFocus onValueHigh Impact CommunicationAbhor Delays Continuous LearningExperiment FrequentlyEmbrace Changex = Organizational Mindset
  • 30. Distributed LeadershipFocus onValueHigh Impact CommunicationAbhor DelaysContinuous LearningExperiment FrequentlyEmbrace ChangeAgileagile
  • 31. Extreme Programming Distributed LeadershipFocus onValueHigh Impact CommunicationAbhor DelaysContinuous LearningExperiment FrequentlyEmbrace Change
  • 32. Scrum“3 of 3’s”Product OwnerScrum MasterTeam Product BacklogSprint BacklogBurndown Chart Sprint PlanningDaily StandupSprint ReviewRolesArtifactsMeetingsDistributed LeadershipFocus onValueHigh Impact CommunicationAbhor DelaysContinuous LearningExperiment FrequentlyEmbrace Change
  • 33. • Our sprints are 12 weeks long...• We do two normal sprints andone bugfix sprint...• We do all our planning up front...• We skip the daily meeting...• Our managers decide whats ineach sprint...• We havent read the books yet...• Our team has 30 people...We’re doing Scrum BUT... Distributed LeadershipFocus onValueHigh Impact CommunicationAbhor DelaysContinuous LearningExperiment FrequentlyEmbrace Change
  • 34. You Can’t Estimate In AgileBudgetForecastFixed Bid
  • 35. You Can’t Estimate And AchieveAgilityDistributed LeadershipFocus onValueHigh Impact CommunicationAbhor DelaysContinuous LearningExperiment FrequentlyEmbrace Change
  • 36. You Can’t Know WhenYou’ll BeDone In Agile
  • 37. You Can’t Know WhenYou’ll BeDone And Have Agility
  • 38. You Don’t Need Project ManagersIn Agile
  • 39. You Don’t Need Project ManagersTo Have Agility
  • 40. - Old People- Stagnation- ImposingValues- No Responsibility- Estimating is a waste- Pair Programming- Can’t Scalehttp://blog.assembla.com/assemblablog/tabid/12618/bid/87899/Seven-Things-I-Hate-About-Agile.aspx
  • 41. 1) Stop Calling Things Agile
  • 42. 2) Understand the forces at play
  • 43. 3) Reframe the question
  • 44. Software is our craft TM8th LightCory Foy (@cory_foy)foyc@coryfoy.comwww.coryfoy.com