• 15 years doing ScrumBut

  • First things first… What is Scrum?

  • Scrum But

    ScrumButs are reasons why teams can’t take full advantage of Scrum to solve their problems and realize the full benefits of product development using Scrum.

  • Is it worth it?

    • (2000) TDEXA
    • (2006) OmniTI — NYC
    • (2011) SoftLogik
    • (2014) CIMAT Thesis
    • (2015) ITSZaS
  • TDEXA

  • OmniTI

  • SoftLogik

  • CIMAT

  • ITSZaS

  • Common mistakes

  • Summary:

  • Static View

    • The Scrum Team
      • The Product Owner
      • The Development Team
      • The Scrum Master
    • Scrum Events
      • The Sprint
      • Sprint Planning
      • Daily Scrum
      • Sprint Review
      • Sprint Retrospective
    • Scrum Artifacts
      • Product Backlog
      • Sprint Backlog
      • Increment
    • Artifact Transparency
      • Definition of “Done”
  • A ScrumBut has a particular syntax: (ScrumBut)(Reason)(Workaround)

    • “(We use Scrum, but) (having a Daily Scrum every day is too much overhead,) (so we only have one per week.)”

    • “(We use Scrum, but) (Retrospectives are a waste of time,) (so we don’t do them.)”

    • “(We use Scrum, but) (we can’t build a piece of functionality in a month,) (so our Sprints are 6 weeks long.)”

    • “(We use Scrum, but) (sometimes our managers give us special tasks,) (so we don’t always have time to meet our definition of done.)”

  • 86% of projects are challenged or failed.

  • Waterfall is a misunderstanding from the beginning

    Waterfall was supposedly “invented” by the paper “Managing the Development of Large Software Systems” by Dr. Winston W. Royce in 1970

    I believe in this concept, but the implementation described above is risky and invites failure.

  • Mismatch between the model and the problem

    Is a baby a smaller version of an adult?

  • Summary

  • Results

    • Empresa de 5 anios
    • Sistem instaled in over 14,000 schools around the country.
  • + Things we did Right and want to repeat:

    • Commited Team
    • Continuous communication with customers
    • Fulltime software developers
  • - Things we did wrong and want to avoid:

    • We didn´t have a mentor. (Scrum Master)
    • We didn´t use automated tools. (Continuous Integration)
    • We didn´t search for bigger markets
  • Summary

  • + Things we want to repeat

    • Having free beer in the office
    • Experienced developers (phds) Open source contribution.
    • Profitable
  • - Things we want to avoid

    • Arrogance
    • Wrong use of methodologies
  • Summary

  • Results

    • The best software company
    • Average it makes projects in 66% the time it takes their competition.
    • Wins every Government Contract it goes to. Saving the government between MXN $1M - 3M
    • The most profitable company in Zacatecas per employee.
  • + Things we did right and want to do again.

    • Incubation process in Scrum (6 months)
    • We didin´t impose the methodology it Evolved from developers themselves.
    • We used automated tools for everything
      • Continuous Integration
      • Code coverage
      • unit testing
  • - Things we did wrong and want to avoid

    • Softlogik stopped learning… ie not being agile.
    • Top management wasn´t commited to the methodology.
    • We didn´t do Continuous Deployment
  • Summary

  • Results

    • 100% Thesis finished on time or before time.
    • With projections and metrics.
  • + Things we did well and want to keep doing.

    • We use metrics to manage the project
    • take the right corrective actions on time.
  • - Things we want to avoid

    • sometimes we don´t work as a team.
    • we haven´t been able to transmit the method in the whole organization.
  • Summary

  • Results

    • Students with commitment
    • Teachers with appreciation
  • + Things we want to repeat

    • Fulltime during two weeks
    • Configuration of servers to be locally available
    • Mentoring for 6 months
  • - Things we want to avoid

    • Part time of students and teachers
    • lack of alignment between Top Management and the Software Factory.
  • Not using code repository?

  • Not using pair progamming / code reviews?

  • Not writing unit-tests?

  • Lack of automatization

    • pre-commit-hooks
  • not using Continuous Integration?

  • Changing the dates of the Sprint Review

  • Doing Scrum But

  • Doing Scrum by the book after 3 months.

    Stop Learing

  • In the same vein:

    • CMM was born by studying NASA, IBM, DoD
    • PMBOK was born to manage Bridge construction

    Our organizations aren´t like those!!

{"cards":[{"_id":"51088168cba5eb39ba000050","treeId":"5108814ecba5eb39ba00004e","seq":1777573,"position":1,"parentId":null,"content":"# 15 years doing ScrumBut"},{"_id":"510aa1a372d0f5fe88000083","treeId":"5108814ecba5eb39ba00004e","seq":1777910,"position":1.25,"parentId":null,"content":"# First things first... What is Scrum?"},{"_id":"510aa2dd72d0f5fe88000084","treeId":"5108814ecba5eb39ba00004e","seq":4741860,"position":1,"parentId":"510aa1a372d0f5fe88000083","content":"# Summary:\n![](http://agilitrix.com/wp-content/uploads/2009/08/agile-scrum-project-cycle.jpg)"},{"_id":"5124b6093092adccb000005a","treeId":"5108814ecba5eb39ba00004e","seq":1788682,"position":2,"parentId":"510aa1a372d0f5fe88000083","content":"## Static View\n\n* The Scrum Team\n * The Product Owner\n * The Development Team\n * The Scrum Master\n* Scrum Events\n * The Sprint\n * Sprint Planning\n * Daily Scrum\n * Sprint Review\n * Sprint Retrospective\n* Scrum Artifacts\n * Product Backlog\n * Sprint Backlog\n * Increment\n* Artifact Transparency\n * Definition of \"Done\""},{"_id":"5109ab7f72d0f5fe88000061","treeId":"5108814ecba5eb39ba00004e","seq":1777074,"position":1.5,"parentId":null,"content":"# Scrum But\n*ScrumButs are reasons why teams can’t take full advantage of Scrum to solve their problems and realize the full benefits of product development using Scrum.*"},{"_id":"5109f91772d0f5fe8800006e","treeId":"5108814ecba5eb39ba00004e","seq":7683998,"position":1,"parentId":"5109ab7f72d0f5fe88000061","content":"A ScrumBut has a particular syntax: **(ScrumBut)(Reason)(Workaround)**\n\n\n* \"(We use Scrum, but) (having a Daily Scrum every day is too much overhead,) (so we only have one per week.)\"\n\n* \"(We use Scrum, but) (Retrospectives are a waste of time,) (so we don't do them.)\"\n\n* \"(We use Scrum, but) (we can't build a piece of functionality in a month,) (so our Sprints are 6 weeks long.)\"\n\n* \"(We use Scrum, but) (sometimes our managers give us special tasks,) (so we don't always have time to meet our definition of done.)\""},{"_id":"5109fc5572d0f5fe8800006f","treeId":"5108814ecba5eb39ba00004e","seq":1777091,"position":1.75,"parentId":null,"content":"# Is it worth it?"},{"_id":"5109fd0772d0f5fe88000070","treeId":"5108814ecba5eb39ba00004e","seq":7684005,"position":1,"parentId":"5109fc5572d0f5fe8800006f","content":"86% of projects are challenged or failed.\n\n![](http://www.mountaingoatsoftware.com/uploads/blog/Agile-Waterfall-Success-Failure-Rates.jpg)"},{"_id":"510a9b6f72d0f5fe88000082","treeId":"5108814ecba5eb39ba00004e","seq":1777900,"position":2,"parentId":"5109fc5572d0f5fe8800006f","content":"# Waterfall is a misunderstanding from the beginning\n\n*Waterfall was supposedly “invented” by the paper “Managing the Development of Large Software Systems” by Dr. Winston W. Royce in 1970*\n\n> I believe in this concept, but the implementation described above is risky and invites failure."},{"_id":"510aea7372d0f5fe88000086","treeId":"5108814ecba5eb39ba00004e","seq":7691183,"position":3,"parentId":"5109fc5572d0f5fe8800006f","content":"# Mismatch between the model and the problem\nIs a baby a smaller version of an adult?"},{"_id":"510aedfe72d0f5fe88000087","treeId":"5108814ecba5eb39ba00004e","seq":1778024,"position":1,"parentId":"510aea7372d0f5fe88000086","content":"![](http://s3-ec.buzzfed.com/static/2014-12/9/7/enhanced/webdr07/enhanced-15692-1418127385-8.jpg)"},{"_id":"510aeef272d0f5fe88000089","treeId":"5108814ecba5eb39ba00004e","seq":7691222,"position":2,"parentId":"510aea7372d0f5fe88000086","content":"In the same vein:\n* CMM was born by studying NASA, IBM, DoD\n* PMBOK was born to manage Bridge construction\n\nOur organizations aren´t like those!!"},{"_id":"51088569cba5eb39ba000051","treeId":"5108814ecba5eb39ba00004e","seq":7691334,"position":2,"parentId":null,"content":"* (2000) TDEXA\n* (2006) OmniTI -- NYC\n* (2011) SoftLogik\n* (2014) CIMAT Thesis\n* (2015) ITSZaS"},{"_id":"5109350acba5eb39ba000053","treeId":"5108814ecba5eb39ba00004e","seq":1777609,"position":3,"parentId":null,"content":"# TDEXA"},{"_id":"510a0f2b72d0f5fe88000074","treeId":"5108814ecba5eb39ba00004e","seq":3114872,"position":0.25,"parentId":"5109350acba5eb39ba000053","content":"# Summary\n![](https://scontent-dfw1-1.xx.fbcdn.net/hphotos-xaf1/v/t1.0-9/29220_420904769922_6938188_n.jpg?oh=ce9031fde63e21308697fc33564fd3af&oe=5636B0B0)"},{"_id":"51093d7acba5eb39ba000055","treeId":"5108814ecba5eb39ba00004e","seq":1777615,"position":0.5,"parentId":"5109350acba5eb39ba000053","content":"# Results\n* Empresa de 5 anios\n* Sistem instaled in over 14,000 schools around the country.\n"},{"_id":"5109b04c72d0f5fe88000062","treeId":"5108814ecba5eb39ba00004e","seq":7691338,"position":0.75,"parentId":"5109350acba5eb39ba000053","content":"# + Things we did Right and want to repeat:\n* Commited Team\n* Continuous communication with customers\n* Fulltime software developers"},{"_id":"51093c50cba5eb39ba000054","treeId":"5108814ecba5eb39ba00004e","seq":7691340,"position":1,"parentId":"5109350acba5eb39ba000053","content":"## - Things we did wrong and want to avoid:\n* We didn´t have a mentor. (Scrum Master)\n* We didn´t use automated tools. (Continuous Integration)\n* We didn´t search for bigger markets"},{"_id":"510a031d72d0f5fe88000071","treeId":"5108814ecba5eb39ba00004e","seq":1777139,"position":3.5,"parentId":null,"content":"# OmniTI"},{"_id":"510a8cbd72d0f5fe88000081","treeId":"5108814ecba5eb39ba00004e","seq":3114853,"position":0.5,"parentId":"510a031d72d0f5fe88000071","content":"# Summary\n![](http://s.omniti.net/i/content/logo.gif)"},{"_id":"510a03be72d0f5fe88000072","treeId":"5108814ecba5eb39ba00004e","seq":7691345,"position":1,"parentId":"510a031d72d0f5fe88000071","content":"## + Things we want to repeat\n* Having free beer in the office\n* Experienced developers (phds) Open source contribution.\n* Profitable"},{"_id":"510a05f572d0f5fe88000073","treeId":"5108814ecba5eb39ba00004e","seq":7691346,"position":2,"parentId":"510a031d72d0f5fe88000071","content":"## - Things we want to avoid\n* Arrogance\n* Wrong use of methodologies"},{"_id":"51093ebccba5eb39ba000056","treeId":"5108814ecba5eb39ba00004e","seq":1775949,"position":4,"parentId":null,"content":"# SoftLogik"},{"_id":"510a21a072d0f5fe88000075","treeId":"5108814ecba5eb39ba00004e","seq":3114882,"position":0.5,"parentId":"51093ebccba5eb39ba000056","content":"## Summary\n![](http://www.softlogik.mx/wp-content/uploads/2014/10/Logo_SK_Tranpartente1.png)"},{"_id":"5109bcec72d0f5fe88000063","treeId":"5108814ecba5eb39ba00004e","seq":7691350,"position":1,"parentId":"51093ebccba5eb39ba000056","content":"# Results\n* The best software company\n* Average it makes projects in 66% the time it takes their competition.\n* Wins every Government Contract it goes to. Saving the government between MXN $1M - 3M\n* The most profitable company in Zacatecas per employee."},{"_id":"5109c4fe72d0f5fe88000064","treeId":"5108814ecba5eb39ba00004e","seq":7691356,"position":2,"parentId":"51093ebccba5eb39ba000056","content":"# + Things we did right and want to do again.\n* Incubation process in Scrum (6 months)\n* We didin´t impose the methodology it Evolved from developers themselves.\n* We used automated tools for everything\n * Continuous Integration\n * Code coverage\n * unit testing"},{"_id":"5109d05f72d0f5fe88000065","treeId":"5108814ecba5eb39ba00004e","seq":7691357,"position":3,"parentId":"51093ebccba5eb39ba000056","content":"## - Things we did wrong and want to avoid\n* Softlogik stopped learning... ie not being agile.\n* Top management wasn´t commited to the methodology.\n* We didn´t do Continuous Deployment"},{"_id":"5109d53672d0f5fe88000067","treeId":"5108814ecba5eb39ba00004e","seq":1776914,"position":4.5,"parentId":null,"content":"# CIMAT"},{"_id":"510a27ef72d0f5fe88000076","treeId":"5108814ecba5eb39ba00004e","seq":3114916,"position":0.5,"parentId":"5109d53672d0f5fe88000067","content":"# Summary\n![](http://zacatecas.startupweekend.org/files/2014/07/Cimat-bueno.png)"},{"_id":"5109d7e372d0f5fe88000068","treeId":"5108814ecba5eb39ba00004e","seq":7694841,"position":1,"parentId":"5109d53672d0f5fe88000067","content":"## Results\n* 100% Thesis finished on time or before time.\n* With projections and metrics."},{"_id":"5109dd0a72d0f5fe88000069","treeId":"5108814ecba5eb39ba00004e","seq":7694894,"position":2,"parentId":"5109d53672d0f5fe88000067","content":"## + Things we did well and want to keep doing.\n* We use metrics to manage the project\n* take the right corrective actions on time."},{"_id":"5109e1cb72d0f5fe8800006a","treeId":"5108814ecba5eb39ba00004e","seq":7694901,"position":3,"parentId":"5109d53672d0f5fe88000067","content":"## - Things we want to avoid\n* sometimes we don´t work as a team.\n* we haven´t been able to transmit the method in the whole organization."},{"_id":"51094038cba5eb39ba000057","treeId":"5108814ecba5eb39ba00004e","seq":1775954,"position":5,"parentId":null,"content":"# ITSZaS"},{"_id":"510a47eb72d0f5fe88000077","treeId":"5108814ecba5eb39ba00004e","seq":3114896,"position":0.5,"parentId":"51094038cba5eb39ba000057","content":"# Summary\n![](http://www.itszas.edu.mx/nueva/img/logos2.png)"},{"_id":"5109e7d372d0f5fe8800006b","treeId":"5108814ecba5eb39ba00004e","seq":7694939,"position":1,"parentId":"51094038cba5eb39ba000057","content":"# Results\n* Students with commitment\n* Teachers with appreciation "},{"_id":"5109e8cf72d0f5fe8800006c","treeId":"5108814ecba5eb39ba00004e","seq":7694940,"position":2,"parentId":"51094038cba5eb39ba000057","content":"# + Things we want to repeat\n* Fulltime during two weeks\n* Configuration of servers to be locally available\n* Mentoring for 6 months"},{"_id":"5109edbc72d0f5fe8800006d","treeId":"5108814ecba5eb39ba00004e","seq":7694941,"position":3,"parentId":"51094038cba5eb39ba000057","content":"## - Things we want to avoid\n* Part time of students and teachers\n* lack of alignment between Top Management and the Software Factory."},{"_id":"510a594d72d0f5fe88000078","treeId":"5108814ecba5eb39ba00004e","seq":1777652,"position":6,"parentId":null,"content":"# Common mistakes"},{"_id":"510a59c272d0f5fe88000079","treeId":"5108814ecba5eb39ba00004e","seq":7694945,"position":1,"parentId":"510a594d72d0f5fe88000078","content":"## Not using code repository?"},{"_id":"510a5aab72d0f5fe8800007a","treeId":"5108814ecba5eb39ba00004e","seq":7694948,"position":2,"parentId":"510a594d72d0f5fe88000078","content":"## Not using pair progamming / code reviews?"},{"_id":"510a5b6a72d0f5fe8800007b","treeId":"5108814ecba5eb39ba00004e","seq":7694949,"position":3,"parentId":"510a594d72d0f5fe88000078","content":"## Not writing unit-tests?"},{"_id":"510a60e172d0f5fe88000080","treeId":"5108814ecba5eb39ba00004e","seq":7694952,"position":3.5,"parentId":"510a594d72d0f5fe88000078","content":"## Lack of automatization\n* pre-commit-hooks"},{"_id":"510a5bec72d0f5fe8800007c","treeId":"5108814ecba5eb39ba00004e","seq":7694953,"position":4,"parentId":"510a594d72d0f5fe88000078","content":"## not using Continuous Integration?"},{"_id":"510a5c6272d0f5fe8800007d","treeId":"5108814ecba5eb39ba00004e","seq":7694954,"position":5,"parentId":"510a594d72d0f5fe88000078","content":"## Changing the dates of the Sprint Review"},{"_id":"510a5d6172d0f5fe8800007e","treeId":"5108814ecba5eb39ba00004e","seq":7694955,"position":6,"parentId":"510a594d72d0f5fe88000078","content":"# Doing Scrum But"},{"_id":"510a5f8672d0f5fe8800007f","treeId":"5108814ecba5eb39ba00004e","seq":1777681,"position":7,"parentId":"510a594d72d0f5fe88000078","content":"# Doing Scrum by the book after 3 months.\nStop Learing"}],"tree":{"_id":"5108814ecba5eb39ba00004e","name":"15 years doing ScrumBut","publicUrl":"15-years-doing-scrumbut"}}