The book starts with a presentation of Agile and Lean principles. The second part explains how Lean adoption can improve the usage of Scrum with an interesting table comparing Scrum and Lean accompanied by a list of practices to avoid.
In his article “Effective Retrospectives & Reviews” Marco Mulder illustrates how Scrum teams can continuously improve by using a combination of their definition of done, working agreements and the product backlog.
The Agile Project Leadership Network (APLN) is a 501(c)6 non profit organization that is focused on making people great project leaders by focusing on the following:
Some people want to take the stance that no work should be done in advance of the sprint. That is clearly untenable. To see why, let’s take that view to its extreme: If we did nothing in advance to understand what we’re building, we’d show up at the planning meeting and say, “Hey, what should we build this sprint? We were working on an eCommerce site yesterday, but I think maybe we should switch to writing a word processor…” The team would literally have nothing written down—no product backlog / user stories / prioritized feature list at all.