Articles, Blog Posts, Books and Quotes on Agile Project Management
I have observed and participated in a great number of sprint reviews. I’ve seen some quirky things from the Scrum teams as they attempt to demonstrate the working software and artifacts they have produced in the sprint.
“Aspects of Kanban” is an introduction to the Kanban workflow Lean project management system.
Scrum and other agile methods recognize that responsiveness to change is an important aspect of delivering projects. They also recognize that software development is evolutionary and creative. By managing changes through Adaptive planning, Scrum provides a simple yet effective method of planning and tracking project progress. “How to Sustain Adaptive Planning” examines what is needed to sustain Adaptive planning and improve Team’s responsiveness towards customer needs.
This happens all the time on projects: assuming there is consensus when none exists. While good teams can roll with these punches and adapt as they go, it’s a form of waste that can hurt or kill the unwary before they even get out of the gate. To nip this problem in the bud, ThoughtWorks created a lightweight project chartering tool called “The Agile Inception Deck: 10 questions and exercises you’d be crazy not to ask before starting your project.”
Everyone has heard about the benefits of a strong Agile team. They are focussed, extremely productive and self-managing. Why is it so hard to make your agile team gain these same benefits?
It’s obvious, but warrants mention: What we do in the future is likely to be different from what we’re doing today. The implications for user stories should be obvious: User stories are temporary. Saving them for posterity doesn’t serve the primary purpose of user stories, and doing anything that makes them less temporary can turn user stories from benefit to detriment.
“The Quest for High Performance” by Tom Reynolds. One of the best ways to ensure that a team grows to be high performing is to get them off to the right start. Read this article to learn two team start-up activities that focus on process and help ensure everyone is on the same page from the beginning.