bookmate game
en
Gunther Verheyen

Scrum – A Pocket Guide

Giv mig besked når bogen er tilgængelig
Denne bog er ikke tilgængelig i streaming pt. men du kan uploade din egen epub- eller fb2-fil og læse den sammen med dine andre bøger på Bookmate. Hvordan overfører jeg en bog?
This pocket guide is the one book to read for everyone who wants to learn about Scrum.The book covers all roles, rules and the main principles underpinning Scrum, and is based on the Scrum Guide Edition 2013. A broader context to this fundamental description of Scrum is given by describing the past and the future of Scrum.The author, Gunther Verheyen, has created a concise, yet complete and passionate reference about Scrum. The book demonstrates his core view that Scrum is about a journey, a journey of discovery and fun. He designed the book to be a helpful guide on that journey.Ken Schwaber, Scrum co-creator says that this book currently is the best available description of Scrum around. The book combines some rare characteristics:• It describes Scrum in its entirety, yet places it in a broader context (of past and future).• The author focuses on the subject, Scrum, in a way that it truly supports the reader. The book has a language and style in line with the philosophy of Scrum.• The book shows the playfulness of Scrum.David Starr and Ralph Jocham, Professional Scrum trainers and early agile adopters, say that this is the ultimate book to be advised as follow-up book to the students they teach Scrum to and to teams and managers of organizations that they coach Scrum to.
Denne bog er ikke tilgængelig i øjeblikket
119 trykte sider
Oprindeligt udgivet
2013
Udgivelsesår
2013
Har du allerede læst den? Hvad synes du om den?
👍👎

Citater

  • Nahuel Rabeyhar citeretfor 3 år siden
    In an Agile process the goal of each iteration is to produce a working piece of product. No partial work is included in the software at the end of an iteration.
  • Nahuel Rabeyhar citeretfor 3 år siden
    Detailed requirements, hard-coded plans, designs, etc. form a liability in software development, and not an asset, because they represent potentially unused work. Agile avoids producing these upfront in every possible detail. If the potential point of implementation of identified work is still some time away, the chances are quite high that this will not be implemented.
  • Nahuel Rabeyhar citeretfor 3 år siden
    It invokes the difficult exercise of letting go of ‘command and control’,

På boghylderne

  • Henrik
    Henriks hylde
    • 105
  • Epicent Public Relations A/S
    Martin
    • 40
  • Signe Ziegler Larsen
    Arbejde
    • 9
  • Amra Besic Pedersen
    Work
    • 5
fb2epub
Træk og slip dine filer (ikke mere end 5 ad gangen)