Your SlideShare is downloading. ×
Lean development based on scrum
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

Lean development based on scrum


Published on

Realizing a solution is no longer enough …

Realizing a solution is no longer enough

Imagine yourself a clever software developer, sitting in his room, working deep at night. For weeks, months, he's breeding on that one perfect solution. He codes like crazy, refactors, rebuilds. He wants it to be perfect. May be he showed it to some of his friends and they told him they like the idea. After a lot of hard work the solution is finally ready. Excited and full of expectations he introduces it to the market. Soon, all his effort will pay off, money will start flowing. Unfortunately, nobody seems to be interested in using the product and for sure they don't want to pay for it. What went wrong? How to prevent? During the lecture we will discuss how to cut this big salami into small pieces by using a lean development approach based on Scrum.

Published in: Business, Technology

  • Be the first to comment

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 1. Lean developmentbased on
  • 2. Gartner  studies  suggest  that  75%  of  all  US  IT  projects  are  considered  to  be  failures.    The  solu:ons  fundamentally  did  not  do  what  was  agreed.  Or  they  missed  deadlines.  And/or  came  in  over  budget.  Half  of  the  projects  exceeded  budget  by  200%!  WHY?  
  • 3. I’m a Dutch guy who fellin love with Poland and …Picture source:
  • 4. What do you want to  learn    today?
  • 5. Realizing  a  solu;on  is  not  enough  
  • 6. Thinking  what  the  customer  needs  ….  
  • 7. It’s good todream bigPicture source:
  • 8. But it allstartswith little stepsSource:
  • 9. The  road  to  success  Source: ATBREAK
  • 10. The Toyota way•  “ContinuousImprovement” (kaizen)Challenging everything bycreating an atmosphere ofcontinuous learning and anenvironment that embraceschange.•  “Respect for People“Which is essential to createsuch an environment
  • 11. Manifesto for Agile Software DevelopmentWe are uncovering better ways of developing software by doing itand helping others do it. Through this work we have come to value:•  Individuals and interactions over processes and tools•  Working software over comprehensive documentation•  Customer collaboration over contract negotiation•  Responding to change over following a planThat is, while there is value in the items on the right, we value theitems on the left more.Source:  
  • 12. Too many startups begin with    an ideafor a productthat they think peoplewant
  • 13. The lean startup methodology•  Eliminate uncertainty•  Work smarter not harder•  Develop an MVP• Validated learningSource:  
  • 14. The  lean  startup  
  • 15. Iterative development withSCRUM
  • 16. Scrum  is  an  Agile  soJware  development  framework  Scrum is an agile software development framework. Workis structured in cycles of work called sprints, iterations ofwork that are typically two to four weeks in duration. Duringeach sprint, teams pull from a prioritized list of customerrequirements, called user stories, so that the featuresthat are developed first are of the highest value to thecustomer. At the end of each sprint, a potentiallyshippable product is delivered.Image source:
  • 17. Three Scrum roles• Product owner:  responsible for thebusiness value of the project• ScrumMaster:  ensures that the team isfunctional and productive• Team:  self-organizes to get the workdone
  • 18. Four ceremonies• Sprint planning: the team meets with the productowner to choose a set of work to deliver during asprint• Daily scrum: the team meets each day to sharestruggles and progress• Sprint reviews: the team demonstrates to theproduct owner what it has completed during the sprint• Sprint retrospectives: the team looks for waysto improve the product and the process
  • 19. Three Artefacts• Product backlog: ordered list of ideas forthe product• Sprint backlog: set of work from theproduct backlog that the team agrees to completein a sprint, broken into tasks• Product Increment: required result ofevery sprint. It is an integrated version of theproduct, kept at high enough quality to beshippable
  • 20. Het  scrumproces  Source:  
  • 21. How  do  you  eat  a  salami?  
  • 22. Contact details:@ peter.horsten@goyello.com8 http://goyello.com8 http://blog.goyello.com8 http://petersopinion.com TO YOUThanks for your attention!Feel free to contact and follow!Or ask questions today, I don’t bite ....Goyello Sp. z o.o.Al. Grunwaldzka 47280-309 Gdansk