This was the name of a session that I hosted at the Agile Open Florida on October 26, 2018. It was just an idea rattling around in my head coming off a month of screening candidates for scrum master, product owner, and agile coach roles. Honestly, I think wanted to talk about it to help me solidify some ideas and maybe some criteria around each of those roles, but especially the agile coach role. I had no idea that day that some many others would be interested in it as well.
Tag Archives: agile
I originally published this article directly on LinkedIn on April 2, 2018. It quickly began making its way around the world shortly afterwards. Needless to say, I was quite taken aback by both its popularity and the overwhelmingly positive response. It’s very humbling and I am very grateful.
Since the writing of the Agile Manifesto in 2001, agile software development has made major gains in popularity. As I write this, that increasing momentum shows no sign of lessening any time soon. However, like all popular movements in business (or society), agile doesn’t always mean the same thing to all people. This is where the struggle to adopt agile software development begins. But couple the confusion stemming from what agile really means with a fundamental lack of knowledge of what kind of environment agile software development needs in order...
What Is Scrum?
Scrum is an iterative, ritualized, process-driven agile software product development framework created by Ken Schwaber and Jeff Sutherland. Their official guide can be found at http://www.scrumguides.org/. Scrum organizes software product development around three foundational pillars; artifacts, roles, and meetings, that control the flow of work through the Scrum framework.
The Scrum artifacts are the product backlog, the sprint backlog, and the product/software increment. The product backlog is composed of prioritized product backlog items (epics, user stories, and bugs). The sprint backlog is composed of...