Ken Schwaber
Autor de Agile Project Management with Scrum
Sobre El Autor
Obras de Ken Schwaber
Etiquetado
Conocimiento común
- Nombre canónico
- Schwaber, Ken
- Fecha de nacimiento
- 1945
- Género
- male
- Nacionalidad
- USA
Miembros
Reseñas
También Puede Gustarte
Autores relacionados
Estadísticas
- Obras
- 12
- Miembros
- 930
- Popularidad
- #27,610
- Valoración
- 3.6
- Reseñas
- 12
- ISBNs
- 26
- Idiomas
- 1
As a non-IT person who now works with IT, this was interesting to me to look at Scrum from a management rather than an IT perspective. In this respect, the book comes up short, in that it was written in 2002 and is fairly full of jargon that is a) very IT development-heavy in a US corporate context, and b) that jargon is more than ten years out of date (even I can detect that!).
There are some practical aspects of Scrum, such as task estimating, which are not covered at all - which, considering how central task estimation is to Scrum is something of an oversight. And the book is very poorly edited. There is a lot of duplication of message and of text, which does give the impression of a tub-thumping endorsement of Scrum that some readers will find irritating. The author has practical experience of implementing Scrum, but his examples all start from the premise that he was brought in as a senior manager to make a project work, so his implementation of Scrum was made easy by a) his ability to drive through change with a degree of authority at his back, and b) an assumption that all his team are going to be 100% devoted to their work 100% of the time. A nice assumption, but one often at odds with the real world.
Nonetheless, I read this book as a refresher on Scrum and found it quite helpful. I'd been employed in a development environment as a tester some four years previously and worked with Scrum. A copy of this book was included in the cost of a Scrum Master training course, but to be honest I had not read it until now, when after a career break of some four years, I found myself in a new testing environment working with an IT systems development contractor who was employing Scrum. I found the case studies and some of the discussion of the philosophy of Scrum more interesting than some other readers with more of an IT bent might, which is a bit of a shame as they are the book's intended audience rather than people like me who are more people systems people. (I was quite amused by a short section explaining where the term 'Scrum' comes from, and debunking some people's ideas about that.)
As I said, the book is very poorly edited. There is one instance where a person being talked about in a case study changes gender in the middle of a paragraph, and a psychological test on perception, which relies on a particular colour graphic used on the cover of the first edition, is still referred to even though a subsequent edition has dropped the graphic! Other graphics in the book appear to be 1990s clip art or very basic chart work, and give the impression of much cheapness. And Pearson seem to have gone for a really low-cost approach to the book; my copy appears to have been printed on photocopier paper. I know I got this book for nothing, but the care that Pearson have lavished on this later edition suggest that that's all they think it's worth.
Really, the book needs a re-write to pitch it to a slightly different audience and revision to make the practical Scrum lessons a bit more relevant.… (más)