Several of us in the Kanban and Scrum community got together recently to build a bridge between Scrum and Kanban. We are writing a series of blog posts looking at this bridge from different perspectives.
I am enjoying the Vikings series with my wife, and it inspired a metaphor I have been using when discussing Scrum and Agile Roles within the Scrum team. The roles in Scrum are like the roles on long ship, and the purpose was either trade or raiding.
If agility is why your organization adopts Scrum, look for more sophistication in employing Scrum.
Through Scrum, teams and organizations create the opportunity of having a releasable version of product no later than by the e
What makes the software development work great? Obviously, technology, right... Wrong! In an interesting article in "Peopleware", authors Tom and Timothy describe how the most important aspect of software development is not technology, but people.
Congratulations! You replied to the job advert for an agile position, and you’ve got an interview. Genuinely keen to work in an agile way, you know that the organization must have picked up on your credentials.
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.