Your SlideShare is downloading. ×
Why practices are not as important as principles?
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Why practices are not as important as principles?

3,233

Published on

You might wonder why is not that easy to adopt agile engineering practices and achieve technical excellence. When we think at practices we tend to think at simple things: pinning on the fridge with a …

You might wonder why is not that easy to adopt agile engineering practices and achieve technical excellence. When we think at practices we tend to think at simple things: pinning on the fridge with a magnet the list of shopping items to buy, having a clear prioritised list of things to do, and work that in order… why is then that with Agile practices is not working that easy? What is that Teams are not getting right? Is it that we don’t have the right Software tools? Or we are not collocated? The Agile dilemma is: “To effectively apply practices, you need to understand the principle, to understand the principles you need to practice!”, simply… complicated!

Published in: Technology
0 Comments
12 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
3,233
On Slideshare
0
From Embeds
0
Number of Embeds
13
Actions
Shares
0
Downloads
93
Comments
0
Likes
12
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. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.Why Practices are not asimportant as Principles?Simply... Complicated!Tuesday, April 23, 13
  • 2. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.Andrea TomasiniAgile Coach & Trainerandrea.tomasini@agile42.com@tumma72@agile42/coachesTuesday, April 23, 13
  • 3. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.principle |ˈprɪnsɪp(ə)l|noun1 a fundamental truth or proposition that serves as thefoundation for a system of belief or behavior or for achain of reasoning: the basic principles of justice.• (usu. principles) a rule or belief governing onesbehavior: struggling to be true to their own principles | [ massnoun ] : she resigned over a matter of principle.Tuesday, April 23, 13
  • 4. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.practice |ˈpraktɪs|noun [ mass noun ]1 the actual application or use of an idea, belief, ormethod, as opposed to theories relating to it: theprinciples and practice of teaching3 repeated exercise in or performance of an activityor skill so as to acquire or maintain proficiency in it:it must have taken a lot of practice to become sofluent.Tuesday, April 23, 13
  • 5. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.Practices...Tuesday, April 23, 13
  • 6. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.Tuesday, April 23, 13
  • 7. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.Daily Stand-up MeetingA common practice used by many agile teams. In Scrum isoften used for the Daily ScrumTuesday, April 23, 13
  • 8. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.Daily Stand-up Meeting•Practice: the Daily Stand-Up meeting is aboutmeeting while standing. It’s a practice, often used byTeams developing software following an Agileapproach. By standing the meeting will take less time,and will be more focused, as standing for long it’s notcomfortable.Tuesday, April 23, 13
  • 9. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.and now... you!what did you doyesterday?Daily Standup MeetingControlTuesday, April 23, 13
  • 10. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.Daily Stand-up Meeting•Principle: working in complex environment, withrapid and not always predictable changes, and a lot ofdependencies, requires focusing constantly on thegoal to succeed. For this reason, it is important tointroduce regular check that allows a Team of peersto re-asses regularly the status of progress and decidehow to move forward and improveTuesday, April 23, 13
  • 11. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.Planning MeetingThe moment in which Agile Teams decide what to do andhow to do it...Tuesday, April 23, 13
  • 12. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.Planning Meeting•Practice: The whole Team meets to agree on a goalfor the next iteration of work. During the meeting -which is normally time-boxed - the Team decideswhat will be transformed into working software, outof a list of prepared items called Backlog, whichshould reflect the order better suited to achieve thegoal.Tuesday, April 23, 13
  • 13. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.Hey, that’senough Stop!Planning MeetingShootingTuesday, April 23, 13
  • 14. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.Planning Meeting•Principle: Agile Teams deliver working andvaluable software at regular interval. In order toreduce the impact of changes on the developmentplan, agile Teams plan in detail at regular interval oftime - normally between 1-4 weeks.•Assumption: the length of the iteration is such that it isacceptable for the Business to wait the next iteration to plan forchanges, so to reduce interruptions.Tuesday, April 23, 13
  • 15. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.Pair-ProgrammingAn eXtreme Programming practice to improve code qualityand design...Tuesday, April 23, 13
  • 16. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.Pair Programming / Pairing•Practice: all code to be sent into production iscreated by two people working together at a singlecomputer. Pair programming increases softwarequality without impacting time to deliver.Tuesday, April 23, 13
  • 17. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.I need help, whowants to pair?Me! I’d like tolearn somethingPair Programmingfor nothingfor free!Tuesday, April 23, 13
  • 18. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.Pair Programming / Pairing•Principle: It is counter intuitive, but 2 peopleworking at a single computer will add as muchfunctionality as two working separately except that itwill be much higher in quality. With increased qualitycomes big savings later in the project.•Note: One thing pair programming is not is mentoring. Ateacher-stundent relationship feels very different from two peopleworking together as equals even if one has significantly moreexperience.http://www.extremeprogramming.org/rules/pair.htmlTuesday, April 23, 13
  • 19. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.Test Driven Development (TDD)An eXtreme Programming practice to create simple andeffective design, by starting to write tests...Tuesday, April 23, 13
  • 20. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.Test Driven Development•Practice: is a software development process thatrelies on the repetition of a very short developmentcycle: first the developer writes an (initially failing)automated test case that defines a desiredimprovement or new function, then produces theminimum amount of code to pass that test, andfinally refactors the new code to acceptable standards.Tuesday, April 23, 13
  • 21. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.I am really eagerto try TDD on thisnew designApparently this design is toocomplicated for TDD... I don’t seemto be able to write tests first.Test Driven DevelopmentDesignTestingTuesday, April 23, 13
  • 22. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.Test Driven Development•Principle: In the spirit of simplicity - as the art ofmaximizing the amount of work not done - agileteams focus on implementing the minimal amount ofcode needed to fulfills the tests. In this respect thedesign and the architecture will be emerging out ofthe need of fulfilling those tests. By doing so the codewill remain simple, easier to maintain and evolve.Tuesday, April 23, 13
  • 23. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.Continuous Integration (CI)An eXtreme Programming practice to accelerate feedbackloop and learning...Tuesday, April 23, 13
  • 24. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.Continuous Integration•Practice: is the practice, in software engineering, ofmerging all developer workspaces with a sharedmainline several times a day. It can be seen as anintensification of practices of periodic integrationadvocated by earlier published methods ofincremental and iterative software development.Tuesday, April 23, 13
  • 25. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.Continuous IntegrationDis-Tuesday, April 23, 13
  • 26. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.Continuous Integration•Principle: Agile teams are seeking constantly toaccelerate feedback loops, so to learn faster. Inparticular teams value validated learning more thanassumptions based learning. Through discipline it ispossible to come to reproduce ready-to-ship softwareas often as possible. In order to validate the learningof having understood what needed to be done,through stakeholders’ feedback.Tuesday, April 23, 13
  • 27. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.Review MeetingAgile Team meet regularly to review the status of theirProduct evolution and decide what to deliver next...Tuesday, April 23, 13
  • 28. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.Review Meeting•Practice: The team and the Product Owner meet atthe end of every iteration and assess the results ofwhat was achieved. At the meeting may attend alsosome of the stakeholder, so that they can provideadditional feedback.Tuesday, April 23, 13
  • 29. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.Come on guys,stay calm... believein what you didRejected! that’snot what I want...ProductReviewComplianceTuesday, April 23, 13
  • 30. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.Review Meeting•Principle: through iterative and incrementaldevelopment of a product it is possible to learn whatis really needed and what not. By reviewing the statusof the product development regularly against thecurrently planned value to deliver, the Team canincrease its effectiveness and learn what is reallyneeded to the stakeholders.Tuesday, April 23, 13
  • 31. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.Understanding the Principles...Tuesday, April 23, 13
  • 32. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.Pull principleIterative&IncrementalEmpirical Process ControlLean ThinkingAgile Reading GlassesTuesday, April 23, 13
  • 33. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.Empirical Process controlAgile is based on empirical control, through transparency, inspection andadaptation the best processes are emerging while doing, and only retrospectively itis possible to recognize successful adaptation from non successful onesTuesday, April 23, 13
  • 34. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2010.Defined Process Control Production-based processTuesday, April 23, 13
  • 35. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2010.Let’s make a test...Complexity: the amount of agents in playand their dependencies are so many thatit’s impossible to predict the state upfront> 60!Tuesday, April 23, 13
  • 36. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2010.Empirical Process Control R&D based processTuesday, April 23, 13
  • 37. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.Pull PrincipleAgile approaches are based on pull principle which allows self-organizing teams topull in work and knowledge as needed in order to deliver valuable quality softwareTuesday, April 23, 13
  • 38. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.PushPullIndividual TeamEnforcementCollaborationComplianceFocusonvalueTuesday, April 23, 13
  • 39. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.Lean ThinkingLean Thinking inspired process improvement through constant observation of theunevenness in a flow, resources or people overburdening and elimination ofwasteful activitiesTuesday, April 23, 13
  • 40. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2010.Overburden(無理:muri)do not overload yourPeopleTuesday, April 23, 13
  • 41. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2010.UnnecessaryVariations(斑: mura) keep the FlowEvenTuesday, April 23, 13
  • 42. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2010.WastefulActivities(無駄: muda)remove non value addingActivitiesTuesday, April 23, 13
  • 43. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.Iterative & IncrementalDelivering a product in subsequent iterative releases, not only improves the explicitquality of it, it also allows everybody involved in its development as well as everystakeholder, to learn better what is really needed to support a business visionTuesday, April 23, 13
  • 44. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.VerifyIdeaImproveitAddValueReadyitDone!1 2 3 4 5Iterative & Incremental0% 100%Tuesday, April 23, 13
  • 45. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.EveryIncrement:✓is inspect-able✓adds value✓it’s high qualityReady toship!Tuesday, April 23, 13
  • 46. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.So what?Tuesday, April 23, 13
  • 47. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.This old axe, is stilldoing a pretty goodjob after all...Hey, you should try the newChainsaw, it’s much better...is much heavier, and cuts noway better than my old axe...not all new things are betterafter all...Tuesday, April 23, 13
  • 48. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.What’s the recipe?1) Focus on Value, notcompliance to rules!Tuesday, April 23, 13
  • 49. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.What’s the recipe?2) Understand the Principlesand then learn the PracticesTuesday, April 23, 13
  • 50. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.What’s the recipe?3) Assimilate the Principles byPracticing more, and improvethe Practices byconceptualizing better thePrinciplesTuesday, April 23, 13
  • 51. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.What’s the recipe?4) Build your own Practices,as you learned to live thePrinciplesTuesday, April 23, 13
  • 52. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.Thank You!Tuesday, April 23, 13
  • 53. agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.More food for thought...http://slideshare.net/tumma72Now inCroatian!Tuesday, April 23, 13

×