Agile Project Management with Scrum
Apply the principles of Scrum to software project management with guidance from one of the leaders in the agile process movement. Case studies and project examples demonstrate Scrum concepts in practice and emphasize driving projects for maximum ROI. The rules and practices for Scrum—a simple process for managing complex projects—are few, straightforward, and easy to learn. But Scrum's simplicity itself—its lack of prescription—can be disarming, and new practitioners often find themselves reverting to old project management habits and tools and yielding lesser results. In this illuminating series of case studies, Scrum co-creator and evangelist Ken Schwaber identifies the real-world lessons—the successes and failures—culled from his years of experience coaching companies in agile project management. Through them, you'll understand how to use Scrum to solve complex problems and drive better results—delivering more valuable software faster.Gain the foundation in Scrum theory—and practice—you need to: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 Receive clearer specifications—and feedback—from customers Greatly reduce project planning time and required tools Build—and release—products in 30-day cycles so clients get deliverables earlierAvoid missteps by regularly inspecting, reporting on, and fine-tuning projects Support multiple teams working on a…
Stats for nerds
2recommend
4mentions
4people
2008–2023years
50% recommend50% neutral
Mentions per year
What Hacker News says
- These are loosely related to your topic. But, depending on where your interests lie, these might be interesting for you:
"Nine Algorithms That Changed the Future: The Ingenious Ideas That Drive Today's Computers" - John MacCormick
"Domain Driven Design" - Eric Evans
"Artificial Intelligence: The Basics" - Kevin Warwick
...and on the Project management / Executive side:
"Agile Project Management with Scrum" - Ken Schwaber
"Reality Check" - Guy Kawasaki
"Founders at Work: Stories of Startups' Early Days" - Jessica Livingston
- There are a lot of them. A lot!
But it depends if you are interested in pure methodology, or you want to see some example of applying it in software/Web development with PHP/Java/RoR/...
From my experience, I found helpful next books:
"Test Driven Development: By Example" by Kent Beck
"Agile Software Development, Principles, Patterns, and Practices" by Robert C. Martin
"Agile and Iterative Development: A Manager's Guide" by Craig Larman
"Agile Project Management with Scrum" by Ken Schwaber
"Agile Software Development Ecosystems" by Jim Highsmith
Those are pretty "technology independent". Helpful to understand the idea. And the authors are respected and well known in the community of agile developers.
If you work with RoR (which is popular choice nowadays) you may find "Agile Web Development with Rails" by Dave Thomas and David Hansson interesting, but it does not cover "agile methodology" itself too wide. But it does give a good overview of practical usage. Anyhow, personally I still prefer to learn theory before practice, but many people see it working for them ;-)
- Anything focusing on Lean Software Development and/or Agile. As much hate those words bring up in people that have had bad experiences and bad management of those processes, the alternatives of waterfall are much worse for software. There are exceptions like if you’re building software for a nuclear reactor or high risk projects you’ll want very stringent requirements processes.
The core concepts behind agile/lean are really geared towards minimizing churn on stuff that doesn’t matter (unimportant features) and having a short feedback loop so you can find issues faster. Nothing is perfect and you will still have unused features and bugs, that’s the nature of it. One of the books I read had research backed findings based on analysis of projects, I think it was Agile Project Management with Scrum. Rework and other books by the Basecamp founders are good. It’s good to read up on a few different ways people have successfully done things to get perspective that not everything is “one size fits all.” Don’t take any methodology or process as prescriptive, they all have trade offs.
- Having read ken schwaber's "agile Project management with scrum" something like 8 years ago and hearing him speak, and working with agile teams during my most junior development I couldn't fucking agree more. I loved scrum when I first started using it, and I was a horrible developer back then. I pity anyone who had to work with me.
This article was strangely heartwarming.
Related
Agile Software Development Ecosystems
2 recommend · 2
Agile Software Development, Principles, Patterns, and Practices
7 recommend · 10
Agile Software Development with SCRUM
2 recommend · 3
Agile web development with rails
67 recommend · 137
Scrum
6 recommend · 8
The art of agile development
13 recommend · 33
