|View the full article at Scrum Lessons Learned – Part 1.|
Note that Scrum Alliance has indefinitely suspended the member-submitted article section of their website while they work on a redesign. So this article is not accessible there.
I am proud to announce that the Scrum Alliance editorial team has reviewed, approved and published another one of my articles. This one is titled Scrum Lessons Learned. This is the first of many lessons learned articles to come.
What’s it about ?
If you’re using Waterfall or some other non-Agile method, then transitioning to Agile principles and the Scrum process is a significant paradigm shift. It’s likely that without professional Agile transformation guidance, you will encounter one or more common Agile implementation mistakes.
This article discusses some lessons learned through pain and triumph and tries to boil them down to a few do’s and don’ts with some real-world scenarios.
The article will focus on the following do’s and don’ts:
- Don’t take shortcuts with Scrum. Don’t mess with what works.
- Do support your Superheroes. ScrumMasters and Scrum product owners (POs) are your leaders; they must apply themselves as superheroes.
- Don’t micromanage. To reach maximum productivity, the Scrum team must be a self-managing entity.
Who is the Scrum Alliance ?
The ScrumAlliance.org is the non-profit organization that manages the official Scrum certifications, training, events, community and more.
View this article on the Scrum Alliance site at:
View my Scrum Alliance profile at:
My other articles published by the Scrum Alliance:
Adopt Scrum for Competitive Advantage