Scrum Guide Refresh July 2016 - Scrum Pulse Episode #14

Поділитися
Вставка
  • Опубліковано 4 лис 2024

КОМЕНТАРІ • 6

  • @boucarba2239
    @boucarba2239 5 років тому

    great debate and a wondefull explanation of scrum guide contents and its values .

  • @jmuria
    @jmuria 8 років тому +1

    I loved to hear Ken and Jeff talking about the Scrum Values and some of the answers they gave. I'm a bit courious about how Jeff measured the speed of the 70.000 team and was able to catalogue them in terms of that speed.

    • @KirillKlimov
      @KirillKlimov 8 років тому

      This is about a research and people who started it:
      www.infoq.com/articles/quantifying-impact-agile
      This is recent report from CA (former Rally):
      www.rallydev.com/sites/default/files/ImpactofAgileQuantified2015.pdf
      where all names of the original team are ripped off as well as information on how research has been made.

    • @jmuria
      @jmuria 8 років тому

      Thanks Kirill. I'll read it carefuly

  • @chriswallace207
    @chriswallace207 8 років тому +1

    I just checked and see that an Esperanto translation of the Scrum Guide does not exist yet. Perhaps this is an opportunity for me to make a real contribution to the Scrum Framework's international body of knowledge. I just completed a movie script translation. I'm not great at it but I get better every sentence and blew the whole thing out in record time. It was a twice the work in a tenth of the time type situation based on the previous team's benchmark.

  • @jholmterrier
    @jholmterrier 8 років тому +1

    Great news! Without values, the Scrum Guide always felt pretty sterile to me.
    On #NoEstimates, however, it seems our dear gentlemen confuse, deliberately or not, not estimating with #NoEstimates, which suggests using other practices than story point estimation to make small batches and commitment work without it, for example slicing heuristics. Ironically, there's no need for Jeff and Ken to oppose this, since small, clear, right-sized stories and simply counting them works well within the Scrum framework.