What the experience really shows is the opposite: that hierarchical bureaucracy is a work culture that no longer fits the marketplace of 2011. (Source: Forbes, Scrum Is A Major Management Discovery)
I've been exposed to agile processes and methodologies since 2006. Of course, back then I didn't know what it was or how it could help me. What I did know is that it was different, and I had a hard time adapting to it.
It's been ingrained in the way I do things since.
The great thing is that I still remember the frustration and challenge of learning this new system. I remember thinking: There are all these other great, big ideas that we need to tackle - why should I be focused on this one little part?
At some point it hit me - those little parts make the engine go. It's about doing things. We all have great ideas but those who actually implement them are the ones we look to.
So, starting today, I'm introducing the daily scrum. It will initially be focused on a weekly podcast that will turn into a daily resource of agile-based tips and tricks for non-developers.
Why am I doing this?
A few reasons:
- I've always wanted to podcast. Hearing and editing my voice is a bit awkward but I'm fascinated with the radio and the spoken word. And to be honest, I just want go through the process of posting content to a broader audience (kinda like this site).
- I have great access to agile knowledge. I'm referencing Ken Schwaber's book (more info at the end of this post), which anyone can pick up and read. But I also have direct access to the software development community (the birthplace of agile) and my colleague and friend (we'll introduce Mike shortly) who has been training and deploying agile teams for a long time.
- I wanted a valid reason to change my avatar. I'm not sure if this is it, but I'm going for it.
What do I hope you'll get out of it?
Here's how I think this might benefit you:
- I have the experience - and continue gaining experience right now - and the contacts to help you better understand how agile + scrum can help you achieve your bigger goals (via smaller steps).
- We can build a community, you and I. We can apply what we've discussed and learned directly to our jobs. No matter our level within our organization.
- I am not a Scrum Master. I am not an agile expert. I am not an engineer. I am not a developer.
That last point is supposed to be beneficial to you. Really. I'm not going to get bogged down in sprints-this or stories-that. Instead, I'm trying to figure out how we can apply the development approach to project management to our own unique schedules.
So, what's next?
I'm starting to develop this content now and since I want to keep things fresh and relevant, I'll continue building these pieces out as I go along. For now, here's the plan:
- You can hold onto this link, which is the daily scrum category
You can grab the initial podcast session here (It should show up in iTunes shortly!)It's on iTunes now!
- You can subscribe to the feed here
- You can follow me on Twitter: @wiljr
I'll always revert back to those fond days in 2006. Pitching fits, muttering strange words, and other frustration-generating actions.
But this time, we'll have an end goal in place and we'll be better positioned to take advantage of a crucial process for helping us get stuff done.
I've been asked to build a Q&A / forum for this series. I'll work to add something over the next week or so. In the interim, don't hesitate to leave a comment below or send a message to me via Twitter.
Thanks for the initial feedback!
(This is an affiliate link to Amazon.)