- Agile Leadership Development
- AgileSafari
- Coaching
- Facilitation
- Leadership
- Practices
- Principles
- Product Owner
- Scaling
- ScrumMaster
Be Better, Don’t Limit Yourself to Best Practices
We hear a lot about best practices. We talk a lot about them. Many organizations are of the opinion that if they can identify the best practice, they are set. Of course, that thinking can be limiting in a number of ways. We need to be better, not
The Real Baseline Agile Retrospective Format
I always considered this six question format to be the Baseline Agile Retrospective Format. I say baseline instead of standard because a baseline is something to build on, not an ‘always the way’ standard (or worse, a “best practice“).
I believe the six question baseline
New to agile? Remember a user story is more than a card!
What’s wrong with the user story on the card? It seems to have everything we need: a) short title, b) a size (in this case 2), and c) a well-written story using the standard “As a … I want … so that …” format. So what’s wrong?
Agile antipatterns: Agile burn-down chart roundup post
Do you want to see several different ways agile and scrum burn-down charts can lie? If so, you are in the right place! This month I went on a burn-down chart craze and posted several blog entries about the different ways those charts can lie to us or expose us to team dysfunction. In order, the
New to agile? Learn how to split stories
In my last blog Agile antipattern: Taking on large stories I said I would give you some tips on how to split stories. First though, it is important to understand WHY splitting a story well can be helpful. It is about much more than just making smaller
Agile antipattern: Taking on large stories
Earlier this week I posted a blog entry “Agile antipattern: Burndown charts that hide the truth” which dealt with one way a burndown chart could hide reality. This blog entry shows another way it is possible for a burndown chart to be misleading. The burndown
New to agile? Work at a sustainable pace
Question: Which is better: a) Working nights and weekends to meet iteration commitments, or b) Admitting the commitment was too much and working normal hours regardless of the
Agile antipattern: Using email as the primary communication tool
Can I just be short and to the point for this one? I hope so, because that is my intention!
Email is LOW BANDWIDTH communication
Agile teams REQUIRE HIGH BANDWIDTH communication
Do you see a problem?
Agile teams need to communicate in real-time whenever possible. Even the agile manifesto says “individuals and