How do we justify spending money on an internal Community & Collaboration platform like JiveSBS? I have been thinking more about Social Business ROI and how to measure it effectively.
Over the years I have become convinced that more often than not the success or failure of a project or product has very little to do with the technology involved.
As a proponent of customer-centric development efforts, agile methods, and frameworks such as Ruby on Rails, it probably comes as no surprise that I am also a big fan of story tests and test-driven development (TDD) in general.
There is danger in attempting to change the world in one step. Whilst a big fan of Agile methods, I spend a lot of time ensuring that people understand the magnitude of the task they have ahead of them, and how difficult it will be, without curbing their enthusiasm.
I have experimented with Agile project management tools over the years, trying to find something that has a good balance of simplicity and functionality. Nothing beats a good old-fashioned “project wall” or board for radiating information to the team and stakeholders … or so I thought, until I discovered Pivotal Tracker.
