The Elements of Scrum Quotes

Rate this book
Clear rating
The Elements of Scrum The Elements of Scrum by Chris Sims
898 ratings, 3.97 average rating, 74 reviews
Open Preview
The Elements of Scrum Quotes Showing 1-10 of 10
“Working software is the primary measure of progress.”
Chris Sims, The Elements of Scrum
“anyone who has worked on an enterprise-scale software project knows that the only thing you can count on is change.”
Chris Sims, The Elements of Scrum
“We have seen a few examples of teams trying to have one person serve as both scrum master and product owner. In all the cases we have seen, this has failed.”
Chris Sims, The Elements of Scrum
“Talent wins games, but teamwork and intelligence wins championships.”
Chris Sims, The Elements of Scrum
“Agile processes of all kinds share one thing: they embrace change, approaching it as an opportunity for growth, rather than an obstacle.”
Chris Sims, The Elements of Scrum
“So, why do we do development work in these short cycles? To learn. Experience is the best teacher, and the scrum cycle is designed to provide you with multiple opportunities to receive feedback—from customers, from the team, from the market—and learn from it. What you learn while doing the work in one cycle informs your planning for the next cycle. In scrum, we call this “inspect and adapt”; you might call it “continuous improvement”; either way, it’s a beautiful thing.”
Chris Sims, The Elements of Scrum
“describes the role of the product owner: “You must recognize that through your actions—writing user stories and acceptance tests, prioritizing user stories by business value, deciding which user stories are developed next, providing rapid feedback, etc—you”
Chris Sims, The Elements of Scrum
“Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan”
Chris Sims, The Elements of Scrum
“The Standish Group’s 2002 “Chaos” study of software project success and failure rates states that in a typical software system, 45% of features are never used. Only 7% of features are always used, and another 13% are used often.”
Chris Sims, The Elements of Scrum
“The best architectures, requirements, and designs emerge from self-organizing teams.”
Chris Sims, The Elements of Scrum