Title: Agile Project Management with Scrum
Author: Ken Schwaber
Year: 2004
Pages: 192
Scrum is a simple framework with simple rules and practices to build products in complex environments.
Despite Scrum’s simplicity, its lack of prescription can be disarming, and new practitioners revert to old project management tools and habits.
A series of stories illustrate the responsibilities and typical problems that Product Owners, Scrum Masters, and Teams face. Throughout each section in Agile Project Management With Scrum, there is a brief, concise story followed by a lessons learned section that summarizes the various points made.
As a result, I gave this book a rating of 7.5/10.
For me, a book with a note 10 is one I consider reading again every year. Among the books I rank with 10, for example, is Dale Carnegie’s How to Win Friends and Influence People.
Overview of Agile Project Management With Scrum
In Agile Project Management With Scrum, as a result of his years of experience coaching companies in agile project management, Scrum co-creator, and evangelist Ken Schwaber offers this series of case studies in Scrum to help you really understand it.
Agile Project Management With Scrum covers crucial subjects to help you gain a foundation in Scrum theory and practice:
– Rein in even the most complex, unwieldy projects
– Effectively manage unknown or changing product requirements
– Simplify the chain of command with self-managing development teams
– Obtain customer feedback and clearer specifications
– Greatly reduce project planning time and required tools
– Avoid missteps by regularly inspecting and fine-tuning projects
– Support multiple teams on a large-scale project from many locations
Agile Project Management With Scrum shows a process that helps teams work together to deliver products incrementally and continuously.
My Book Highlights & Quotes
“… The ScrumMaster is responsible for the Scrum process, for teaching Scrum to everyone involved in the project, for implementing Scrum so that it fits within an organization’s culture and still delivers the expected benefits, and for ensuring that everyone follows Scrum rules and practices…”
“… At the end of the Sprint, a Sprint review meeting is held. This is a four-hour, time-boxed meeting at which the Team presents what was developed during the Sprint to the Product Owner and any other stakeholders who want to attend…”
“… Laying out a process that repeatably will produce acceptable quality output is called defined process control. When defined process control cannot be achieved because of the complexity of the intermediate activities, something called empirical process control has to be employed…”
“… Scrum makes a clear distinction between these two groups and ensures that those who are responsible for the project have the authority to do what is necessary for its success and that those who aren’t responsible can’t interfere unnecessarily…”
“… Teams are self-managing, self-organizing, and cross-functional, and they are responsible for figuring out how to turn Product Backlog into an increment of functionality within an iteration and managing their own work to do so. Team members are collectively responsible for the success of each iteration and of the project as a whole…”
“… There are three legs that hold up every implementation of empirical process control: visibility, inspection, and adaptation…”
“… The rules of Scrum distinguish between the chickens and the pigs to increase productivity, create momentum, and put an end to floundering…”
“… It doesn’t matter whether it is visible that this functionality is done if no one can agree what the word “done” means…”
“… The heart of Scrum lies in the iteration. The team takes a look at the requirements, considers the available technology, and evaluates its own skills and capabilities. It then collectively determines how to build the functionality, modifying its approach daily as it encounters new complexities, difficulties, and surprises. The team figures out what needs to be done and selects the best way to do it. This creative process is the heart of the Scrum’s productivity…”
“… Scrum hangs all of its practices on an iterative, incremental process skeleton…”
The Scrum framework includes roles such as the Product Owner, Scrum Master, and Development Team, as well as ceremonies such as Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective.
Agile Project Management With Scrum provides an in-depth understanding of the Scrum framework, including its principles, roles, ceremonies, and artefacts.
Agile Project Management With Scrum also includes tips and best practices for implementing Scrum in an organization and dealing with common challenges.
Agile Project Management With Scrum is intended for project managers, team leads, and anyone else involved in managing projects using the Scrum framework.
These topics will help you learn how to use Scrum to solve complex problems and deliver better results.
I am incredibly grateful that you have taken the time to read this post.
Do you want to get new content in your Email?
Do you want to explore more?
Check my main categories of content below:
- Agile
- Blog
- Book Notes
- Career
- Leadership
- Management
- Managing Yourself
- Productivity
- Project Management
- Technology
- Weekly Pulse
Navigate between the many topics covered in this website:
Agile Art Artificial Intelligence Blockchain Books Business Business Tales Career Coaching Communication Creativity Culture Cybersecurity Design DevOps Economy Emotional Intelligence Feedback Flow Focus Gaming Goals GPT Habits Health History Innovation Kanban Leadership Lean Life Managament Management Mentorship Metaverse Metrics Mindset Minimalism Motivation Negotiation Networking Neuroscience NFT Ownership Parenting Planning PMBOK PMI Politics Productivity Products Project Management Projects Pulse Readings Routines Scrum Self-Improvement Self-Management Sleep Startups Strategy Team Building Technology Time Management Volunteering Work
Do you want to check previous Book Notes? Check these from the last couple of weeks:
- Book Notes #123: The Personal MBA by Josh Kaufman
- Book Notes #122: The First 20 Hours by Josh Kaufman
- Book Notes #121: A World Without Email by Cal Newport
- Book Notes #120: Storynomics by Robert McKee and Thomas Gerace
- Book Notes #119: Getting Things Done by David Allen
Support my work by sharing my content with your network using the sharing buttons below.
Want to show your support tangibly? A virtual coffee is a small but nice way to show your appreciation and give me the extra energy to keep crafting valuable content! Pay me a coffee:
