Scan barcode
ryanwriter's review against another edition
5.0
Loved the book! Great introduction to using Scrum with teams beyond software development.
ksilvennoinen's review against another edition
3.0
One thing that I didn’t fully grasp while taking my first year courses at the university was the focus on the management methods ands logistics of Japanese car manufacturers. Once I entered the work force I began to understand it was because most of those things were still very foreign to companies. Sutherland’s book isn’t a book that will explain Scrum itself (the reader is supposed to be familiar with the basics), it’s a book that explains where it came from and what ideas surround it - and this is interesting: many flashbacks to my first year courses in strategy, management and logistics and how all those building blocks started to fit together.
gloame's review against another edition
4.0
The main takeaway here is "the 80/20 rule is basically the whole point". A few other things to note...
- Keep team sizes small (but not too small!) to maintain the best efficiency
- Don't even try to multitask because it never works and you're wasting time and resources.
- Get your priorities straight; what is the ACTUAL GOAL of the project? Not the bells and whistles.
- Be respectful. Duh. All leaders should be.
- Don't get too attached to A Plan. Be ready and willing to adapt, change, go with the flow.
These kind of make up the philosophy behind the technical aspects of 'how to scrum'. Would have been nice to see some examples of projects that didn't work so well, even with scrum, and what happened as a result. Not every project will go smoothly. (Do any ever?)
- Keep team sizes small (but not too small!) to maintain the best efficiency
- Don't even try to multitask because it never works and you're wasting time and resources.
- Get your priorities straight; what is the ACTUAL GOAL of the project? Not the bells and whistles.
- Be respectful. Duh. All leaders should be.
- Don't get too attached to A Plan. Be ready and willing to adapt, change, go with the flow.
These kind of make up the philosophy behind the technical aspects of 'how to scrum'. Would have been nice to see some examples of projects that didn't work so well, even with scrum, and what happened as a result. Not every project will go smoothly. (Do any ever?)
irenecas's review against another edition
3.0
Buen libro para aprender sobre Scrum. Me estoy preparando un examen y te ayuda a entender el contexto de cómo surgió, así como ejemplos para poder usarlo no solo en proyectos de tecnología, también del día a día
annbvrnes's review against another edition
2.0
Չէի նախատեսել այս գիրքը կարդալ, զուտ մասնագիտական նպատակով, քանի որ հիմա Scrum մեթոդն եմ ուսումնասիրում: Չէի ասի, որ ինձ շատ նոր բան տվեց, հիմնական իմացածս թեթև ամրապնդեցի ընդամենը: Ոչ գեղարվեստական ու չոր մասնագիտական գրքերն իմը չեն, գնալով համոզվում եմ: 2/5 for effort, ինչ-որ մեկին խորհուրդ չէի տա, բացի Project Management-ի ոլորտի մարդկանցից: