How to Adopt Agile at Your Organization
Upcoming SlideShare
Loading in...5
×
 

How to Adopt Agile at Your Organization

on

  • 13,675 views

 

Statistics

Views

Total Views
13,675
Views on SlideShare
4,178
Embed Views
9,497

Actions

Likes
6
Downloads
86
Comments
0

18 Embeds 9,497

http://blog.rayapps.com 9284
http://localhost:4000 71
http://orana.info 45
http://localhost 45
http://translate.googleusercontent.com 14
http://translate.googleusercontent.com 14
url_unknown 6
http://webcache.googleusercontent.com 3
http://feeds.feedburner.com 3
http://www.slideshare.net 3
http://twitter.com 2
https://www.google.com 1
http://www.365dailyjournal.com 1
http://www.newsblur.com 1
http://honyaku.yahoofs.jp 1
http://www.hanrss.com 1
http://paper.li 1
http://www.linkedin.com 1
More...

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

CC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

How to Adopt Agile at Your Organization How to Adopt Agile at Your Organization Presentation Transcript

  • Agile Riga Day 2011 How to Adopt Agileat Your OrganizationChallenges and Success Stories
  • Agile Open-Technology source Ruby Raimonds Simanovskis JavaScript Social github.com/rsim @rsim
  • I heard about Agile...
  • But what is Agile?
  • But what is Agile?
  • But what is Agile?
  • But what is Agile?
  • But what is Agile?
  • But what is Agile?
  • But what is Agile?
  • But what is Agile?
  • But what is Agile?
  • But what is Agile?
  • 0 Why to start Agile? What are the problems we want to solve? Do we acknowledge that we have problems?
  • We want toDevelop software faster Be responsive to changesGet higher quality result
  • Challenges before starting • “Why to change?” • “We are already agile”change? Why to • “Just another buzzword” is Everything • “Our managers don’t allow to be agile” already more or • “Our employees don’t take less OK responsibility” • “Our customers want waterfall”
  • Challenges before starting • “Why to change?” • “We are already agile” • “Just another buzzword” We are already • “Our managers don’t allow to be agile” Agile! • “Our employees don’t take responsibility” • “Our customers want waterfall”
  • Challenges before starting • “Why to change?” • “We are already agile” • “Just another buzzword” Just another • “Our managers don’t allow to be agile” buzzword... • “Our employees don’t take responsibility” • “Our customers want waterfall”
  • Challenges before starting • “Why to change?” • “We are already agile” • Our managers “Just another buzzword” • “Our managers don’t allow to beto don’t allow us agile” • “Our employees don’t take :( be agile responsibility” • “Our customers want waterfall”
  • Challenges before starting • “Why to change?” • “We are already agile” • Our employees “Just another buzzword” don’t take • “Our managers don’t allow to be agile” responsibility :( • “Our employees don’t take responsibility” • “Our customers want waterfall”
  • Challenges before starting • “Why to change?” • “We are already agile” • Our customers “Just another buzzword” are demanding • “Our managers don’t allow to be agile” • “Our employees don’t take :( waterfall responsibility” • “Our customers want waterfall”
  • OK, ready to start!
  • Big bang approach!
  • OK, some ramp up
  • But in reality...
  • There will be failures
  • Adopt iterativelypractice by practice
  • 1 Start with values and principlesIndividuals and Processes over interactions and tools Working Comprehensive over software documentation Customer Contract over collaboration negotiationResponding to Following over change a plan
  • 2 Start with iterations Create Self-organizeda backlog everyday Plan in work Demonstrate iterations iteration result Regular 1 - 4 weeks Retrospect review of and priorities improve
  • Challengesafter starting
  • Just renaming thingsProject Manager Scrum Master Project phases Iterations Tasks in MS Project plan Backlog items Requirements specification User stories Detailed design specification ... we still need this ...
  • Performing rituals withoutunderstanding the reason What did you do? Let’s go to lunch! Nothing special You guys The same as usual are cool!
  • Overcustomizing practicesIteration 1 Iteration 2 Iteration 3 Iteration 4 Require Design Testing ments & coding Require Design Testing ments & coding Require Design ments & coding
  • False sense of early finish We’re doing Scrum! And lean as well! Yeah! We’re so Agile!
  • 3 Involve customer Explain values and principles Explain iterations and backlog Explain product owner role and help with it
  • Lo-fi communications:user stories, index cards, whiteboard Speak more write less
  • Lo-fi communications:user stories, index cards, whiteboard Transparency and honesty
  • Challenges Agile just insidedevelopment team without customer involvement
  • ChallengesCustomer does not have time
  • Challenges Development team andcustomer each have own backlogs and priorities
  • ChallengesCustomer collaboration and scope management in fixed scope / fixed price contracts
  • 4 Implement Quality Done is done
  • Testing Not a role but functionIntegrated into development Automated
  • Continuous integration Observe code repositoryPublish Buildresults product Execute tests
  • Zero bugs
  • ChallengesBacklog Work in process Done
  • Growing work in processBacklog Work in process Done
  • Growing work in processBacklog Work in process Done
  • UsabilityDone means not just doable but also usable
  • 5 Technical Excellence Pair Programming Is it 10 PRINT “Hello” #@%$^& good? 20 GOTO 10
  • Test Driven Development
  • Challenges• “Why to change?”• “We are already agile”• Technical practices “Just another buzzword”• much harder than “Our managers don’t allow to be agile”• “soft” practices :( “Our employees don’t take responsibility”• “Our customers want waterfall”
  • Challenges• “Why to change?”• “We are already agile”• “Just another buzzword” much Twice as• “Our managers don’t allow to be agile” work!• “Our employees don’t take responsibility”• “Our customers want waterfall”
  • Challenges• “Why to change?”• “We are already agile”allowed I’m not• “Just another buzzword” to do refactoring• “Our managers don’t allow to beon Need don’t work to take agile”• “Our employees new features responsibility”• “Our customers want waterfall”
  • Challenges• “Why to change?”• “We are already agile”• Legacy code... “Just another buzzword”• “Our managerstechnology... Bad don’t allow to be agile”• “Our employees don’tdo TDD Can’t take responsibility”• “Our customers want waterfall”
  • 6 Readiness for change Anything can be changed Agile operations Minimize cycle time to production Source code always ready for deployment Automated deployments
  • ChallengesDevelopment Operations
  • 7 Staying agile