A while back I pointed out that high performing teams tend to break their automated build. This might be misconstrued, so to clarify the point. A successful, productive Team will inevitably discover unexpected issues that will break the build. However this does not make breaking the build acceptable so do make sure that this message is reinforced albeit gently and with good humour, for example with silly hats or similar.
Showing posts from June, 2007
- Other Apps
I like to travel light. I hate carrying things, especially big, bulky laptops. But as part of my work I need to take notes, and also have access to a range of reference materials that can be used to help some Teams to understand what I am explaining - slideshows, summary documents etc can help get the agile message across. The problem is I often don't know that I need a specific document until I need it. I also have a (growing!) backlog of blog entries that need thinking about and finishing - it would be nice to be able to work on these when I can wherever I am but without the encumberance of a laptop. In order to solve this 'write once access anywhere problem' I have been playing with the online storage service provided by Omnidrive to provide a central location for data I use regularly and "in progress" documents. The system integrates Zoho Writer with the storage so documents can be edited online anywhere - but also they can be posted to a blog. T