7 books
—
1 voter
Scrum Books
Showing 1-50 of 465

by (shelved 86 times as scrum)
avg rating 4.14 — 23,433 ratings — published 2014

by (shelved 50 times as scrum)
avg rating 4.23 — 1,010 ratings — published 2013

by (shelved 50 times as scrum)
avg rating 4.15 — 1,645 ratings — published 2012

by (shelved 48 times as scrum)
avg rating 3.94 — 2,504 ratings — published 2006

by (shelved 43 times as scrum)
avg rating 4.01 — 1,851 ratings — published 2009

by (shelved 40 times as scrum)
avg rating 4.21 — 1,828 ratings — published 2007

by (shelved 38 times as scrum)
avg rating 4.24 — 544 ratings — published

by (shelved 33 times as scrum)
avg rating 4.14 — 2,623 ratings — published 2005

by (shelved 31 times as scrum)
avg rating 4.22 — 1,928 ratings — published 2010

by (shelved 31 times as scrum)
avg rating 3.71 — 1,536 ratings — published

by (shelved 30 times as scrum)
avg rating 3.89 — 2,853 ratings — published 2004

by (shelved 28 times as scrum)
avg rating 3.84 — 1,643 ratings — published 2008

by (shelved 26 times as scrum)
avg rating 3.81 — 962 ratings — published 2001

by (shelved 23 times as scrum)
avg rating 4.38 — 718 ratings — published 2018

by (shelved 22 times as scrum)
avg rating 3.96 — 1,222 ratings — published 2010

by (shelved 19 times as scrum)
avg rating 4.02 — 624 ratings — published

by (shelved 18 times as scrum)
avg rating 4.06 — 212 ratings — published 2013

by (shelved 17 times as scrum)
avg rating 4.20 — 185 ratings — published

by (shelved 16 times as scrum)
avg rating 4.18 — 285 ratings — published 2012

by (shelved 16 times as scrum)
avg rating 3.60 — 384 ratings — published 2012

by (shelved 15 times as scrum)
avg rating 4.28 — 139 ratings — published

by (shelved 15 times as scrum)
avg rating 3.77 — 238 ratings — published

by (shelved 13 times as scrum)
avg rating 4.19 — 3,900 ratings — published 2012

by (shelved 13 times as scrum)
avg rating 3.95 — 124,529 ratings — published 2009

by (shelved 13 times as scrum)
avg rating 4.10 — 309 ratings — published 2008

by (shelved 13 times as scrum)
avg rating 3.50 — 155 ratings — published 2007

by (shelved 12 times as scrum)
avg rating 4.31 — 124 ratings — published

by (shelved 12 times as scrum)
avg rating 4.42 — 72 ratings — published

by (shelved 12 times as scrum)
avg rating 4.21 — 259 ratings — published 2014

by (shelved 11 times as scrum)
avg rating 4.11 — 360,231 ratings — published 2011

by (shelved 10 times as scrum)
avg rating 4.35 — 102 ratings — published

by (shelved 10 times as scrum)
avg rating 4.16 — 285 ratings — published

by (shelved 10 times as scrum)
avg rating 4.11 — 134,701 ratings — published 2002

by (shelved 10 times as scrum)
avg rating 3.96 — 3,363 ratings — published 2012

by (shelved 9 times as scrum)
avg rating 3.82 — 1,116 ratings — published 2008

by (shelved 9 times as scrum)
avg rating 4.15 — 602 ratings — published 2014

by (shelved 8 times as scrum)
avg rating 4.12 — 121 ratings — published

by (shelved 8 times as scrum)
avg rating 4.26 — 49,376 ratings — published 2013

by (shelved 8 times as scrum)
avg rating 4.14 — 9,883 ratings — published 1987

by (shelved 8 times as scrum)
avg rating 4.27 — 686 ratings — published 1996

by (shelved 8 times as scrum)
avg rating 4.20 — 1,006 ratings — published 2011

by (shelved 8 times as scrum)
avg rating 3.87 — 465 ratings — published 2010

by (shelved 7 times as scrum)
avg rating 3.84 — 56 ratings — published

by (shelved 7 times as scrum)
avg rating 4.38 — 146 ratings — published

by (shelved 7 times as scrum)
avg rating 3.97 — 893 ratings — published 2011

by (shelved 7 times as scrum)
avg rating 3.94 — 1,638 ratings — published 2010

by (shelved 7 times as scrum)
avg rating 4.11 — 358 ratings — published 2012

by (shelved 7 times as scrum)
avg rating 4.20 — 3,294 ratings — published 2010

by (shelved 7 times as scrum)
avg rating 3.79 — 227 ratings — published 2011
“Just because architecture is supposed to be stable, it does not mean that it should never change.”
― Scaling Done Right: How to Achieve Business Agility with Scrum@Scale and Make the Competition Irrelevant
― Scaling Done Right: How to Achieve Business Agility with Scrum@Scale and Make the Competition Irrelevant
“The Agile project manager plays a crucial role in ensuring the successful delivery of projects using Agile methodologies. They act as facilitators, coaches, and leaders, guiding the team through the iterative development process.
Here are some key responsibilities of an Agile project manager:
Orchestrating the project's lifecycle: This involves planning and breakdown of work into sprints, facilitating ceremonies like daily stand-ups, sprint planning, and retrospectives, and ensuring the project progresses smoothly towards its goals.
Promoting collaboration and communication: Agile thrives on open communication and collaboration. The project manager fosters an environment where team members feel comfortable sharing ideas, concerns, and updates. They actively remove roadblocks and ensure everyone is aligned with the project vision and goals.
Empowering the team: Agile teams are self-organizing and empowered to make decisions. The project manager provides guidance and support but avoids micromanaging. They trust the team's expertise and encourage them to take ownership of their work.
Stakeholder management: The project manager acts as a bridge between the development team and stakeholders, including clients, sponsors, and other interested parties. They keep stakeholders informed of project progress, manage expectations, and address their concerns.
Continuous improvement: Agile is an iterative process that emphasizes continuous improvement. The project manager actively seeks feedback from team members and stakeholders, analyzes project data, and identifies areas for improvement. They implement changes to the process and tools to enhance efficiency and effectiveness.
Overall, the Agile project manager plays a vital role in driving successful project delivery through Agile methodologies. They wear multiple hats, acting as facilitators, coaches, leaders, and problem-solvers, ensuring the team has the resources, support, and environment they need to thrive.”
―
Here are some key responsibilities of an Agile project manager:
Orchestrating the project's lifecycle: This involves planning and breakdown of work into sprints, facilitating ceremonies like daily stand-ups, sprint planning, and retrospectives, and ensuring the project progresses smoothly towards its goals.
Promoting collaboration and communication: Agile thrives on open communication and collaboration. The project manager fosters an environment where team members feel comfortable sharing ideas, concerns, and updates. They actively remove roadblocks and ensure everyone is aligned with the project vision and goals.
Empowering the team: Agile teams are self-organizing and empowered to make decisions. The project manager provides guidance and support but avoids micromanaging. They trust the team's expertise and encourage them to take ownership of their work.
Stakeholder management: The project manager acts as a bridge between the development team and stakeholders, including clients, sponsors, and other interested parties. They keep stakeholders informed of project progress, manage expectations, and address their concerns.
Continuous improvement: Agile is an iterative process that emphasizes continuous improvement. The project manager actively seeks feedback from team members and stakeholders, analyzes project data, and identifies areas for improvement. They implement changes to the process and tools to enhance efficiency and effectiveness.
Overall, the Agile project manager plays a vital role in driving successful project delivery through Agile methodologies. They wear multiple hats, acting as facilitators, coaches, leaders, and problem-solvers, ensuring the team has the resources, support, and environment they need to thrive.”
―