Read about the experiences and ideas of Agile colleagues around the world, and share your own thoughts here. You can also visit
, which features blogs by experts in the fields of Scrum, Agile, and the broader business world.
5/12/2015 by Michael Barone
The sprint retrospective event is, in my opinion, the most important event in Scrum. Of course I did not invent it, but I do perform the event a little differently than most.
5/11/2015 by SAVVY KATHAM
Have you ever wondered why there are a lot of scrutiny and checkpoints on IT programs and projects? Because there's an investment involved.
5/8/2015 by Ankush Sabharwal
The size of a story should be as small as possible. I know it can be difficult to create smaller stories, but trust me, you will get better with time, and eventually you will see results that make you happy. Here are some tips.
5/7/2015 by Wei Zhou
One day, a new ScrumMaster -- I'll call him Jack -- came to see me. "Hey, Joe," he said. "You know, sometimes I think Waterfall is better for a cross-functional team." . . .
5/6/2015 by Aaron D'Souza
Often teams struggle with picking the right-sized user story. Teams should involve the product owner and negotiate the feature if it ends up being too complex.
5/6/2015 by Karen Fernandez
There are seven styles of learning, but there are two that, when combined, resonate with most people. Interaction, spatial and kinesthetic, is human behavior. This is why my high-performing teams rarely sit during a meeting.
5/5/2015 by Chia Kwan
A Scrum team should invest sufficient time in design, with the sole purpose of delivering value to the customer. Here are some ways to do this.
5/4/2015 by Francesco Attanasio
I ask myself this question every day: How can my work support other people's motivation?
5/1/2015 by Samuel Nadarajan
I recently used Scrum outside of technology, for a construction project. Here is how I implemented Scrum roles and used ceremonies, along with the benefits realized.
4/30/2015 by K Pawan Kumar
To get developers and testers on the same page, it's imperative that an appropriate "handshake" is done between developer and tester at the beginning of the project, and it should continue throughout the sprints.