6. Mistakes to avoid
Not having a product manager permanently present with the team is a major risk for the project. One way of protecting against this problem is to have a second expert who can deputise for him when he is absent.
Don't think of Scrum as a toolbox from which you can only choose what you find interesting. It's certainly a framework, but one that has already been stripped down to the bare essentials. Not applying the whole method is also a risk, especially when you haven't mastered the principles underlying the practices.
The Ultimate Scientific and Technical Reference
This article is included in
Management and innovation engineering
This offer includes:
Knowledge Base
Updated and enriched with articles validated by our scientific committees
Services
A set of exclusive tools to complement the resources
Practical Path
Operational and didactic, to guarantee the acquisition of transversal skills
Doc & Quiz
Interactive articles with quizzes, for constructive reading
Mistakes to avoid
Frequently asked questions
Bibliography
Schwaber K., Sutherland J., Software in 30 days , Wiley & Sons, 2012, 194 p.
Aubry C., Scrum , Dunod, 2010, 304 p.
Schwaber K., The Enterprise and Scrum , Microsoft Press, 2007, 176 p.
Derby E., Larsen D., Agile Retrospectives: Making Good Teams Great , Pragmatic Bookshelf, 2006, 200 p....
Websites
scrum.jeffsutherland.com Jeff Sutherland's blog, co-creator of the Scrum method
controlchaos.com Ken Schwaber's blog, co-creator of the Scrum method
The Ultimate Scientific and Technical Reference
