When I got back to the office after my Certified Scrum Master training, I didn't know what to do. I knew all the theory but I didn't know what to do next.
"Well...I suppose we try it", I thought, "Let's start with a taskboard" and so we made a taskboard.
Then we had a daily scrum meeting.
Then we did a planning meeting, then we tried a retrospective and then a review meeting and before long we were doing Scrum.
Then we started having problems because the client/PO kept changing things so we learned about Kanban and got rid of the iterations (or vice versa, I can't quite remember). On some projects, having iterations worked so we kept them.
Then we realised the product backlog was often in bad shape so we started training the PO and making her understand what happens when the product backlog is in bad shape.
Then we started fixing problems in the code by adding a "Code Review" column to the taskboard.
Then we made a google doc for one of our projects for our client in a different timezone and used it as our taskboard (we had our daily scrum meeting around the google doc), this gave him 100% visibility on what we were doing and when (and who).
Today I learned about "Crystal Clear" created by Alistair Cockburn (say: "co-burn") which I'm now reading about. Maybe we can borrow some things from that.
You see, for me (us) it wasn't about doing Scrum or Agile or Kanban or whatever but was about creating something that works. If it works, keep doing it; if not, change it!
As Seth Godin puts it in a post I just read:
"The Simple two-step process
Step one: Open all doors. Learn a little about a lot. Consider as many options as possible, then add more.
Step two: Relentlessly dismiss, prune and eliminate. Choose. Ship."