Helping web developers and operations bridge the deployment gap
Posts tagged as:
If you want to get things done, focus is the key. Single piece flow (focusing on only one task at a time) might be too extreme, but limiting your work to your capacity is mandatory. No matter whether we’re talking about a team, an organization or about your personal productivity.
Matthias and I started this blog over a year ago because we had first-hand experiences with the rift between developers and sysadmins. We knew this was a lose-lose situation not only for those directly involved, but the companies they were working for as well. We’ve described many real-life examples of how to overcome this rift, [...]
Agile methodology builds on the concept of iterations – time boxes – in which you create a piece of working software. Each iteration starts with a planning meeting where the team takes stories from the backlog and commits to the sprint goal. If you use a tool like Pivotal Tracker, you even get emergent iterations [...]
Currently, I’m preparing for teaching my next course on Agile Methodology. Again and again, I wonder what is the single most important thing my students should be able to take with them after four full days. One of my core messages is definitely that agile is more about principles than about practices. If you absorb [...]
It’s a very important thing for any agile team to find a definition of Done, which fits the expectations and the environment of the current development. For User Stories, I definitely prefer Done = Released as the most helpful metric. Only if a story is really out there serving users can you truly forget about [...]
We’re using PivotalTracker as our agile planning tool. It’s great for maintaining a backlog of prioritized user stories and managing the flow of stories within an iteration. We’re really happy with it. But recently a new requirement came up: How can we manage our bigger features? How can we make sure all the stories we [...]
It’s been a while since we were using Thoughtworks Mingle as our agile project management tool. We liked their Kanban style Card Walls View a lot.
Nevertheless, we switched to PivotalTracker because of its superior support of prioritizing stories in a backlog and automated iteration planning. Unfortunately, PivotalTracker does not offer any Kanban style [...]
Zen is a brand new Kanban tool for lean project management. In contrast to PivotalTracker, which concentrates on automating iteration management for SCRUM like projects, Zen’s main view is a story board. The funny thing is, that I preferred the stroy board view in Mingle over the list view provided by PivotalTracker before I started [...]
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 [...]
