Many companies are using Scrum, however some struggle with achieving really effective teams. When teams feel the pressure from the business and Product Owner, look at all the work they have to do, and how much time they have to do it, working on improvements seems unimportant.

The sprint retrospective meeting in Scrum is a time for the team to reflect on how they're doing and find ways to improve.

Many of those practicing Scrum mistakenly call the Sprint Review a Demo. Is it just a matter of terminology? From my point of view, the Sprint Review is the most underestimated Scrum Event, and for many companies, its potential is yet to be revealed. It is true that the Demonstration or Demo is an essential part of the Sprint Review, but it isn't the only one.

**Summary**: A meeting to prepare for the Sprint, typically divided into two parts (part one is “what” and part two is “how”). **Participants**: Part O...

I'm currently the Scrum Master of a 10 developer strong team. We've adopted Agile/Scrum methodologies for some time now and are currently on our 53rd Sprint. Our stakeholders actively like to understand the output of story points in advance of a Sprint. This is currently done on a capacity basis working on a focus factor of 60%.

Choosing the right iteration length is an important decision. These are important factors you should consider when selecting your team's iteration length.

I read a lot about the planning onion related to Agile environment.  Here at my office, I use the planning onion to effectively show the layers of responsibility that help us to get things don…