I was talking to a friend the other day. She was looking for a job as a Scrum Master. Her background is technical and the last year or so she has been working as a professional coach. Not in IT that is. Just helping people to think and grow. We came to talk about if she should include her c...

I work in the public sector as an Agile coach. One of the question I often get asked is how to estimate the size of a new project, or a new delivery, as we need to determine a budget before executing it. One practice that has proven useful for this in my work experience is what I call the wall se...

One of the important event in Agile this year seems to be an argument around Test Driven Development (TDD). More precisely, high profile personalities in our industry debated against the statement "TDD is dead". Initially launched by David Heinemeier Hansson at the RailsConf keynote, it created quit...

] Volunteers at the Port Of San Diego - Operation Clean Sweep 2013 Think about this: If everyone in your organization could do whatever they wanted at work, would they do anything differently compared to today? If so, your organization is in big trouble! Why? Because that means that...

Recently I gave a talk on the ScrumDayEurope 2014 conference. The talk was about how you can use game principles in combination with evidence based management (EBM) in your agile adoption. One of the hard points in evidence based management is that people tend to ignore evidence when that evidence c...

A common challenge for businesses developing new products is having a coherent and universal understanding of what the value proposition for the organisation is.

Story Points - An Introduction The scrum guide tells us that estimates should be provided by people that will be doing the work but it doesn’t tell us how we should provide estimates. It leaves that decision to us. A common tactic used by scrum teams is to estimate using a unit of measurement r...

The Scrum.org blog is branching out to include our entire expert community! Now, readers will get more than the occasional formal article. The collective wisdom of all 150-ish Scrum.org Experts will be streaming to you on a regular basis. Help Seed the Content The Scrum.org community has some ...

I did a coaching and training session with a company recently. They're a small, early-stage company in the Greater Boston-area. I got a call from the owner (let's call him Mike) looking for help solving their problems with Team Foundation Server version control. Mike was complained that they were re...

The Scrum.org crew just returned from the Agile 2014 conference in Orlando. The great conversations with attendees were as good as the sessions themselves. There are people doing some truly amazing things with Scrum and software and this conference is a great place to meet up with them. I haven’t...

How can my team deliver value and innovation in 24 hours without intervention from management? A "FedEx Day" can be used to show management that just a few people can deliver innovative, working products and software in only 24 hours, and how intrinsic motivators are the key to unlocking our own inn...

In the past, the Scrum Guide consistently used the word "priority" for the Product Backlog or noted that the Product Backlog was “prioritized.” While the Product Backlog must be ordered, ordering by priority is only one many techniques — and rarely the best one at that.

The chicken and pig lore of Scrum is no longer a part of the Scrum Guide. Professional Scrum Trainer Steve Porter discusses the signifigance of what some may assume to be a relatively innocuous change.