Browsing Posts in Top Content

Top Content

No comments

Top 10 pages visited on the site.

  1. Agile Team Members – Roles and Responsibilities
  2. Kanban Ground Rules Example for a Specific Team
  3. 12 Agile Adoption Failure Modes by Jean Tabaka
  4. Naked Planning Explained – Kanban in the Small
  5. Cougar’s donation is pending
  6. What do you think the INVEST acronym is for #Agile User Stories?
  7. Setting a Minimum Bar for Scrum
  8. Applying to Become a Certified Scrum Trainer
  9. Leading a Retrospective Before Introducing Kanban to a Team
  10. Whole Team Incentives – Redeeming Features for Rewards

I’m so glad you’re still here, buddy.

International Human Rights Day is December 10th. In recognition, I participated in an event organized by the #occupysf movement. This video is where I enjoyed my favorite moment, and share it with you now:

This is a question I asked recently of a newly-formed Scrum team in a User Story Writing workshop. It occurred to me to not just blurt it out and to let them offer suggestions instead. They were very willing to contribute and I’d like to share the answers they came up with:

Throwing Your Hat Into The Ring The Scrum Alliance is accepting new applicants to become Certified Scrum Trainers (CST) and I’ve decided to throw my hat in the ring. If you would like to know why I am applying, please feel free to read my letter of intent.

Lately I’ve been reading about people lamenting unsuccessful adoptions of Scrum within organizations. Somehow, these entities survived before Scrum was introduced. They are not just going to fold because they have not done it right. They may choose to ignore some of the principles of Agile and continue to bring in revenue without coming all the way around.

So the Agile community has some advice. Make sure good technical practices are in place. Have motivated and skilled people in the trenches with the will to change. Make sure there is executive support. Use some assessment tool. There are other suggestions, these just come to mind immediately.

If the right ingredients are not present, people are encouraged to leave the organization, or the organization to get rid of the misfits. Coaches are encouraged not to engage with dysfunctional organizations, or to fire the client when they discover that the resistance is too great.

This leaves me feeling uncomfortable. What about those left behind in the wreckage of an implementation gone awry? Fear, stress and lies are still the modes of operation. There is no hiding from the authorities. The overhead of the process is overwhelming. People are worse off, thanks to the mangled introduction of Scrum. For many reasons including personal and macro-economical, people cannot just leave the situation.

What should be done to help them?

Chatting over Skype. I think it highlights some of the cultural differences of adopting Agile. Here’s the award acceptance video, too.

“Most organizations have suicidal tendencies”. -Jean Tabaka

Update: Adding the video from Agile Australia mentioned by Mike Alber.

Day 1 – 9.45am – Jean Tabaka from Zoltan Deak on Vimeo.

Is the Product Backlog a list of prioritized “stuff to do”? Does it include defects, tasks and feature requests? What else?

I recently received an email from a senior-level manager, who raises a valid question about all the meetings associated with Scrum.