Blogs on Scrum and Agile Project Management
Agile values working software over comprehensive documentation – It is 1/4th of the original manifesto. That doesn’t mean don’t document! It means don’t document more than you need to document. Documentation does have value, but the practice of documenting got excessive – that’s why a reaction to the bad stuff earned a spot as one of the pillars of agile. This blog post discusses how do you avoid over-reacting when changing a culture of over-documentation?
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.
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.
In his blog post “Earned Value versus Earned Schedule“, Glen Alleman discuss the concepts of Earned Value and Earned Schedule.
As an agile coach, you want to build trust with the people on the team you are coaching. You also want to improve trust between individuals on the team (which is hard to do if the team doesn’t trust you yet). This post shares Rachel Davies thinking on how you can help encourage trust to grow in different situations.
Scrum Expert Copyright © 2009-2024 Martinig & Associates