Archive | October, 2010

Why You Should Use Twitter Style Language In Your Project

Now that Oprah joined Twitter, it is a serious medium. In Project Management we like “serious”. It sounds wise, professional, the proper thing to do. Now that Oprah is leading the masses towards Twitterland, we need a serious answer to why we should use this medium in our projects. The short answer: Twitter can enable […]

Continue Reading

Estimating Work Shared Between Two Backlog Items

Product backlog items can be ideally written to be independent. It is the hallmark of a good team that its members can implement product backlog items in any order. However, it would be nearly impossible to remove all dependencies between product backlog items and so our goal becomes minimizing important dependencies rather than eliminating them […]

Continue Reading

Towards generic APIs for the open world

In my last post on how Clojure protocols encourage open abstractions, I did some quick rounds between type classes in Haskell and protocols in Clojure. At the end in the section titled “Not really a type class”, I mentioned about the read function of Haskell’s Read type class. read takes a String and returns a […]

Continue Reading

Bad Programmer, Bad Process Or Bad Education

A few articles in the past week prompted some thinking about the industry of software development. In this case, when I say software development, I am talking about developing websites, web applications, commercial software, enterprise software and almost anything else that requires someone who can code. When comparing the industry to other scientific industries, software […]

Continue Reading

Getting Predictable

Over the past few weeks, I’ve made two assertions about new agile teams. First… teams need to get good at calling their shots. To me, that means that over time, a well-formed, stable team should get good at being able to predict what they will get done over the course of the next iteration. Second… […]

Continue Reading

How *Not* to Eat An Elephant

The old adage about eating an elephant is wrong. As it goes, the answer to “how do you eat an elephant” reads “one bite at a time.”  And a lot of agile folks subscribe to that notion in general—you can accomplish any task if you break it up into smaller tasks, and take it one […]

Continue Reading