Monthly Archives: April 2014

Back to the Basics: Individuals and Interactions

Engineers discussing in front of computer.

Serge Bertasius Photography –

We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:

Individuals and Interactions
Processes and Tools

This is how the Agile Manifesto starts. Not with a list of acceptable practices. With a statement that people matter. Specifically that they matter more than the process and tools that we use to get value. Continue reading

The New Daily Stand Up

I’ve spoken about the Daily Stand Up before. I’ve also talked about how it didn’t work right for us. Some time in the last couple of weeks I came across a blog post that resonated with me on these meetings.

See, I’m all for Scrum. It’s a great tool. The process framework is something that will really help enable change in most organizations. That said, Individuals and Interactions over Processes and Tools. The Agilist in me can not allow Scrum to become a sacred cow. Continue reading

The Development Team

Team by graur codrin via

graur codrin via

Scrum runs as a team process. Part of the Scrum Team is the Development Team. Having a dedicated team of professionals delivering fully “Done” product is something that every form of Agile can relate to. An unfortunate side-effect of the name is that not every team is created with the ability to deliver a “Done” product. Continue reading

The Journey Belongs to All of Us

I am learning a lot about Agile. Most of it I learn by reading. I also learn by writing. Each post I put here forces me to reign in my thoughts so I can share them cohesively. This is one of my primary reasons for having a blog.

This blog in particular though has more reason for being. One goal I have is for this to be a community. It is called Our Agile Journey, not My Agile Journey, for a reason. There are not many places where Agilists can congregate without being tied to a particular type of Agile. I would like to see a forum someday. I would really like to have other people contribute though.

Maybe you don’t have a blog of your own. Maybe you have one, but it is tied to your company and not a good place to put certain things you would like to share. Maybe you feel you don’t have enough to start your own blog, but would still like to give back. This could be the place to do it.

This is not a place I want to commercialize. No advertorial’s or straight advertisements. Links that may generate revenue are ok, but they need to be relevant. (Such as to a book, class, or business page.) The point here is to give back to the community, not create the next Agile Alliance.

It could be a single guest post. It could be a mini-series. It could be weekly, or even daily postings. It can be attributed to you, a pseudonym, or anonymous. Every author that wants one will get an about page. From there they can link back to their site or their business.

The details are a little fuzzy but will be worked out as the need arises. The important part is that it remains a place to share about our journeys. We can then learn from each other as we teach each other.

If you are interested please contact me via the “contact me” link above, or via any of the methods available on the “about me” page.

Scrum Master Defined

The topic of what a Scrum Master (SM) seems to be pretty hot lately. In some sense this is confusing to me. I haven’t taken a class and obtained CSM yet. That said, everything I can find points to the CSM and PSM, which I did obtain, being equal. Equivalent in function, knowledge, and ideals.

The Scrum Guide from spells out what a SM does. It does it in 291 words that span half of two different pages. My assumption is that the Scrum Alliance has some similar definition of what a SM does. Of course, Scrum is a framework. Much like the frame of a car is not drive-able Scrum will need more than what is defined to truly deliver value.  Continue reading