The emphasis in product development should not be simply on correctly following the Scrum process, but rather on delivering a finished, working software; this is the true purpose of Scrum. Scrum provides a framework with established accountabilities, events, and artifacts which all relate to creating a working product. Therefore, using Scrum effectively will improve the delivery process. However, solely mastering Scrum won't guarantee success. The end goal should always be to deliver valuable, functioning software.

I've given the same advice to almost all of my clients -- "you need a clearer Product Backlog", "You're working really hard but you're not getting anything done", and "You need to cut scope, launch your product with a more focused scope, launch it, and then get feedback." ...

Your Sprint Planning Meetings don’t have to be a chore. Your Sprint Backlog doesn’t have to be a mess. Do short backlog refinement meetings twice a week and sleep a lot.

As part of the on-going Scrum Myths series at Scrum.org, here are three myths related to people skills.  When I say people skills, I mean topics like emotional intelligence, emotional IQ, and person-to-person interactions.

I work with a lot of companies to help them to improve their development processes and to either adopt Scrum or improve how they’re currently doing Scrum.  Lately, I’ve noticed that a fair number of companies run into problems with a certain kind

I did a coaching and training session with a company recently. They're a small, early-stage company in the Greater Boston-area.