- Testing Dash Metrics with Cucumber (Bradley Taylor) – A short article showing off a Cucumber feature for monitoring with Nagios.
- Kanban vs. Scrum (Henrik Kniberg) – A great, 26 page long PDF about the similarities and differences between Scrum and Kanban. Absolutely worth reading!
- Reconnoiter (Theo Schlossnagle) – Theo and his OmniTI Labs are working on a new monitoring and trending application – a combination of Nagios, Cacti and the like with the goal to ease administration and scale efficiently. No releases yet but looks promising.
Archives for June 2009
For developing our Ruby on Rails based web site, we usually take regular SQL dumps from our production servers (of course, anonymizing sensitive customer data along the way). Always having a fresh dump allows us to be on the safe side when writing database migrations. Having an up to date development database enables us to run our test suite as well; it’s just a matter of
rake db:test:prepare to get our test database up-to-date. So far, so good.
I’ve been busier than a one-legged man in an ass-kicking contest the past few weeks. And because of this I haven’t been keeping up with my weekly posts. But yesterday, after getting through the guilt trip, I realized that I was missing more than just blogging. I was missing my weekly retrospectives and thereby losing focus of my priorities. Currently, I am an “Army of One” so the only retrospective I’ve been conducting is with me, myself and you – the reader.
Not writing about and contemplating my experiences, successes and failures from the week’s work meant I wasn’t improving, wasn’t honing my focus. Last week, I had a velocity of 0. For the first time in over six months, I literally delivered no customer value in my weekly sprint. And I chalk it up to not blogging – or at least not holding my strange sort of online weekly retrospective.
Recently, I was looking deeper into how we could add some automated acceptance tests to our Ruby on Rails based website. We’re using RSpec since quite a while now for TDD, but doing some high level acceptance tests was not on our agenda so far.
DRY Cucumber Scenarios
The new cool kid on the block is Cucumber. One of its main features is that you can describe acceptance tests in nearly plain English (or any other language) simplifying discussions with the product managers and other, non-technical stake holders. I’m really impressed by the ease, with which you can describe DRY scenarios like our login feature:
It’s time to say “Thank you” to all of you, our loyal readers. Thanks for reading, commenting and subscribing to our posts for exactly one year now. That’s right, Agile Web Operations is now one year old. I can hardly put into words how great it is to have you with us!
103 posts and 113 comments. That’s the result of our first year. And, exactly 200 of you have subscribed to our RSS feed – an excellent choice. For all of you who joined recently (and to remind you veterans), check out the five most read posts:
- Puppet or Capistrano – Use the Right Tool for the Job (Guest post by Andrew Shafer)
- Puppet vs. Capistrano – a short comparison
- System Configurations + Code Revisions = Continuous Integration FTW (Guest post by Patrick Debois)
- Thoughtworks Mingle vs. Pivotal Labs Tracker
- Agile Tool Vendors: Please don’t try to manage complexity – simplify my life!
And don’t miss out on our three most commented posts:
- Agile on steroids
- Configuration Management remixed: Introducing Carpet
- Visible Ops: Rolling Out Change Management
I hope you enjoy reading Agile Web Operations as much as we do writing it. Keep the comments flowing and don’t forget to tell your friends!
We’re looking forward to the coming years of Agile Web Operations.
Dan & Matthias